Toggle paywall on iOS: why Apple rejects it and what to test instead
Apple has begun rejecting iOS apps whose paywall uses a switch to add or remove a free trial. The pattern is not reported as a problem on Google Play or the web, so the practical response is platform-specific: remove the toggle on iOS, keep clear trial disclosure, and test compliant alternatives rather than waiting for the next rejection.
What the toggle paywall did
A toggle paywall presents a subscription offer alongside a switch for adding or removing a free trial. In the common version, the switch starts off with a lower-looking annual plan selected. Turning it on switches the user to a different, often weekly, plan that includes a trial. Because many users continue without touching the switch, they may pay upfront and never see the trial offer.
That mechanic spread after mid-2024 documentation showed weekly revenue rising from about $2,500 to over $5,300, with a 63% introductory-offer conversion rate and 68% retention in that example. Other case studies cited a 17% ARPU boost and a 64% revenue uplift. The appeal was behavioural: the default path favoured immediate payment, while the trial required an active choice.
Why Apple is acting now
Reports of rejections began in mid-January 2026 and quickly multiplied across developers and a Reddit thread, indicating a pattern rather than an isolated review decision. Apple has not published a separate policy announcement explaining the timing.
Three plausible reasons connect the dots. First, Guideline 3.1.2 emphasises subscription transparency, and related scam-prevention language covers tricking users into a subscription under false pretences; a default-off trial can look like a trial most users never see. Second, the design became widely copied and publicly promoted, making it more visible to App Review. Third, user confusion is central to the mechanic itself: if success depends on users not noticing or not using the switch, Apple can reasonably treat that as obfuscation rather than clear disclosure.
A practical iOS compliance checklist
Use this checklist before submitting an iOS update:
- Remove any switch that adds or removes a free trial from the purchase screen.
- State plainly on the selected offer whether a trial is included, its length, and when charging begins.
- Make the trial part of a named package rather than a separate hidden mechanic.
- Check every paywall variant, including experiments and remotely configured screens, not only the default.
- Keep Android and web variants separate if they still use the toggle, and verify each platform's current rules before launch.
A useful April 2026 example is Flo Health: it replaced the toggle with a distinct 14-day free trial plan within a multi-plan paywall while retaining 'Not sure yet?' copy. That keeps the choice visible as a package decision instead of a switch.
Six compliant alternatives worth testing
- Honest timeline paywall: Show the sequence after tapping Start Free Trial, such as access today, a reminder before the end date, and the charge date. Blinkist's version was reported to lift conversion by 23% and reduce complaints by 55%. Clarity can build trust instead of relying on a trick.
- Multi-package selector: Place weekly, monthly, and annual options side by side and badge the package that includes a trial. The user chooses a package; no toggle is needed. Price anchoring can still make the annual option the obvious choice.
- Value-first paywall: Lead with benefits, visuals, social proof, and ratings before price. This reframes the decision from cost alone to the outcome the user receives.
- Personalized paywalls with conditional visibility: Show trial messaging prominently only to users eligible for an introductory offer, and show a direct purchase flow to others. Eligibility, not a switch, determines the offer.
- Exit offer: When a user dismisses the main paywall, present a different offer such as a lower price, longer trial, or monthly plan after an annual rejection. Test carefully because Apple is also stricter on aggressive abandonment offers.
- Web purchase button: For eligible US iOS users, route to web checkout where App Store guidelines do not govern the web flow and the 30% App Store commission does not apply. In-app purchases must still be offered in-app, but web pricing can be discounted or in-app pricing raised to encourage the web route. Web rules still apply.
Keep the hierarchy, drop the switch
Do not assume the toggle was the sole source of its gains. In one A/B test, the toggle version beat a Blinkist-style honest paywall on ARPU by 19%, yet isolating the switch showed the main lift came from supporting design choices: normalized yearly pricing, a 'Most Popular' badge, and a larger annual-plan treatment.
That distinction matters for your rebuild. Preserve the hierarchy, anchoring, and badge while removing the switch, then test the honest timeline and multi-package versions against each other. You may retain much of the performance without the compliance risk. Start now rather than waiting for an update to be rejected, and let the new champion be the design that earns a clear, informed subscription.
| Alternative | Key benefit | Compliance risk |
|---|---|---|
| Timeline / honest paywall | Builds trust, reduces complaints, reported conversion lift | None |
| Multi-package selector | Clear choice, uses price anchoring, no toggle needed | None |
| Value-first paywall | Shifts focus from price to value | None |
| Personalized / conditional paywalls | Tailored experience per user segment | None |
| Exit offer | Second chance to convert abandoning users | Low if not overly aggressive |
| Web purchase button | Full design freedom, avoids 30% commission | None (web rules apply) |
As reported in the captured evidence; test in your own app before treating figures as general results.
Frequently asked questions
Why is Apple rejecting toggle paywalls?
Apple's rejection notice, citing Guideline 3.1.2, says the purchase screen includes a toggle to add or remove a free trial and calls the design confusing because users may not understand they are committing to an auto-renewing subscription that charges after the trial. It instructs developers to remove the toggle and present a clear offer stating explicitly whether a trial is included.
Is the toggle paywall banned everywhere?
No indication was given that Google has an issue with the design, and web paywalls are not subject to App Store guidelines. A multi-platform app can therefore show a compliant toggle-free paywall on iOS and a different design on Google Play or the web, using remotely configurable targeting.
What compliant design is closest to the toggle?
Flo Health replaced the toggle with a specific 14-day free trial plan option on a multi-plan paywall, keeping 'Not sure yet?' copy. That approach appears compliant and matches user intent without a separate toggle mechanic.
Was the toggle itself responsible for the performance lift?
An A/B test comparing a toggle paywall with a Blinkist-style honest paywall found the toggle won on ARPU by 19%, but isolating the toggle showed it was not the main driver. The lift came mainly from visual hierarchy: normalized yearly pricing, a 'Most Popular' badge, and a larger annual-plan UI.