# Create, preview, and publish your website app
Start with a website you own or have permission to use. Your website supplies the content and functionality; SiteTo.App adds the app name, icon, navigation, and optional push notifications around it.
1. Add your website URL
Start a free preview. Enter your public, mobile-friendly website address. The builder attempts to extract its name, logo, and suggested navigation. Review the suggestions; automatic extraction may miss links or choose a title you want to change.
If extraction fails, check that the website opens in a normal browser, uses a public URL, and is not behind a login or bot challenge. You can retry, choose Skip auto-fill to set things up yourself, or contact support with the public URL. Never send private credentials.
2. Test the preview and navigation
The next step provides a phone preview. Scan the QR code with your phone, or use the preview link on the phone you are already using. Follow the installation instructions if the preview application is required, then return to the link or QR code.
Test the journeys your customers actually use:
- Open your home page and navigate back from another page.
- Sign in, sign out, and recover an account.
- Complete your checkout or booking flow in its test mode, if available.
- Open external links and test uploads or downloads you depend on.
- Check the keyboard, cookie banners, and small-screen layout.
A connection to the preview is not proof that every website feature works. External authentication and payment flows need particular attention.
3. Create your app
Select Create my free app on the preview step. If you aren't signed in yet, you sign in first and the app is created as soon as you return. Creating an app is free and separate from purchasing. If you selected Android, iOS, or both on the pricing page, that choice carries forward; you can review it before payment.
4. Make it yours in the dashboard
Your new app opens in the dashboard with the extracted name, logo, and menus. From there you can change the app name and identifier, add your icon and launch screen, and edit the side, footer, and header menus at any time before building.
5. Choose a paid build
Android is $29 USD, iOS is $79 USD, and both are $99 USD as one-time app-build prices. Developer accounts, website hosting, and paid external services are separate. Review pricing and publishing responsibilities before paying, including questions about future rebuilds or a specific launch deadline.
6. Prepare your store accounts and build
Open your app in the dashboard. For iOS, connect your Apple Developer account so SiteTo.App can sign the build and upload it to TestFlight. Connecting Google Play is optional for Android. Complete the required publishing configuration. Follow the Apple account guide or Google Play account guide.
If you want push notifications, follow the Firebase setup guide. Complete the necessary platform configuration before requesting a build that uses it.
Request builds from the app's Build & publish screen. iOS builds are uploaded to TestFlight in your App Store Connect account. Android builds produce an APK for direct installation or an AAB for Google Play, and you download them from the build history. Test the generated app before submitting it. A successful payment, a completed build, and an approved store listing are separate milestones.
7. Submit to the stores and respond to review
SiteTo.App builds your app but does not submit it to the stores. You submit it yourself: for iOS, select the TestFlight build in App Store Connect and submit it for App Review; for Android, upload the AAB to a Play Console release. You create and own the store listings.
Prepare screenshots, your app description, support details, and accurate privacy disclosures. Supply reviewer access if your app requires an account. Apple and Google decide whether to approve the submission; adding an app icon alone does not guarantee approval.
Read the publishing guide for the preparation checklist. If a reviewer asks for changes, use the specific feedback to identify the affected website content, app configuration, or listing information.
Need help?
Contact support with your public website URL, chosen platform, the step you reached, and what happened. Do not include passwords, store private keys, or payment information.