2.8xEstimated signup conversion, before and after
30 daysEach comparison window
Owaves opening screen: a colored 24-hour day clock with the headline A day worth waking up for and a Design My Ideal Day button. Owaves onboarding: after the person picks a goal, the day plan behind the guide fills in with activity blocks. The person's day in Owaves as a colored 24-hour clock built around their Peak Performance goal.
The current Owaves onboarding. The opening screen offers to design your day; after the optional Health step, one goal reshapes the plan in the real app behind the guide.

The problem

Owaves is a daily planning app built around personal rhythms and wellbeing. It needed a clearer path from first open to a useful first experience, with fewer avoidable steps, transparent permission choices and a good path for anyone not ready to connect Health data.

What I did

I redesigned and built onboarding with AI assistance, then shipped it with the team, with the aim of helping people leave their first session with a day they could understand and use. Health connection comes first and is optional; choosing one goal visibly reshapes the day behind a guide people can dismiss and resume, keeping the real app within reach. At completion, a soft subscription offer can be dismissed with Maybe Later, and an instrumented activation funnel lets the team assess the release.

What changed

Estimated first-open-to-account conversion rose 2.8x across matched 30-day periods before and after the release.

How it was measured. Estimated signup conversion divides aggregate Cognito account counts by GA4 first opens, so it doesn’t follow the same individuals through both steps. The two 30-day windows exclude the rollout day; differences in traffic and pre-release testing limit the comparison. These are before-and-after observations of a broader release, so they don’t isolate onboarding from other changes or show gains in retention, subscriptions or revenue.

Read: The Value-First Onboarding Framework → Back to Work →