Getting Started
Previewing Your App
Use Mock preview, Flutter Web preview, and a real Android build for progressively more accurate testing.
Before you start
- Saved app configuration
- A website that permits loading in the preview environment
Configure and verify
Start with Mock
Open Preview and choose Mock for a quick shell layout check. Test light and dark mode plus phone and tablet sizes.
Generate Flutter preview
Choose Flutter. The latest generated preview is shown when available. Select Refresh to compile an updated preview from saved settings.
Watch progress
All users see progress and the current step. Admin users can also inspect detailed preview worker logs.
Recognize browser limits
Camera, biometrics, native downloads, Play Billing, push, and some WebView behaviors cannot be fully validated in browser previews.
Test the APK
Install a fresh Android APK and retest permissions, downloads, deep links, authentication, notifications, media, and back-button behavior.
Preview accuracy
- Mock
- Fast visual approximation; no compilation
- Flutter Web
- Compiled shell layout and saved assets; browser limits remain
- APK
- Final Android manifest, dependencies, signing, and device APIs
Refresh behavior
Flutter preview uses per-app output and unique asset filenames. Selecting Flutter does not rebuild automatically; Refresh generates a new version.
Admin emulator
Run on Emulator, worker diagnostics, and stream controls are admin-only. Live scrcpy/MediaMTX streaming can fall back to HTTP screenshots.
Test before release
- Saved settings match the preview
- Both themes were checked
- Navigation does not cover website controls
- A final APK was tested on a physical device