The first 60 seconds of an app

Five screens, one decision

What should the user see before the price?

Ayo Omolewa's teardown of a sleep app shows a sequence that repeats across dozens of subscription apps:

Screen	Job	What breaks it
Promise	One concrete sentence with a horizon: "sleep better starting tonight"	"Improve your sleep" promises nothing testable
Goal	A multiple-choice question that commits the user and feeds the plan	Too many options, or none that matter
Plan	A program built from the answers, with numbers: bedtime, duration, days	A generic plan that could belong to anyone
Price	The plan first, so the price is compared to the outcome	Price shown before the user sees value
Trial	Seven days free, then a subscription with a clear end date	A trial that feels like a surprise charge

The psychology is standard (commitment, specificity, loss aversion), so execution decides. The right-hand column breaks the sequence faster than bad visual design does.

The order is the conversion. Each screen borrows credibility from the one before it. Move the price up, and the plan has to sell itself alone.

Steal the structure, not the app

Where do you start if you have never built a paywall?

Start from screens that already work. Libraries such as Mobbin or ScreensDesign index thousands of screens from live apps, including paywalls and onboarding flows. The first mover paid for the experiments, and you can study what survived.

Copy the order of screens, the type of question and the way the price is framed. Write the content yourself.

Remove friction before value

What is the smallest thing someone must do to feel the product?

A restaurant app in Omolewa's teardown saw its App Clip drive 60 percent of its users, according to his analysis. An App Clip opens one function, such as ordering or booking, without a full install. Once the value is demonstrated, the full app takes over.

Every step before value is a chance to lose someone:

• Mandatory signup.
• A ten-screen tutorial.
• A notification request at launch.
• A profile form.

For each one, ask whether the user could feel the product without it. If so, move it after the first win.

Measure three numbers

How do you know the first session works?

Number	Question it answers	First fix if it is low
Completion rate	How many installs finish onboarding?	Remove a step before value
Time to activation	How long before the user gets the promised outcome?	Shorten the plan, cut the tour
Trial conversion	Does the promise survive the trial?	Rewrite the promise before redesigning the paywall

Add session recordings on a sample: watching someone hesitate on one screen often reveals more than a drop-off rate. Then test one variable at a time, 50/50, and keep the winner.

The first-session checklist

• Write the promise in one sentence, with a testable horizon.
• Ask one goal question, with concrete choices.
• Build a plan that uses the answers.
• Show value before price.
• Give the trial a clear end date.
• Measure completion, time to activation, trial conversion.
• Watch five session recordings before changing a screen.
• Test one variable, keep the winner, repeat.

Sources

• Ayo Omolewa, sleep app onboarding structure: promise, goal, plan, price, trial — instagram.com/reel/Dd1-6QVyOs8
• Ayo Omolewa, reusing winning screens, Mobbin and ScreensDesign — instagram.com/reel/Dc2UeNSg-Lo
• Ayo Omolewa, App Clips and install friction — instagram.com/reel/Ddnfah6gY-A
• Ayo Omolewa, one number, traces and 50/50 tests — instagram.com/reel/DeNKjDeyYIl