---
title: "Stride — Study-Habit App, Anonymised"
description: "An anonymised study-habit iOS app designed around one clear next session, with onboarding, intake and a component set. No metrics claimed."
kind: anonymised
kindLabel: "Client work, anonymised"
status: "Client work, anonymised — name, brand and interface re-drawn at the client's request."
year: "2025"
location: "Canada"
sector: "Product design"
services: ["Product UX and UI", "Branding and identity"]
dateCreated: 2025
canonical: https://uxpro.ca/work/stride
publisher: "UXPro Design Studio"
license: "Quote freely with a link to the canonical URL."
---

# Stride, an anonymised study-habit app — Put the next study session on the first screen.

**Client work, anonymised.** Client work, anonymised — name, brand and interface re-drawn at the client's request.

> The engagement was real and paid for. The client asked not to be showcased, so the name, the brand and the interface on this page were re-drawn by us: the decisions are the project's, the artwork is not the client's. Nothing here is a figure, because their numbers are theirs.

Product design for a study-habit iOS app, from onboarding to the daily plan. The flows, information architecture and component logic come from the paid engagement; the identity is re-drawn at the client's request.

Canonical page: https://uxpro.ca/work/stride

## Project story at a glance

- **The challenge:** A task list shows what is unfinished; it does not tell a student what to do in the next twenty minutes.
- **The decision:** Put one named, scoped and timed study session first, then make onboarding and study areas support that next step.
- **Why it helps:** The design gives an open-ended study intention a concrete next action. Nobody outside the studio tested the screens, and no product outcome is claimed.

## Facts

| Fact | Value |
|---|---|
| Our role | Product UX and UI, the screen set and the component library |
| Scope | Onboarding, intake, study areas, the daily plan and task creation |
| Constraints | Phone-first, iOS; the identity re-drawn for this page |
| Status | Delivered 2025 · no figures shared with us |

## The problem

*Why does a student with four study apps still not start?*

The research the engagement started from said something more useful than “students procrastinate”: students do not lack apps, they lack a rhythm they can keep. A task list tells you how much you have not done. It does not tell you what to do in the next twenty minutes.

So the design problem was the first screen after opening the app. One session, named, scoped and timed, with the start button attached to it — and everything else one scroll below.

## What we designed

Three of the decisions, and the screens they were made on.

- Onboarding in three screens and under thirty seconds: what the product does, then how much study time actually fits the day, with copy that says out loud the choice can change.
- A four-question intake survey with a visible progress bar and a Skip on every screen, ending in a plan rather than a score.
- Study areas that hold a course or a personal goal. A course code is optional, because “learn enough statistics to read a paper” is a study area too.
- A home screen with one obvious starting point: the next session, its subject, its scope and its duration, and the start action on the card itself.
- Task creation as a sheet over the area it belongs to, so the relationship between a task and its plan stays visible while it is typed.
- Four stable destinations — Today, People, Progress, You — with task creation kept contextual rather than given a tab.
- A component set on an eight-point spacing foundation: buttons, fields, rows, chips, progress indicators, tabs, cards, sheets and toasts, sharing semantic colour roles across the light and dark themes.

## What we did not do

- We did not build or ship the app. This is the product design: flows, screens and a component set a developer builds from.
- We did not keep the client's identity. The name, the mark, the palette, the typography and every line of interface copy on this page were drawn for the anonymisation, and the client's own artwork appears nowhere on this site.
- We did not claim a business outcome. We hold no install, retention or revenue figures for the product, so none appear.
- We did not run usability testing. Nobody outside the studio has been observed using these screens.
- We did not invent research to fill a gap. The study numbers the original board carried are the client's, and they are not reproduced here.

## Results

No business metrics are claimed for Stride.

Where a project on this site has real numbers, they appear with a client name, a measurement window and a date. Orient Barber Shop is the only case study on this site with numbers.

## Validation

What can honestly be shown is the standard of the work and the logic of the flow: a first session a student can start without choosing between five equally loud buttons, an intake survey short enough to finish, and study areas that hold a course or a personal goal without forcing either into a timetable.

Every screen was checked for text contrast against WCAG AA in both the light and the dark theme, and every selected or focused state carries a shape as well as a colour, because a ring of oxblood on graphite is not a state a colour-blind student can read.

### The limits of that

- No metrics are held. Installs, retention and revenue are unknown to us.
- No usability testing was run, so nothing here is evidence that the flows work for a stranger.
- Every number inside a screen — sessions done, streak days, question counts — is sample data drawn for the presentation, not a record of anyone's study.
- Anonymisation is not a guarantee. Someone who worked on the original commission may still recognise its scope.

## Why it is shown this way

**Show the thinking. Keep the client's name.**

A studio that sells product design should show product design. A studio that keeps its clients should also be able to show the work when the client would rather not be named — which means re-drawing the identity far enough that the product is not identifiable, and saying so at the top of the page rather than in a footnote.

So the name, the mark, the palette, the typeface and every word of interface copy here were drawn for this presentation. Stride is white and cool-grey surfaces, one oxblood as the single brand colour, graphite for the dark theme, and a brass line used sparingly for small accents. The type is SF Pro throughout, because the product is iOS and the platform face is the honest choice. What survives from the engagement is the part worth showing: the flows, the information architecture and the component logic.

| | |
|---|---|
| Platform | iOS, phone first |
| Discipline | Product UX and UI |
| Deliverable | Screen set and component library |
| Identity | Re-drawn for this page |
| Type in the screens | SF Pro |
| Metrics held | None |

## Credits

- Project: Study-habit iOS app, client name withheld
- Type: Client work, anonymised at the client's request
- Sector: Product design
- Services: Product UX and UI, component library, anonymised identity
- Year: 2025
- Result: No business metrics claimed.

---

Read the illustrated page: [Stride, an anonymised study-habit app](https://uxpro.ca/work/stride)