Skip to main content
Back to Documentation

Preview & Testing

How to preview your Mobiforge app on a real device or in the browser.

Three ways to preview

Mobiforge gives you three ways to see your app: a web preview in the browser, Expo Go on your physical device for fast JavaScript iteration, and native builds (APK/IPA) for full testing of native features and store submission readiness.

Web Preview

The built-in web preview lives in the right panel of the builder. It runs your app inside a mobile-frame iframe directly in the browser — no installs, no QR codes. Every time the AI finishes an edit, click the refresh button to see the updated version instantly.

Best for

  • Rapid UI iteration between AI edits
  • Checking screen layout and navigation flow
  • Verifying that data loads from Supabase correctly

Web preview runs Expo on the web and may not reflect native behavior exactly. Always validate on a real device before shipping.

Expo Go (device preview)

Expo Go lets you run your app on a real iOS or Android device over Wi-Fi without needing a full native build. It's the fastest way to feel your app on real hardware.

1

Download Expo Go

Install Expo Go from the App Store (iOS) or Google Play Store (Android) on your device.

2

Click the Expo Go button

In the Mobiforge builder top bar, click the "Expo Go" button to generate a live preview link.

3

Scan the QR code

On iOS, scan with your camera app. On Android, open the Expo Go app and use its built-in QR scanner.

4

Your app loads live

Expo Go bundles your app over Wi-Fi. Your device must be on the same network as the Mobiforge preview server.

Expo Go runs JavaScript only. Native modules — including Stripe payments, push notifications via APNs, and some camera APIs — require a native build to work correctly.

Native builds

For full-feature testing and App Store / Play Store submission, you need a native build. Mobiforge compiles native binaries in the cloud — no Xcode or Android Studio required on your machine.

Android — APK / AAB

APK for direct device install during testing. AAB for Google Play Store submission. No signing credentials required for debug APKs.

iOS — IPA

IPA for TestFlight distribution and App Store submission. Requires App Store Connect API credentials configured in your project settings.

See the iOS Build Setup and Play Store guides for step-by-step credential configuration.

Tips for testing

Test on a real device early

Web preview misses native behaviors like gestures, keyboard handling, and platform-specific UI patterns.

Use Expo Go for fast iteration

Expo Go reloads in seconds. Use it between AI edits before committing to a full native build.

Native builds take 5–15 minutes

Cloud compilation queues can vary. Kick off native builds early when you need them for demos or reviews.

Always test native features natively

Auth, payments, camera, and push notifications must be tested on a native build — not web preview or Expo Go.