Native mobile apps
A native project is an Expo / React Native application for iOS and Android. Cadrant generates the app with full access to native device APIs and opens the preview in a phone frame by default.
Use this mode when you need camera, push notifications, sensors, or other native capabilities — and when you want to ship a true store-native iOS app.
What you get
- Expo / React Native stack targeting iOS and Android.
- Full native APIs: camera, push notifications, sensors, and more — prefer expo-* packages.
- Phone-frame preview in Cadrant via Metro + react-native-web.
- Expo Go QR code for a quick on-device UI preview (layout and navigation only — not for validating native APIs).
- Supabase data tab: auth, database, storage and Edge Functions.
- GitHub sync and version history.
- App Store (iOS) publishing via a guided Apple Developer flow.
Create a native project
- Create a new project and open the Mobile application tab.
- Select « Native » (not « Webview / PWA »).
- Describe screens, navigation and native features in your prompt.
- Iterate in the phone-frame preview until the UX feels right.
Preview
Native preview uses Metro. Inside Cadrant, the app renders in a phone frame through react-native-web. You can also preview layout on a real device:
- Start the preview server from the project.
- Install Expo Go on your phone.
- Scan the QR code shown in Cadrant to open the live app.
Data and GitHub
Same as web projects: open the data tab for Supabase (auth, database, storage, Edge Functions), and connect GitHub for sync and version history.
Publish
Native projects are not published like a classic web app. There is no Cadrant slug or custom domain for the native binary.
App Store (iOS)
From the project header, open App Store publish. Cadrant guides you through Apple Developer sign-in, app details, certificate and build, then uploads an iOS binary to your App Store Connect account.
- The app is a true native Expo / React Native binary — not a WebView shell.
- You keep ownership under your Apple Developer account.
- Finalize listing, screenshots and review in App Store Connect.
- Validate native features on device with TestFlight before App Review.
Step-by-step: Publish to App Store Connect then Test with TestFlight.
Recommended workflow
Build and preview UI
Iterate in the phone frame, and optionally use Expo Go for a quick on-device layout check. Expo Go is not for validating native APIs.Connect backend
Wire Supabase and GitHub as needed from the data tab and project tools.Publish and test with TestFlight
Publish to App Store Connect, then install via TestFlight to validate camera, push, sensors, and other native features before App Review.
Related
- Mobile applications — choose between Native and Webview / PWA.
- Webview & PWA mobile apps — shareable URL, PWA install, App Store WebView shell.
- Publish to App Store Connect — upload the iOS binary from Cadrant.
- Test with TestFlight — validate native features on a real device.