From URL to the stores
The core path: create, preview, publish, update.
The path has four steps, each with its own guide. Every step works from the dashboard, the CLI, or the MCP server.
1. Create the app
The input is the site's URL, a name, and an icon; nothing else is required. The app loads the site as it is. Create your app →
2. Preview it on a phone
Dashboard-created apps receive an installable preview within 48 hours: TestFlight on iOS, a deep link on Android, a QR code that reaches both. Apps created from the CLI or the MCP server are self-managed, skip the Appo preparation step, and are ready in minutes. See the preview →
3. Publish
Appo runs the operated publication to the selected stores: builds, submission, Apple review. Each gate requires the owner's approval. Publish to the stores →
4. Keep it updated
Web deploys reach the app without any store action, because the app loads the site. Changes to the name, icon, or splash screen require a new operated build. Update the app →
If a store review fails, Appo converts the rejection into a required action and a fix recipe: recover from a rejection.