Frameworks
Frameworks
Pick your framework for build and session setup, and see which frameworks hot reload.
Pick your framework to see how to build it and open it in a Revyl session.
Web
- Web overview and deployed previews
- Next.js
- Vite
- Any other framework — Remix/React Router, Nuxt/Vue, SvelteKit, Astro, Angular, and plain static sites can use the generic Web setup with a compatible static or self-contained server bundle, or an existing HTTPS preview. Author the recipe yourself; Revyl does not detect these frameworks or provide Web hot reload.
Mobile
- iOS Native (Swift)
- Android Native
- React Native (bare)
- Expo
- Flutter
- Kotlin Multiplatform (including Compose)
- Bazel
- Any other framework — Capacitor/Ionic, .NET MAUI, NativeScript, and Unity can use the
mobile quickstart's artifact-upload path if you produce a
compatible simulator
.appor emulator.apk. There is no framework-specific setup detection or hot reload for these apps; rebuild and upload after changes.
Mobile apps use the Revyl dev loop.
Hot Reload vs Rebuild
Web
| Framework | Dev Loop Model | When to Rebuild |
|---|---|---|
| Next.js | Build a standalone server bundle | Rebuild and open the new build after a code change |
| Static Vite | Build a static bundle | Rebuild and open the new build after a code change |
| Any deployed Web framework | Register the hosted HTTPS preview | Deploy the change, register the preview URL, and open that build |
Web does not use a Revyl hot-reload provider.
Mobile
| Framework | Dev Loop Model | When to Rebuild |
|---|---|---|
| Swift/iOS | Rebuild on every change | Every code change (binary is the app) |
| Android Native | Rebuild on every change | Every code change (binary is the app) |
| React Native (bare) | Hot reload (JS/TS changes are live) | Only when native dependencies change |
| Expo | Hot reload (JS/TS changes are live) | Only when native dependencies change |
| Flutter | Rebuild on every change | Every code change (Dart compiles into the binary) |
For Expo and React Native, the uploaded build is a "dev client shell" -- your JS/TS code is served live from your local Metro server via a Revyl relay. For Flutter, Swift, and Android, the binary is the app.
Platform Build Requirements
Web
| Platform | Requirements |
|---|---|
| Web bundle | One dedicated output directory. Static output needs a root index.html; server output needs its runtime dependencies and an explicit run.start. See Web builds. |
| Web deployment URL | An existing HTTPS preview, with no URL credentials, query string, or fragment. See deployed previews. |
Mobile
| Platform | Requirements |
|---|---|
| iOS and Android | A simulator .app or an emulator-compatible .apk. See Build Artifact Requirements. |
The mobile frameworks' default debug builds satisfy their artifact requirements. For custom
configurations — narrowed abiFilters, release builds, or .ipa archives — check the
full rules and trade-offs.
Hot reload and rebuild configuration
Web
Web recipes are authored explicitly; revyl init does not detect Next.js, Vite, package managers,
or preview hosts.
| Framework | Hot Reload | Rebuild Dev Loop | Provider Name |
|---|---|---|---|
| Next.js | Not supported | revyl build --profile preview --platform web, then start a new session | — |
| Vite | Not supported | revyl build --profile preview --platform web, then start a new session | — |
| Deployed Web preview | Not managed by Revyl | Register the updated preview URL, then start a new session | — |
Mobile
revyl init best-guesses mobile build and dev-loop configuration.
| Framework | Hot Reload | Rebuild Dev Loop | Provider Name |
|---|---|---|---|
| Swift/iOS | — | [r] rebuild + reinstall | swift |
| Android Native | — | [r] rebuild + reinstall | android |
| React Native (bare) | Fully supported | [r] for native changes | react-native |
| Expo | Fully supported | [r] for native changes | expo |
| Flutter | — | [r] rebuild + reinstall | — |
| Kotlin Multiplatform | — | [r] rebuild + reinstall | — |
| Bazel | — | [r] rebuild + reinstall | — |
Bazel and Kotlin Multiplatform are detected as build-tool or layout signals,
not as supported build.framework values. A project with both native apps
uses framework: ios and builds each recipe for its own platform.
Dev Loop Framework Troubleshooting
Web
| Symptom | Cause | Fix |
|---|---|---|
Web: no recipe after revyl init | Web setup is manual | Create a Web app and add the Next.js or Vite recipe, or register a preview |
Web: profile <name> is URL-only | The profile has an app ID but no managed build recipe | Register the preview URL, or add explicit build_commands and output_path |
| Web: server health check fails | The server is bound to localhost or the health check does not return 2xx or 3xx | Bind to 0.0.0.0; match run.port and run.healthcheck to the app |
| Web: static bundle rejected | No root index.html in the output directory | Point output_path at the built static site, not the source directory |
Mobile
| Symptom | Cause | Fix |
|---|---|---|
| "Detected Swift/iOS instead of Expo" | Detection ran outside the Expo app root or expo is absent from its local package.json | Run revyl init --detect from the app directory; if needed, edit build.framework and the generated profile, then validate |
| "Detected Android instead of Expo" | Detection ran outside the Expo app root or the native directory won an ambiguous match | Run revyl init --detect from the app directory; if needed, edit build.framework and the generated profile, then validate |
| "No providers detected" | Missing package.json, wrong directory, or no framework indicators | cd to the app directory; verify package.json has expo or react-native |
| "App scheme empty" | The Expo app config does not resolve a custom scheme | Configure expo.scheme in the app, rebuild the dev client, and use the new build |
| "No runnable development recipe" | The project config has no usable profile/platform recipe | Edit the generated named profile and run revyl config validate |
| "Port 8081 is already in use" | Another Metro instance running | lsof -ti:8081 | xargs kill or --port 8082 |
| "No application is registered to handle this URL scheme" | The installed dev client does not register the scheme recorded with the build | Correct the Expo app's scheme/generated-scheme settings, rebuild, and use the new build |
| No URL scheme in the app | App only uses universal links | Add "scheme": "myapp-dev" to app.json, rebuild dev client |
| No eligible iOS or Android recipe | The selected named profile lacks that platform recipe | Edit the profile in .revyl/config.yaml, then run revyl config validate |
Deep link fails with LSApplicationWorkspaceErrorDomain error 115 | The URL scheme in the deep link doesn't match any installed app | Same as "No application is registered" above |
| App closes briefly after tapping "Open" in the dialog | Normal: dev client is reloading to connect to Metro via tunnel | Wait for it to reopen; if it doesn't, check Metro output for JS errors |
| "Open in [App Name]?" confirmation dialog | iOS system prompt for URL scheme handoffs | Tap "Open" to proceed; this is expected behavior |