Mobile app paywall and subscription examples
Planning subscriptions for your mobile app? Study captured offers from Calm, Duolingo and Revolut to decide how to explain benefits, compare plans and present a trial. Leave with a brief to adapt to your product. Notes are public; a free account lets you keep references and unlock workflows.
Prepare a brief for your subscription offer
Copy this outline into your notes, replace the bracketed items and connect a reference to each choice. You will have a workflow to test before building payments.
Subscription offer for [my app] Paywall trigger: [action or limit reached]. Primary benefit: [what someone will be able to accomplish]. Plans and initial selection: [choices and useful differences]. Actual billed amount and period: [amount, currency and duration]. If a monthly equivalent is shown: [amount and relation to billing]. Optional trial: [length, billed amount and period after the trial, or no trial]. After closing or postponing: [return to the task and remaining access]. After purchase, an error or restoration: [state and next action]. References to compare: [saved screenshots and workflows]. Hypothesis to test: [change, expected outcome and measurement in my app].
Design your paywall with concrete references.
Create your free account with GitHub to save useful references, compare screens in a collection and keep your design decisions together.
One preview workflow per app, with up to 4 visible screenshots. A free account includes 3 complete workflow unlocks per calendar month. No payment card needed. Saving a reference does not unlock its screenshots.
- Open the workflow to understand the offer’s context.
- Save screens that illustrate your decisions.
- Compare them in a collection and record the offer you will test.
After signing in, you will return to these examples to save your first reference.
References to explore
Explore these references and follow each app’s available workflows.
Study the context before the offer
Identify where the offer appears: during onboarding, after a first action or when a feature is selected. The same screen can play a different role depending on what someone has already experienced. Following a workflow helps distinguish an introduction to a plan from an interruption to an ongoing task.
Available captures show screen order, the benefits presented and visible choices. They do not provide conversion rates, A/B test results or app profitability. Use them to develop hypotheses to test in your own product.
Compare how clearly plans are presented
Use the same review criteria across several references. Look at the space given to benefits, the way someone chooses a plan and the information presented before continuing.
