We had a stubborn drop-off on the pricing page inside the app. I moved the onboarding and payment to a web funnel so I could try different price points and page layouts without waiting on app-store reviews.
In the first week I ran three price-point variants and one simplified checkout flow. The drop-off rate on the pricing page fell by about a third for the variant that reduced choices and showed the monthly vs yearly math up front. It also let us isolate whether copy or price was the issue because we could change one thing at a time.
Has anyone else shifted checkout off the store to speed up pricing tests? How did you structure the experiments and track the win?
I did the same when installs were stuck.
I ran price A/Bs on a web funnel and measured conversion to payment the same day.
I used a small web-to-app SDK to keep user IDs in sync so the app saw the subscription right away.
Being able to change copy and price without a build saved weeks.
I moved the paywall to the web so I could run hourly A/Bs on copy and price. Changes pushed live instantly and conversions updated in our analytics.
The trick was tying the checkout session to the app user id so the app recognized purchases without delays.
This cut our experiment cycle from two weeks to a few days.
I tried pulling checkout to a web page for a fitness app.
We tested a stripped down pricing page against our full page. The simple page won and fewer people dropped off.
Timing the offer after a short onboarding survey helped too. Worth testing different moments.
Cut the store wait
Tested prices live
Results in days
We did weekly price tests on a web paywall.
We tracked both immediate conversion and 30-day retention per variant.
One price lifted conversion but churned faster. That told us to compromise on price for better LTV.
If you can change price without a new build you can iterate much faster.
Start with small sample sizes and watch retention not just conversion.