Website to APK Without Coding: What Actually Works

Use a no-code builder. You paste your website’s address, pick a name and an icon, and it hands back a signed APK you can install on your phone. If your site is already a Progressive Web App, PWABuilder does the same job with a Trusted Web Activity. Building the APK takes minutes. Getting it accepted on Google Play is where most of the work is.

Search Reddit for this and you’ll see the same pattern. Someone asks for the easiest tool, and the replies turn to Play Store rejections, lost signing keys and login screens that break inside the app.

The two no-code routes

1. A WebView builder

Most “website to APK” tools build a WebView app. Android’s documentation describes WebView as a view that “lets you display web pages as a part of your activity layout.” It also “doesn’t include the features of a fully developed web browser, such as navigation controls or an address bar.”

The app is a thin shell. Your pages, logins and checkout still run on your server; the shell adds an icon, a full-screen view and some navigation. Edit your site and the app shows the change at once. Rename the app or swap its icon, though, and you have to build and install a new version.

It works for any HTTPS site, with no manifest, no service worker and no changes to the site’s code.

2. A Trusted Web Activity through PWABuilder

A Trusted Web Activity opens your web app from an Android app using a protocol based on Custom Tabs. Your site runs in the user’s own browser, full screen, rather than in an embedded view. It works in Chrome on Android version 72 and above, and the app can’t reach into your pages, so cookies and other web data stay with the browser.

The catch is ownership. Chrome expects the app and the site to come from the same developer and checks this with Digital Asset Links, a file you upload to .well-known/assetlinks.json on your site. If the check fails, the quick start guide says your site opens “as a Custom Tab with browser UI at the top of the page.” Your users see a browser window, not an app.

Developers build these with Bubblewrap, a command-line tool that needs Node.js 18.0.0 or above: bubblewrap init with your manifest URL, then bubblewrap build. That is code. PWABuilder puts a form in front of it. Its team wrote in July 2020 that it uses Bubblewrap under the hood.

Take this route only if your site is already a real PWA with a working manifest. If you’d have to build that first, you’re coding after all.

What people run into after the APK works

Google Play’s webview rule

In October 2020 Google wrote that it sees “a large volume of app submissions that are just webviews of existing websites,” and that “such apps are considered webview spam, and are removed from Play.”

The current spam policy bans apps whose main purpose is to drive affiliate traffic to a website, or to show a webview of a website without permission from its owner. The functionality policy adds: “We do not allow apps that only have limited functionality and content.”

Wrap a site you own, and give the app a reason to exist: offline pages, faster paths to the parts people use most, a layout built for a phone. A one-page brochure site in a shell is the classic rejection.

The signing key

Every build is signed, and whoever holds the key controls updates. PWABuilder’s 2020 post lists three choices: leave the package unsigned so Google Play signs it, let PWABuilder generate a new key and include it in the download, or upload your own .keystore. Back up the key and its password the day you get them. More on the risks in whether an online APK converter is safe.

Logins, uploads and links

A WebView isn’t Chrome. JavaScript is off by default in a raw WebView, which is why home-made wrappers often show a blank page. Builders switch it on, but sign-in pop-ups, file uploads, downloads and links to other domains can still break. Test each of those on a real phone before you share the APK.

The cost of Google Play

Building can cost nothing. Publishing can’t: Google charges a US$25 one-time registration fee. Personal accounts created after November 13, 2023 must also run a closed test with at least 12 testers opted in continuously for at least 14 days before going to production. Finding 12 people is often slower than building the app. There’s more on the free and paid parts in can I convert my website to an Android app for free.

Which one I’d pick

If your site is a solid PWA and you’re publishing on Google Play, use the Trusted Web Activity. Your users get their real browser, and the pop-up and upload quirks above go away.

For a plain HTTPS site, a small business page, an internal tool you’ll install yourself or a folder of offline HTML pages, a WebView builder is quicker and asks less of your site. That’s the gap WebToAPK Free covers. It runs in your browser, needs no account, outputs both a signed APK and an AAB, and keeps the project and private signing key on your device instead of uploading them to a build server.

It has limits. There are no push notifications and no iOS output, generated apps need Android 8.0 or newer, and it can’t import an existing JKS or P12 keystore. An AAB from it is not Google Play approval either; the webview rule still applies.

A quick checklist

Own the site, or get its owner’s permission to wrap it.
Pick the route: a WebView builder for any HTTPS site, or PWABuilder if you already have a PWA.
Build, install the APK on a real phone, and test login, forms, uploads and outside links.
Back up the signing key and its password before you share a single build.
Before you submit, list what the app does that the website doesn’t. If the list is empty, expect trouble in review.

FAQ

Can I really make an Android app from my website without writing code?

Yes. A no-code WebView builder takes your URL, name and icon and gives you a signed APK. If your site is already a Progressive Web App, PWABuilder can package it as a Trusted Web Activity without code too.

Will Google Play accept an app that is just my website?

Not reliably. Google has said that apps which are just webviews of existing websites are treated as webview spam and removed. Add something the website alone doesn’t give users, and only wrap a site you own or have permission to use.

What is the difference between a WebView app and a Trusted Web Activity?

A WebView app shows your pages inside the app’s own embedded browser view. A Trusted Web Activity opens your PWA in the user’s browser, full screen, and needs Digital Asset Links to prove the app and site belong to the same developer.

What do I need besides the APK to publish on Google Play?

A Google Play developer account with a one-time US$25 fee, an AAB rather than an APK for the store upload, and for newer personal accounts a closed test with at least 12 testers for 14 days.

How do I turn a website into an APK without coding?