6 min read
Backend for an Expo app: auth, subscriptions and push
What an Expo app needs from a backend: verified sign-in tokens, server-side subscription checks, stored push tokens, and secrets kept out of the bundle.
4 articles from the Edict blog cover mobile app subscriptions. The newest comes first.
6 min read
What an Expo app needs from a backend: verified sign-in tokens, server-side subscription checks, stored push tokens, and secrets kept out of the bundle.
8 min read
Give free and paid users different AI limits by routing model calls through your own gateway, metering usage in Postgres, and never embedding a key in the app.
9 min read
A mobile app should not decide on the device what a user paid for. Verify purchases on a server and keep entitlements in a table fed by store notifications.
8 min read
Test trials, renewals, billing retry, expiry and refunds with StoreKit files, sandbox accounts and seeded backend state before any real money moves.