Preview and application tests
Preview lets you review the current artifact without publishing it. Its purpose and controls depend on the project route.
Web preview
Start or reopen the preview from the project stage. Use the viewport or device selector to inspect desktop, tablet, and mobile dimensions when available. Test navigation, forms, loading and empty states, error handling, and keyboard interaction. A screenshot or successful page load alone does not prove that the full app flow works.
Native preview
Native projects can render through the supported mobile preview and device-size selector. Choose a representative phone or tablet size and inspect the layout and interactions. A browser-based rendering of a Native app is a preview aid; it is not a signed iOS or Android binary and does not prove store readiness.
Application tests
Open App tests on routes that expose it, select the available checkpoint and test scope, and review the run result and evidence. Fix failed checks before treating the project as release-ready. The test panel is not available for every route; prototype design projects should be reviewed on their canvas instead of being reported as Web app tests.
Preview troubleshooting
Check whether the runtime is ready, whether the expected route loaded, and whether the browser reports an application error. Distinguish a startup failure from a blank page, failed API request, or missing test data. Capture the project and run identifiers before retrying. Never interpret a stale preview as proof that the latest source is running.