In this guide
With a subscription app, the question is rarely "does it work?" and more often "do people understand what they are getting, and what it costs?" Testers can answer that well, as long as you ask about comprehension, not about whether they would buy.
Test understanding, not purchase intent
People say they would pay when they would not, and the other way round. A tester who never spends real money in a test tells you nothing about willingness to pay. What they can tell you reliably:
- what they think the free version includes
- what they think they get after subscribing
- what they think happens when the trial ends
- whether they can find how to cancel
Do not ask testers to pay, and do not use real purchases as a test. Use your store's test purchase options. On Google Play, license testers can make purchases with test payment methods that do not charge real money (Android Developers, retrieved 2026-10-24); for Apple, check the current App Store documentation.
Question set for paywall comprehension
Show the paywall, then ask in this order, without hinting at answers.
First glance 1. In your own words, what is this screen offering? 2. What do you think each plan costs, and for how long? 3. What is free and what is not?
Trial and billing 4. If you started the trial, what do you think happens in the end? 5. When would you expect to be charged first? 6. Is anything on this screen unclear or easy to miss?
Trust 7. What would make you hesitate? 8. Is there anything you would want to know before continuing?
Cancellation 9. How would you cancel? Show me where you would look. 10. Once cancelled, what would you expect to keep or lose?
Check the whole path
| Step | What to watch |
|---|---|
| Onboarding | Does the value come before the paywall? |
| Paywall | Are price, period and trial terms visible and in plain words? |
| Restore purchases | Can a returning user find it? |
| Account or settings | Is the subscription status visible? |
| Cancellation | Is it easy to find or is it a maze? |
If a tester cannot explain the price after ten seconds, your paywall needs work, whatever the numbers say.
Limits
Developers are not your paying audience. They will spot unclear wording, broken flows and hidden terms, but they cannot tell you what price to set. Do not treat their answers as pricing research. Both stores publish subscription rules. Google Play asks you to be transparent about terms, cost, billing frequency and auto-renewal, to explain how and when a free trial converts to a paid subscription, and to disclose how users can cancel. Apple's guideline 3.1.2 asks you to describe clearly what the user gets for the price before asking them to subscribe (see sources). Check the current policies; this is not legal advice.
With AppReviewX
Developers give each other private, structured feedback: 1 feedback = 1 credit, new accounts start at 0 credits. Nobody is asked to buy anything, and store reviews remain voluntary and unpaid.
Start with AppReviewX and test your paywall for clarity.
Related: App testing for developers · First app feedback for beginners · What testers look for in your app