The mobile industry has spent more than a decade treating the App Store install as a fixed constraint — designing growth engines around it rather than questioning it.
It isn't a law of nature.
It never was.
It's simply how things worked — until the economics stopped working.
The truth is simple:
Installs don't build businesses. Revenue does.
And yet the ecosystem still optimises around store rails it doesn't control. Margin is surrendered to systems that add friction without proportional value. Pricing experiments wait on app releases. Subscriber relationships sit inside accounts the app doesn't own. Identity, billing, lifecycle — the parts of a subscription business that should be a product team's most flexible levers — operate inside opaque systems no one can inspect or evolve.
Beneath all of this sits the real structural flaw:
Mobile never owned its commercial layer.
SaaS companies have long benefited from a full commercial stack — landing pages, trials, pricing experiments, lifecycle automation, payment recovery, analytics that operate on rails the company controls.
Mobile skipped this entirely.
The App Stores absorbed that role, and the industry built a decade of tooling around a funnel no one could truly own. Every mobile subscription company now operates inside that constraint — a system designed for a different era, with economics that no longer scale.
That era is ending.
What's driving the shift isn't ideology — it's operational reality. As mobile subscription businesses scale, store-billing infrastructure stops being a default and becomes a liability surface. 15-30% of every dollar disappears into platform fees. 60-day settlement lags strangle cash flow. Subscriber relationships are mediated by an account the app didn't open and can't close. Pricing flexibility is gated on review timelines.
At that scale, how revenue is captured matters as much as how much.
Web subscriptions aren't experimental anymore.
Spotify, Netflix, and a growing cohort of mobile apps already run their subscriptions on the web. The constraint is no longer whether consumers will buy there — it's whether your app is set up to meet them.
Apple's own guideline 3.1.3(b) permits qualifying apps to direct subscribers to web purchase. The DMA designated Apple a gatekeeper. Korea passed an alternative-billing law. When the path required bespoke infrastructure, only the largest apps could afford to walk it. The rails are now general-purpose.
Most of the market hasn't moved yet — not because the opportunity is unclear, but because the operational work required has been expensive, risky, and difficult to do well. Cohort selection, retention safety, churn modeling, store-policy compliance, identity continuity, support readiness, billing reconciliation. The work isn't in the primitives. The work is in everything around them.
That work has stayed inside the rare apps with the engineering capacity to build it themselves. Recurr is bringing it to the rest of the market.
Recurr is the platform for app-to-web subscriber migration — the operational work of moving mobile subscription businesses out of store-billing constraints and onto rails they own.
Migration is where it starts. We bring an existing subscriber base from app-store billing to web checkout, cohort by cohort, measured against a matched IAP holdout, scaled only when retention, payback, and operational metrics clear agreed thresholds. The Controlled Migration Framework codifies the work that until now has lived inside the small set of apps with the engineering bandwidth to build it themselves.
Migration is also the substrate. Once subscribers are on web rails, a different operating model becomes possible. The lifecycle plays that web SaaS has used to compound subscriber LTV for the last decade — cancel deflection, win-back, pricing experimentation, payment recovery, ascension — were never available inside the store sandbox. They are now.
Apps that move to Recurr aren't just recovering the margin trapped behind store fees. They're stepping out of the constraints that capped what they could do with the subscribers they already have.
We believe mobile subscription companies deserve:
- ownership of their subscriber relationship
- control over their billing rails
- visibility across the full revenue lifecycle
- the ability to experiment on price and offers without store-policy gating
- and margins that scale with the value they create
And we believe the web — not the App Store — will be the primary operating layer for mobile subscription revenue. Not because anyone needs to leave the stores; the stores remain great distribution. Commerce and distribution are different jobs, and they don't have to share infrastructure.
The first cohort of customers to make this transition with us are Design Partners. They get the work done by the founder, end to end. Matthew is on every Migration Review, every pilot kickoff, every go-live. There is no sales engineer handoff. The framework will absorb a delivery team eventually — but the early customers get the people who designed it.
This shift extends beyond the immediate economics.
Commerce surfaces shift. They always do. The apps that own their subscriber relationship — their data, their payment rails, their lifecycle tooling — will be ready when the next surface emerges. The ones whose commerce runs through a marketplace they don't control will be waiting for the marketplace to permit them.
We don't know exactly what comes next. We have ideas. But the right move for any subscription app today is to stop building toward a future where someone else gets to set the rules.
Recurr begins as the migration platform. Over time, it becomes the revenue infrastructure that supports the strategies a subscription business should be able to run on its own terms — without forcing teams into brittle, bespoke internal builds.
We are here to replace defaults that no longer scale.
To eliminate friction that was never essential.
To bring clarity, ownership, and operational control back to mobile revenue.
The web-first era of mobile revenue has already begun.
Recurr exists to make that transition safe, measurable, and operationally sound.
— Matt
