NewThe guide: 11 paywall examples

10 minutes

7 things to understand about your onboarding

You have downloads, a well-designed paywall, and a competitive offer. Yet your app converts poorly. What if the problem is what happens before the paywall?

Clément Parot

7 things to understand about your onboarding

Article summary

  • How many users actually reach your paywall?
  • The number of screens is not a performance metric. What counts is their contribution to conversion.
  • Improving onboarding completion does not necessarily mean improving monetization.
  • Duration alone does not let you tell engagement from friction.
  • It is about building the one that best turns your downloads into engaged users and paying subscribers.

Summarize this article with

When a mobile app does not convert enough, the first reflex is often to change its paywall.

Change the design. Test a new discount. Add a free trial. Put the annual subscription forward.

But there is a question we often forget to ask:

How many users actually reach your paywall?

And among those who reach it, how many have understood why your app deserves to be paid?

An onboarding is not just there to welcome a new user or to ask for their first name.

It has to help them understand what your app is going to give them.

At firstapp, we support B2C mobile apps in optimizing their onboarding, their paywalls, and their monetization.

Here is why your onboarding can be one of the main brakes on your conversion, and how to improve it.

1. An onboarding that is too long is not necessarily a bad onboarding

We regularly hear that a good onboarding has to be short.

Three screens maximum. As few questions as possible. Immediate access to the product.

But that logic forgets an essential element: not every screen creates the same value.

A screen that asks for useless information can create friction.

A screen that helps the user specify their goal can, on the contrary, strengthen their engagement.

Take two examples.

App A: 3 screens

  1. Welcome to the app.
  2. Discover our features.
  3. Go Premium.

App B: 12 screens

  1. What is your goal?
  2. What is your main difficulty?
  3. How long have you been running into this problem?
  4. What result would you like to get?
  5. Several personalization questions.
  6. Presentation of a tailored program.
  7. Paywall.

App B has a longer onboarding.

Yet it can convert better if each step helps the user understand the value of the offer.

That does not mean a 12-screen onboarding is always preferable.

The number of screens is not a performance metric. What counts is their contribution to conversion.

Newsletter

Once a week.

Last issue

We opened 10 apps to see how they sell a subscription.

+534 people read us each week

2. Why some long onboardings convert better

An onboarding can play several roles in the purchase decision.

It helps the user express their need

A person who downloads a nutrition app knows they want to improve their diet.

But they have not necessarily formulated a precise goal.

By asking what they want to accomplish, the app can help them clarify their expectations.

That information can then be used to personalize the experience.

It strengthens the relevance of the offer

A user who has just answered several questions can expect to receive something adapted to their profile.

If the app actually presents a personalized experience, perceived value can go up.

Warning: asking questions without using the answers can produce the opposite effect.

It prepares the paywall presentation

A paywall shown after a generic onboarding can feel disconnected from the user's expectations.

The other way around, a paywall that presents a solution consistent with their goal can be more convincing.

The onboarding should therefore not simply come before the paywall.

It has to prepare the understanding of the offer.

3. The mistake: wanting to cut the number of screens at all costs

Imagine an app that has a 15-screen onboarding.

Its team decides to cut it to 5 screens to improve the completion rate.

Hypothetical result:

MetricLong onboardingShort onboarding
Downloads10,00010,000
Users reaching the paywall5,0007,000
Paywall-to-Paid conversion12%7%
New paying subscribers600490
Download-to-Paid6%4.9%

In this example, shortening the onboarding lets more users reach the paywall.

But overall conversion goes down.

Why?

One possible explanation is that users reach the offer faster, but with a weaker understanding of the product's value.

This is only a hypothesis: only a controlled experiment would make it possible to determine the causes.

Improving onboarding completion does not necessarily mean improving monetization.

That is why you have to measure the path through to payment, not only through to the last screen.

4. The five onboarding mistakes that can cost you subscribers

Mistake 1: asking questions without explaining why they are useful

Asking for a user's age, habits, or preferences can be relevant.

But if this information does not seem useful to the experience, it becomes extra friction.

To test: explain why each piece of information is asked for, and remove the questions that do not bring identifiable value.

Mistake 2: presenting features rather than results

"Personalized tracking", "advanced statistics", "smart recommendations".

These features can be interesting.

But they do not necessarily say what the user is going to get.

A fitness app may have more to gain by showing how it helps people progress than by simply presenting its features.

To test: replace technical descriptions with concrete benefits.

Mistake 3: asking people to create an account too early

Account creation can be significant friction.

Some users do not want to share their email address before they have understood what the app gives them.

That does not mean you should systematically push sign-up later.

But its placement deserves to be tested.

To test: account creation before or after the first demonstration of value, when the product architecture allows it.

Mistake 4: showing the paywall with no transition

The user answers several questions.

Then, with no explanation, a screen asks them to pay.

The shift from personalization to subscription can feel abrupt.

To test: add a summary screen that explains what the app has prepared for the user before presenting the offer.

The announced personalization obviously has to be real.

Mistake 5: not measuring drop-off screen by screen

You know that 40% of users finish the onboarding.

But do you know where the remaining 60% drop off?

Without step tracking, it is hard to tell a problematic question from a technical problem or from friction tied to sign-up.

