First-Run Onboarding

From install to a personalized first Coach conversation

Four short screens shown once that get a new user from "just installed" to a personalized first Coach conversation — not a generic feature tour.

The promise

The first screen states the app's whole thesis before asking for anything: generic health advice ignores what makes you you; Livewello's Coach reads your genetics, labs, and records together instead of making you re-explain your history every time.

What should your plan help with first?

Rather than dropping the user straight into an empty chat box, onboarding asks a single, low-friction question: managing a health condition, caring for someone else, understanding genetics, or building a habit.

This choice seeds the Wellness Coach's first conversation with a real prompt tailored to that intent, so the very first exchange is relevant instead of generic.

Notifications

A plain-language case for enabling push — reminders for goals, sharing invites, and check-in nudges — with an explicit **Not now** escape hatch, not just a system permission dialog with no context.

Wearables

Same pattern for health-data connection: explain the payoff (the Coach can factor in steps, sleep, heart rate, and workouts, and can auto-check-in on step-count goals) before asking for the HealthKit/Health Connect permission. Both permission screens can be skipped — nothing in onboarding is a hard gate.

Every step answers "why should I do this?" before asking for anything — a picked intent shapes the first real conversation, a notification ask explains what it's for, a wearables ask explains what it unlocks. That's the difference between onboarding that feels like a tutorial and onboarding that feels like the product already understands what the user showed up for.