Power your mobile app

Tools that power the Power your mobile app stack

• Supabase — Backend and auth

  Instant REST and realtime APIs plus built-in auth for mobile apps

  See all stacks using Supabase

• Expo — Mobile framework

  Build and deploy React Native apps to iOS and Android from one codebase

  See all stacks using Expo

• OneSignal — Push notifications

  Send targeted push notifications to iOS and Android users

  See all stacks using OneSignal

Setup guide

1. Supabase: Configure Supabase tables and ownership RLS policies for the mobile app. Use a publishable/anon client key, never a service-role key. Configure the auth storage adapter for the chosen Expo storage solution using the current integration guide, and test login, refresh, logout and cross-user data denial on a device. (Read official instructions)
2. Expo: Configure Expo using documented EXPO_PUBLIC variables for intentionally public client configuration or explicit app.config extra values read through the matching API. Values shipped in the app are not secrets. If using SecureStore for auth persistence, wire up a compatible adapter rather than assuming installation enables it. Test a development build on each target platform. (Read official instructions)
3. OneSignal: Follow OneSignal's current Expo setup for both onesignal-expo-plugin and react-native-onesignal, using compatible pinned versions. Expo Go does not support this setup: use a development build and check the guide's Expo SDK and architecture requirements. Configure APNs/FCM credentials, request permission and associate subscriptions with your signed-in user using the current user model. Test delivery and logout on supported devices. (Read official instructions)

   Check: On each supported device, login persists and refreshes correctly, logout removes access, cross-user data requests fail, and push reaches only the intended test user.