One dashboard, multiple jobs
I intentionally kept timer, tasks, deadlines, notes, and AI support in one place. The product value comes from reducing context switching, so separating them into unrelated views would weaken the core idea.
Student productivity platform
Study Flow
A full-stack productivity dashboard for study sessions, notes, tasks, and deadlines in one calm workspace.
Role
Product design, frontend, backend
Scope
Interface design, product structure, app architecture
Context
Solo project
Study Flow
Tasks
Focus
Notes
Study dashboard
Daily flow
Focus block
25:00
Session
Deadlines
Database report02
Systems quiz03
Presentation draft04
Overview
A student workflow product instead of a pile of disconnected tools.
Study Flow combines a Pomodoro timer, note-taking, task management, deadline tracking, and an AI assistant panel into one product. The goal was to make studying feel more continuous and less fragmented.
I wanted to build the kind of study product I would actually want to use myself. Most student tools solve one narrow job well but force the user to keep context-switching between multiple apps.
Timeframe
Multi-feature student product build
Challenge
Students constantly switch between timers, notes apps, task lists, and reminders, which makes studying feel more fragmented than it should.
Product angle
This project best represents how I think across product scope, UI structure, and full-stack implementation at the same time.
Goals
What I wanted to achieve
Keep planning, focus, and execution inside one coherent product
Reduce the friction of switching between notes, tasks, and timers
Make the interface feel calm enough for repeated daily use
Constraints
The app had to support several workflows without becoming visually noisy
The product needed clear state handling because multiple features live in one dashboard
As a solo build, the scope had to stay practical enough to ship incrementally
Process
How the project took shape
01
Define the workflow first
Before thinking about screens, I framed the product around a simple loop: plan the work, focus on it, capture notes, and track what is next. That gave the app a stronger product spine than a typical dashboard clone.
02
Organize the interface by mode, not by feature list
Instead of presenting everything as equal widgets, I grouped the interface around what the student is trying to do in the moment. That made the dashboard easier to scan and reduced the feeling of visual clutter.
03
Build the full-stack shape around product behavior
The backend, state, and UI all had to support one continuous workspace, so I kept the architecture aligned with the product flow rather than treating frontend and data as separate concerns.
Decisions
Product and interface calls that shaped the result
AI as support, not spectacle
The assistant panel is there to help the student stay in flow, not to dominate the interface. I treated it like an embedded tool inside the workspace instead of the headline feature.
Calm visual hierarchy over heavy decoration
A study tool is something people should be able to live in for a while, so I prioritized readability, pacing, and structure over visual novelty.