Preview Overview
Run and test your generated web or Flutter app, preview changes, and check it before publishing.
Preview Overview
How Preview Works
When VULK generates or edits your app, the preview panel runs the generated project. You can interact with its screens, navigation, forms and other controls. You do not need to write code to create the app or request changes; the generated source remains available to inspect and export.
Web apps
Web projects use the preview runtime for their target and dependencies. For example, React/Vite projects run their generated application in the browser. A project's runtime, backend connections and configuration determine what can be exercised in its preview.
React Native/Expo apps
React Native/Expo apps copied from the gallery have a browser preview. Open the copied project, test its interactions and inspect the source. See Creating Mobile Apps for the supported workflow.
Flutter apps
Flutter projects have a compiled web preview. VULK compiles the Dart/Flutter project for the browser and serves the resulting app in the preview panel. You can test screens, navigation, state and interactions in that compiled build.
The browser preview and an installed iOS or Android build are different test environments. Test device-specific permissions, platform integrations and native behavior on the target device as part of your release checks. See Creating Mobile Apps and Publish to App Stores.
How Updates Work
Describe the change in chat. VULK updates the project files, prepares the updated preview and refreshes the preview panel. Flutter changes go through compilation before the new browser build can be shown.
Wait for the change and its preview to finish before checking the result. Loading time depends on the target, dependencies and size of the change. A preview URL, a successful compilation and a working user journey are separate checks: interact with the updated app before publishing it.
Preview Features
- Live rendering — Your app runs in a real browser environment
- Responsive testing — Toggle between desktop, tablet, and mobile views using the device icons
- Interactive — Click buttons, fill forms, navigate between pages and scroll to test the generated behavior
- Open in new tab — Click the external link icon to test your app in a full browser window
- Console output — Errors and logs from your app are captured and shown in the editor
Preview Panel
The preview panel shows your running app inside the editor. Its layout adapts to the available screen space.
Controls
- Reload — Force a fresh reload of the preview
- Device toggle — Switch between desktop, tablet, and mobile viewports
- New tab — Open the preview URL in a separate browser tab
- URL bar — Shows the current preview URL (useful for sharing or debugging)
What to Expect
- Preview starts automatically when you create or open a project
- The first load prepares the target's runtime or compiled build
- After generation, the preview refreshes automatically with your new files
- If the preview shows a blank screen, try clicking the reload button
- External API calls from your app work normally (subject to CORS)
Differences from Production
The preview environment is optimized for development speed, not production performance:
| Aspect | Preview | Production (Deploy) |
|---|---|---|
| Purpose | Test the current project while you build | Share the version you publish |
| Web project | Running web preview | Published web build |
| Flutter project | Compiled browser preview | Published web build or a separate native release |
| URL | Project preview URL; access may require your VULK session | Published address shown by VULK or your custom domain |
| Updates | Refreshes as project changes are prepared | Updated when you publish a new version |
| HTTPS | Yes | Yes |
Troubleshooting
If your preview is not loading, see Preview Not Loading.