How to convert a URL to an app, step by step

Step by step

1. Check the URL on your phoneOpen it in mobile Chrome. Menus, forms and checkout should work one-handed; if they don't, fix the site first.
2. Pick the exact start URLUsually the home page, sometimes a dashboard or /app path. Use the final https:// address with no tracking parameters. How to choose.
3. Install a URL to App converterGet Website to App from Google Play and paste the URL.
4. Name the appA short name (about 12 characters shows in full under the icon) plus a longer Play title. Try the launcher label preview.
5. Set the package nameReverse your domain: shop.example.com → com.example.shop. It can never change after publishing. Generate one.
6. Add icon and coloursA square 512×512 icon with padding, plus a theme colour for the status bar. Test the colour.
7. Decide the link scopeYour domain stays in the app; social, maps, phone and email links open their own apps. Test your links.
8. Build, install, testBuild in the cloud, install the APK, then test login, uploads, payments and the back button before publishing the AAB.

Before you start: a 60-second URL check

Most failed URL apps fail because of the URL, not the converter. Run the address through the start URL inspector and confirm:

• It's https. Android blocks plain http:// traffic in apps by default.
• It doesn't redirect three times. Use the final address you land on.
• It has no session tokens or UTM tags baked in. If you want to measure app traffic, add one clean parameter like ?source=android_app on purpose — the app UTM builder does it properly.
• It works logged out. First-time users arrive with no cookies.

Choosing settings that are hard to change later

Three settings stick to your app for life, so get them right on the first build:

1. Package name. Google Play identifies your app by it forever. Changing it means a brand-new listing with zero installs and reviews.
2. Signing key. Every update must be signed with the same key (or the upload key Play knows). Download and back up the keystore the converter gives you.
3. Version code. Each update needs a higher whole number than the last. Start at 1.

Everything else — name, icon, colours, start URL — can change in a later version.

Testing the APK like a user would

Install the APK (allow “install unknown apps” for your file manager or browser when asked) and walk through the five things users do in the first minute:

1. Open the app with mobile data on and Wi-Fi off — is the first screen fast?
2. Sign up and sign in. If you use Google sign-in, read why it fails in WebViews.
3. Upload a photo from the camera and from the gallery.
4. Tap an external link (Instagram, WhatsApp, a phone number) — it should open the right app, not a page inside yours.
5. Press back repeatedly. It should step back through pages, then leave the app — never trap the user.

Publishing the AAB on Google Play

Create the app in Play Console, upload the AAB to a testing track, fill in the store listing, data safety form and content rating, then roll out. New personal developer accounts must run a closed test with real testers for two weeks before production access. Read Play policy for URL apps before you submit — it's the most common reason website apps get rejected.