How GRTV uses web billing to power app-to-web subscriptions
A horse-racing app that ran for two years without monetization added subscriptions in early 2025, pairing in-app purchase with a web checkout for U.S.
iOS users. This page explains the decision pattern — stack fit, payment choice, and peak-traffic readiness — so you can judge whether the same approach suits your own app.
What is GRTV
{{OWNER_CUSTOMER_NAME}} is a horse-racing app founded by Venezuelan race announcer Gustavo Ravell, providing real-time data, statistics and coverage from racetracks worldwide. After two years without monetization, the team introduced subscriptions in early 2025 to give its most engaged fans premium access to live race data and enhanced features around peak events. The lesson for other teams: monetization can start with the users already showing the strongest intent, rather than redesigning the whole product at once.
Introducing subscriptions while keeping the product on track
With a small distributed team and a growing audience, building a subscription system from scratch would have pulled time away from the product itself. The team chose a managed platform instead, citing out-of-the-box support for Flutter and Firebase and robust analytics. Its backend already ran on Firebase, so the integration fit the existing architecture rather than forcing a rebuild. Decision checklist: (1) Does the platform support your app framework and backend today? (2) Can you manage entitlements without new infrastructure? (3) Does analytics cover both in-app and web purchases in one place?
Offering purchase flexibility with app-to-web
When U.S. developers became able to link out to web-based purchases, the team added a web checkout option reachable directly from the in-app paywall. Customer research behind the decision found many users preferred not to rely on a pre-loaded card in their Apple account and wanted to pick whichever card suited them at that moment. The Web Purchase Button made this straightforward: tapping the link opens a secure hosted checkout, the purchase completes on the web, and the user returns to the app with access unlocked. Web billing supports Apple Pay, Google Pay and manual card entry in a mobile-optimized flow, so teams can offer all three and let users choose. Failure distinction to keep clear: adding a web option is not the same as removing in-app purchase — the value here came from offering both and meeting users where they already were.
Off to the races with reliable purchases
The 2025 Kentucky Derby was the app's highest-traffic week to that point, with thousands of fans arriving to search race data and subscribe to premium features. Search, data access and payment all continued to work through the spike, which gave the team confidence to grow without worrying about backend reliability during marquee events. For your own launch, treat a flagship event as a load test: confirm checkout, entitlement sync and support coverage before the peak, not during it. {{OWNER_CUSTOMER_OUTCOME_AND_DATE}}
Ready to grow?
Use this page as a template for your own story: name the audience and the moment subscriptions were introduced, show the stack fit, explain the payment-choice pattern, and give a dated peak-traffic reference point. Replace every {{OWNER_...}} variable with verified details before publishing, and confirm current store-policy eligibility for app-to-web linking in your market.
| Decision point | What the example did | Check for your app |
|---|---|---|
| Build vs. buy | Used a managed platform instead of building subscription infrastructure | Team size, maintenance capacity, stack fit |
| Payment choice | Added web checkout alongside in-app purchase for U.S. iOS users | Store-policy eligibility, user card preferences |
| Peak readiness | Checkout and data access held during Kentucky Derby traffic spike | Load testing before flagship events |
Dated unverified reference pattern; confirm current policy and platform availability.
Frequently asked questions
How does app-to-web checkout work in this example?
The pattern described is: offer in-app purchase alongside a web checkout reachable from the paywall for eligible U.S. iOS users, so people who prefer not to use a card saved to their Apple account can choose a different card on the web, then return to the app with access unlocked. Confirm current store-policy eligibility and payment-method availability for your own app before implementing.
Why use a managed platform instead of building subscriptions in-house?
The team cited ready-made support for its existing stack — Flutter for the app and Firebase for the backend — plus analytics, as reasons to use a managed subscription platform rather than building and maintaining purchase and entitlement infrastructure in-house with a small distributed team.
What happened during the peak-traffic event?
During the 2025 Kentucky Derby, described as the app's highest-traffic week to that point, search, race-data access and subscription purchase continued to work through the traffic spike. Treat that as a dated, unverified reference point for load planning, not as a guarantee for other apps or events.