Learnlog - iOS Development

Starting with a Question

In an era overflowing with information, people are learning more than ever, but finishing less.
Between podcasts, newsletters, videos, and online courses, most learners lack the same structure that helps them stay consistent with fitness or nutrition.

LearnLog was born from a simple question:

“What if learning had a training plan?”

The goal was to create an app that helps busy, curious people organize their learning habits with the same clarity and rhythm that apps like Fitbod or Runna bring to exercise.

Brand Identity Moodboard:

The Problem

Today’s learners face an overwhelming paradox: unlimited content, zero structure.

• 64% of adults participate in informal learning every year

• 91% of work-related learning happens outside formal training

• Yet, few tools exist to help people stay consistent, measure progress, or reflect

Self-directed learners often struggle with:

• Structure — no clear “what to do next.”

• Consistency — no accountability or rhythm.

• Overchoice — too many tools, not enough focus.

Most platforms either drown users in content (Coursera, Skillshare) or leave them with blank pages (Notion). There’s no tool designed purely to guide the act of learning itself.

The Vision

LearnLog helps people learn like athletes train — with personalized, trackable plans that adapt to their goals.
It’s a system to turn curiosity into a habit: clear, measurable, and sustainable.

The mission: make learning as habitual as exercise.

Design Goals

Design a lightweight, flexible system that:

• Helps users plan and track learning goals with minimal friction.

• Provides visual progress feedback to encourage consistency.

• Uses AI only where it simplifies, not overwhelms.

Idea Boards + Design Exploration Artifacts

Design Process

I began with sketches and a Figma prototype to map the flow:
Template → Time & Rhythm → Activities → Daily Plan → Reflection.

From there, I wanted to see how far I could push my UX skills into working code — to test how the product feels in motion rather than just on boards.

That’s when I began building in Cursor IDE, using AI-assisted code generation with Claude Code and the OpenAI API.

• I scaffolded the project in Swift, connecting Firebase for user data and plan storage.

• The OpenAI API handled plan generation and converted text input (“Learn AI basics”) into structured JSON, which populated the plan builder UI.

• I iterated daily, learning just-in-time development: debugging state management, optimizing prompts, and wiring design logic directly into interface code.

This process taught me how design intent translates into system logic, like how “make it simple” requires understanding how the underlying data behaves.

UX Flows

1. Plan Templates
Users start from curated templates or create a plan from scratch.

2. Project Setup
Define the goal, total learning time, and weekly rhythm (e.g. 30 min, 5 days a week).

3. Activity Builder
Pick activity types — Read, Watch, Listen, Practice, Reflect, Create.
Each includes sub-tags like Article, Podcast, or Prototype.

4. Prioritize Focus
Select one or two “primary” activities; the system auto-balances time across them.

5. Daily Plan Generator
Generates one simple task per day — “Watch Lecture 1 – Day 3 of 14” — with Mark Done, Reflect, or Swap actions.

6. Reflection & Feedback
After each task, users can log quick notes or moods, feeding a sense of measurable progress.

Onboarding Ideation Diagram:

Learnings

Building LearnLog blurred the line between designer and developer.
Learning Swift, debugging APIs, and shaping AI outputs deepened my empathy for how systems behave — and how design constraints ripple through real code.

It also reinforced a UX truth: clarity is an engineering problem as much as a design one.

By grounding design in functioning logic, I built not just a prototype — but a deeper understanding of how product teams can make complex ideas feel effortless.