To test: instrument the important onboarding steps and analyze drop-off by cohort.

5. Six experiments to improve your onboarding

Experiment 1: short onboarding versus long onboarding

Hypothesis: a more detailed path can improve conversion by strengthening understanding of the product.

Compare two variants whose value proposition stays consistent.

The goal is not to prove that long is better than short.

It is to find the level of personalization that maximizes the economic results.

To measure: completion, Download-to-Paid, and revenue per install.

Experiment 2: add a personalized result screen

Hypothesis: presenting a result adapted to the user's answers can strengthen perceived value before the paywall.

For example, an education app can present a learning program adapted to the stated level and goals.

The user then understands more concretely what the app can give them.

To measure: paywall exposure, conversion, and revenue per install.

Experiment 3: test the moment of account creation

Hypothesis: pushing account creation later can reduce initial friction.

You can compare:

  • Account creation at the start of the onboarding.
  • Account creation after personalization.
  • Account creation after a first product experience, when it is technically possible.

You also have to take data recovery, continuity across devices, and payment constraints into account.

To measure: completion, sign-ups, Download-to-Paid, and retention.

Experiment 4: personalize the paywall arguments

Hypothesis: reusing the onboarding answers can make the offer more relevant.

A nutrition app can adapt its promise to the stated goal.

An education app can present different benefits depending on the user's level.

To measure: Paywall-to-Trial, Download-to-Paid, and revenue per install.

Experiment 5: offer a first experience before payment

Hypothesis: letting the user discover part of the product's value can improve their willingness to pay.

For example, a content-creation app can let people generate a first preview before presenting the subscription.

The user then knows more precisely what they are buying.

But this approach can also reduce paywall exposure if too many users drop off before they get there.

To measure: activation, paywall exposure, conversion, and revenue.

Experiment 6: remove the steps that bring no value

Hypothesis: some questions or steps create friction without improving personalization or conversion.

Analyze drop-off and identify the screens whose usefulness is not demonstrated.

Test removing them or moving them to after sign-up.

To measure: completion, activation, and Download-to-Paid.

6. The metrics to track to measure your onboarding

The completion rate is useful.

But it is not enough.

At firstapp, we recommend tracking the whole user journey.

MetricWhat it lets you understand
Onboarding StartedNumber of users who start the journey
Onboarding Completion RateShare who finish the onboarding
Drop-off by stepScreens where users drop off
Paywall Exposure RateShare who reach the paywall
Paywall-to-TrialThe paywall's ability to generate trials
Download-to-PaidOverall conversion to paying subscribers
Revenue Per InstallRevenue generated per install over a defined horizon

You also have to analyze the time needed to finish the onboarding.

But here again, a faster path is not automatically better.

If a user spends more time in the onboarding because they are actually personalizing their experience, that time can be useful.

The other way around, if they stay stuck on a step they do not understand, that is a problem.

Duration alone does not let you tell engagement from friction.

7. How to know if the problem comes from the onboarding or the paywall

Take two apps.

App A

  • 10,000 downloads.
  • 3,000 users reach the paywall.
  • 15% become paying subscribers after exposure.

Result: 450 new subscribers.

App B

  • 10,000 downloads.
  • 7,000 users reach the paywall.
  • 8% become paying subscribers after exposure.

Result: 560 new subscribers.

App A has a better conversion rate on its paywall.

Yet app B generates more paying subscribers.

Why?

Because it exposes many more users to its offer.

That does not prove that B's onboarding is better: the audiences and the paths can be different.

But it shows why it is dangerous to look only at paywall conversion.

The right metric depends on the problem you are trying to solve. The final result must always be evaluated at the scale of the full funnel.

Conclusion: your onboarding has to prepare conversion, not simply be finished

A good onboarding is not measured only by the number of users who reach the last screen.

It has to help users understand the product, discover its value, and make an informed decision when they meet the paywall.

Sometimes that means removing steps.

Sometimes that means adding some.

What matters is not building the shortest possible onboarding.

It is building the one that best turns your downloads into engaged users and paying subscribers.

At firstapp, we help subscription mobile apps improve their monetization by experimenting on the onboarding, the paywalls, and the pricing.

Want to identify the points of friction that limit your app's conversion?

Discover firstapp

FAQ: optimizing a mobile app's onboarding

How many screens should a mobile onboarding contain?

There is no ideal number. A short onboarding can reduce friction, while a longer path can be useful to personalize the experience and demonstrate the product's value. The right format depends on the app and has to be tested.

Does a long onboarding convert better?

Not necessarily. A long onboarding can improve understanding of the offer, but it can also cause more drop-off. You have to measure overall conversion and revenue, not completion alone.

Should you show the paywall before or after the onboarding?

It depends on the moment when the user understands the product's value. An early paywall can maximize exposure, while a later paywall can benefit from a better understanding of the offer.

How do you measure an onboarding's performance?

Track drop-off by step, the completion rate, paywall exposure, Download-to-Paid conversion, and revenue per install. Use comparable cohorts and consistent observation windows.

Should you ask for account creation before the paywall?

There is no universal rule. The best moment depends on technical constraints, the need to save data, and the user experience. Several placements can be tested.

Newsletter

Once a week.

Last issue

We opened 10 apps to see how they sell a subscription.

+534 people read us each week