What does supastack's Expo app include?
It depends on the plan, but the Expo app is a production mobile SaaS, not a demo: Google and Apple sign-in plus email codes, an AI assistant, a notifications inbox, biometric app lock, themes, and a RevenueCat paywall wired to the same backend and access rules as the web app. EAS build profiles for development, preview, and store submission are already configured.
The mobile half of a real SaaS
The app ships the screens a paying mobile product actually needs, not a demo with three buttons. Sign-in flows, a populated home feed, the AI assistant, a notification inbox, settings, and a RevenueCat paywall all work against the same API as the web app.
- Google and Apple sign-in plus email one-time codes, with auth deep links
- AI assistant with model and output controls
- Notifications inbox with read/unread state and compact timestamps
- RevenueCat purchases, restore, and verified access gating
- Biometric app lock and secure-store session handling
- System, light, and dark appearance modes on the shared theme system
- Push-ready notifications through expo-notifications
Built the way Expo teams expect
Expo 57 on React Native 0.86 with Expo Router file-based navigation, typed API calls into the hosted backend, and EAS build profiles for development, preview, and store submission.
Sessions sync through secure storage and auth deep links, so a user who buys on the web unlocks on the phone, and a user who buys in the app shows up in your web admin.
- Expo + React Native
- EAS Build + Submit
- RevenueCat
- TypeScript + Turborepo
- Better Auth
- iOS + Android
From clone to the stores
Point the app at your deployed API, run it in Expo Go or a dev build, and it boots with real screens instead of placeholders. EAS profiles and the store-submission guides walk you from first build to TestFlight and Play Console review.
- Dev, preview, and production build profiles already configured
- RevenueCat and push guides cover the store-specific setup
- App lock, deep links, and theming work out of the box
Common questions about the Expo app
- How do payments work on mobile?, Through RevenueCat in-app purchases, the store-required path for digital goods. Purchases, restores, and entitlement gating are wired to the same access rules as web billing.
- Do I need a Mac to ship the iOS app?, No. EAS Build compiles and signs iOS builds in the cloud; the submit guide covers App Store review. A Mac is only needed if you want a local simulator.
- Does the mobile app work without the web app?, The app talks to the hosted API, the same Next.js or TanStack Start deployment that powers your website. Ship them together and every screen is backed by real data.