Stride
Product design for a study-habit iOS app, from onboarding to the daily plan. The design problem turned out to be one screen: the first one after opening the app.
The 30-second version
Read this first · AnonymisedClient work, shown anonymised. A real, paid engagement whose client asked not to be shown. The name, mark, palette, type and every line of interface copy were re-drawn; the flows, structure and component logic are the engagement’s. No usability testing was run by us, and every number inside a screen is sample data.
01 · The problem
Students don’t lack apps. They lack a rhythm they can keep.
The research the engagement started from said something more useful than “students procrastinate”. Most of them put work off on purpose, and a task list only shows how much is unfinished. It doesn’t tell you what to do in the next twenty minutes.
So the real design problem was the first screen after opening the app.
02 · Decisions
Design for the next twenty minutes, not the whole backlog.
Five decisions, all pointed at the same moment: opening the app with a little time and no plan.
- 01
One named, scoped, timed session first.
The home screen leads with the next session: subject, task, scope, duration, and the start button on the card itself. Everything else sits one scroll below.
Trade-offLess overview on open. We chose momentum over a dashboard.
FIG. 002Home: one named, timed session first. The streak is there, but it isn’t the headline. - 02
Ask how much time fits the day before building the plan.
Onboarding is three screens, under thirty seconds, and says out loud that the choice can change. Then a four-question intake that ends in a plan, not a score.
FIG. 003Onboarding in three screens, each with a progress bar and a Skip. FIG. 004The intake: one honest question at a time, and an ending that hands you a plan. - 03
Study areas, not courses.
An area can be a course or a personal goal (“learn enough statistics to read a paper”). A course code is optional, because not every student’s hardest work comes with one.
- 04
Task creation stays close to the work.
It’s a sheet over the area it belongs to, so the link between a task and its plan stays visible while you type. It doesn’t get its own tab.
- 05
Four stable destinations.
Today, Areas, Progress, You. Nothing moves between visits.
03 · The system
One brand colour, the platform’s own face.
White and cool light grey surfaces, graphite for dark, oxblood (#641E2B) as the single brand colour and brass as a small accent. SF Pro throughout, wordmark included: it’s an iOS product, and the platform face is the honest choice.
8-pt spacing; buttons, fields, chips, progress, tabs, sheets and toasts share semantic colour roles. Contrast checked to AA in both themes, and selected and focused states carry a shape as well as a colour.
04 · Reflection
Showing NDA work without pretending.
The useful thing this project taught me is how to show work a client won’t let you show: keep the thinking, re-draw everything that identifies them, and say so before the first picture.
If we picked it up again, the first thing I’d want is the data we never saw: whether people who started a session from the home card came back the next day.
