The first minute in your app: onboarding that doesn't lose people

Short answer: The best first minute gets people to the thing they downloaded your app for, fast, and asks for as little as possible on the way. Let them look around before signing up, ask for permissions only when a feature needs them, and swap long welcome tours for short tips at the moment they help. Then measure each step, because the screen where people quit is rarely the one you would guess.

Most first-run problems come from good intentions: the owner wants to explain everything, collect details early and switch on notifications "so we can stay in touch". Each of those adds a screen between the new user and the reason they installed the app.

Apple's Human Interface Guidelines put the ideal plainly: people should be able to understand an app by using it, and if onboarding is needed it should be fast, fun and optional (onboarding guidance). Google's Android documentation makes the same argument for permissions. Here is what that looks like in practice.

Walk-through: a sample café app

Imagine a café group in Wellington with an app for ordering ahead and collecting loyalty stamps. This is a made-up example to show the decisions, not a real client.

Screen 1: launch

Common version: a splash screen with the logo, then three swipeable "Welcome to…" slides, then a sign-up wall.

Better version: a brief splash only if needed, then straight into the menu for the nearest café. Apple's guidance suggests displaying a splash screen just long enough to absorb at a glance, and notes that onboarding happens after launch, not as part of it. If the app needs a location to choose the café, offer a list of cafés with a "use my location" option, rather than demanding location immediately.

Screen 2: browsing the menu

Nothing is asked of the user here. They can scroll, search and add items to an order. This is the point where most people decide whether the app is worth keeping, so it should load quickly and look like the real thing, with photos and prices.

A single context tip can help here, such as a small note pointing at the stamp counter the first time it appears. Apple recommends context-specific tips placed near the part of the interface they describe over one long upfront tutorial, because people learn better when they focus on one task at a time.

Screen 3: the first meaningful action

The user taps "Order for pick-up". Now there is a real reason to create an account: the café needs a name for the cup and a way to send the "ready" message.

Apple's account guidance says to delay sign-in as long as possible, noting that people often abandon apps forced to sign in before doing anything useful, and gives the example of a shopping app that lets people browse and asks for sign-in at purchase. It also recommends passkeys or Sign in with Apple where possible. Keep the form to what the order needs: name, email or phone, and a password or passkey.

Screen 4: the notification request

After the order is placed, the app asks: "Want a notification when your order is ready?" That question explains itself; the system prompt follows.

Apple's privacy guidance says to request permission only when the app clearly needs it, ideally when people use the feature that requires it, and to avoid asking at launch unless the app cannot work without it. If you show your own explanation screen first, Apple says it should have one button that clearly opens the system alert, and should not use a button labelled "Allow" or imitate the system dialog.

Android's guidance on requesting permissions matches: ask in context when the user starts to interact with the feature, always let them cancel an explanation, and if they decline, keep the rest of the app working rather than blocking them.

Screen 5: the empty states

Before the first order, the "My orders" tab and the loyalty card are empty. An empty screen is onboarding too. Instead of "No orders yet", show what will appear and how to get there: "Your orders will show here. Your first coffee earns your first stamp." with a button back to the menu.

Screen 6: later, optional extras

Birthday rewards, favourite café, dietary preferences: Apple's onboarding guidance suggests postponing non-essential setup and offering sensible defaults. Ask for these after the second or third order, from the account screen or a small prompt, never in the first session.

Anti-patterns to remove

The tour nobody reads. Several slides of features before the app opens. If you keep one, make it skippable and do not show it again; Apple suggests putting a skipped tutorial somewhere people can find it later, such as help or settings.
Permission stacking at launch. Location, notifications, camera and contacts in a row before the user has seen anything.
Sign-up before value. A login wall on an app whose main content could be browsed without an account.
Teaching the phone, not the app. Apple's guidance notes people do not need to learn how to use their device in your onboarding.
Fake system alerts. Custom screens that look like the iOS or Android dialog, or have "Allow" buttons.
Asking for a rating in the first session. Apple's onboarding page suggests letting people experience the app before asking for ratings or purchases.
Big downloads before first use. Apple warns against making people wait for downloads before they can interact.

Measuring where people drop off

Log a simple event for each step in your analytics tool: app opened for the first time, first screen viewed, first meaningful action started, sign-up completed, permission prompt shown and accepted, first order placed. Then look at the funnel weekly for the first months after launch.

Three patterns to watch:

A big drop at sign-up. Try moving it later or adding a quicker sign-in option.
Low acceptance of a permission. Rewrite the explanation, or move the request closer to the moment it helps.
People finishing onboarding but not returning. That is not an onboarding problem; it is the core experience or the reason to come back.

Change one thing at a time so you can tell what helped.

FAQ

Should every app skip sign-up at first launch?

No. A banking app or a workplace tool may need an account before anything else. Even then, explain why on the sign-in screen, as Apple's account guidance suggests.

How many onboarding screens are too many?

There is no official number. If a screen does not help the user complete their first meaningful action, question whether it belongs in the first session at all.

What if a user declines notifications?

Respect it and keep the app working. Offer a gentle reminder later only where it clearly helps, such as on the order-status screen, with a path to settings.

Do iPhone and Android need different onboarding?

The principles are the same; the system dialogs and some permissions differ. Test both, on real devices.

If your app's first minute is losing people and you would like an outside look at the flow, get in touch with the details.