For engineering - Recurr

The technical goal is to run migration without turning it into a mobile-app roadmap item. Recurr’s default path does not require an app release. It integrates around the app: payment rail, access model, identity, branded web surfaces, and reporting.

What engineering reviews

Area	Review question
Payment rail	Stripe by default; Paddle if scoped for merchant-of-record needs
Access model	How does the app know a subscriber has paid access?
Identity	How does Recurr match web checkout to the app subscriber?
Events	What events need to be sent to the warehouse or internal systems?
Security	What data is shared, retained, and exported?

What stays out of the app

The migration flow is designed to run through owned channels and web surfaces. That means the app binary does not need to include a migration prompt, SDK, or new checkout path for the standard Nostos lane.

Common integration partners

Recurr may fit with RevenueCat, Adapty, Stripe, Paddle, Firebase, analytics tools, warehouses, or custom backends depending on the customer’s stack. The key is access continuity: subscribers who pay on web should keep using the app.