👀 Preview and publish
Test the real app before shipping it to users.
The preview is the main place to verify Ada’s work. It should behave like the app, not like a static design.
Test in the preview
Section titled “Test in the preview”Check the changed screen and the complete path around it:
- Navigate through the normal user journey.
- Verify login, signup, logout, and data changes when they apply.
- Check loading, empty, and error states.
- Test mobile and desktop layouts.
- Confirm camera, microphone, location, maps, payments, and notifications when the app uses them.
The preview can show a live app beside the chat and can open the app on a phone through a QR code. A paused preview should explain its state and provide a way to wake it.
Publish targets
Section titled “Publish targets”One project can produce:
- A web app.
- An Android build that can be downloaded or sent to Google Play.
- An iOS build sent to TestFlight and prepared for App Store Connect.
The publish area should show build progress, readable version information, status, history, and downloads. A build that is still running should remain understandable if the tester leaves the page.
Updates
Section titled “Updates”Many content and design changes can be delivered as updates to installed apps without another store review. Changes involving native device features or new permissions may require a new build.
Test the published experience separately from the preview. Do not treat a successful preview as approval for a production release.