Apple and Google manage their own subscription events, billing rules, receipts, and renewal behavior. Azotte make consistents those events into the same lifecycle and access model used by web, partner, and regional storefronts.
The goal is not to bypass app stores. The goal is to prevent app-store records from fragmenting subscription operations.
Each row shows who manages what, how Azotte changes it, and what happens when you move.
| Aspect | Current way | Azotte way | What changes |
|---|---|---|---|
| Lifecycle events | Apple and Google emit different event shapes and renewal states. | Store events become made consistent lifecycle states inside Azotte. | Map receipt events, grace periods, refunds, expirations, and renewals. |
| Entitlement authority | Access often follows app-store product and receipt state. | Access is defined once, then connected to store, web, and partner purchases. | Map products to access bundles and validate active access. |
| Storefront handling | Each app store behaves as its own subscription channel. | App stores become storefronts inside a broader way of working. | Link app-store users to shared customer identity when needed. |
| Payment control | Payment capture remains inside Apple and Google. | App-store payments coexist with PSP, partner, invoice, and wallet flows. | Keep store payment authority while normalizing subscriber state. |
| Regionalization | Store pricing and availability follow app-store constraints. | Regional rules can coordinate app-store, web, and partner offers. | Document where store rules govern price, tax, consent, and availability. |
This comparison is about making systems consistent. App stores continue to govern their rails; Azotte governs the cross-channel subscription record.
