Mobile App Backend in PHP
Own the API behind your native app.
What you get
The app-backend profile provides bearer-token sign-in, a user profile endpoint and per-user item CRUD. Apple and Google identity tokens are signature-checked against provider keys, then checked for the expected claims and nonce. App tokens are stored as peppered hashes in the backend database.
The tradeoffs
The included SwiftUI and Compose source projects demonstrate sign-in, profiles, items and RevenueCat subscriptions. They are configurable source templates. You still need application identifiers, provider configuration, signing, store products and device testing. The browser operator demo does not prove a live store purchase.
What to try first
Start by running email-code sign-in against a local backend. Add one product-specific resource and test that one user cannot read another user’s data. Then configure native identity providers and test purchase, restore, account switching and deletion before release.
Try before choosing
The live demos use sample data and simulated payments. The download includes the source and setup guides; your own launch still needs provider configuration and end-to-end testing.
Explore the demos · Price, licence and requirements · All guides