What "ready for an app" actually means
A website to app conversion does not change your website. It puts your pages inside an Android WebView — the same engine Chrome uses — with an icon, a name and a splash screen around them. So every property of the site carries straight into the app: if it is slow in Chrome it is slow in the app, if it loses its way without an address bar it loses its way in the app, and if it needs a popup window to sign in, the app has nowhere to open one.
The twelve questions above are the things that decide whether a converted site feels like an app or like a broken browser. They are drawn from the support questions people ask after building — the score is a way of asking them before.
The two hard stops
Two answers cap the score no matter how good the rest is. HTTPS, because Android blocks mixed and cleartext content by default and Google Play's pre-launch report flags it. And ownership, because converting a site you do not control is a copyright problem the moment the app is shared, and every store's terms — and ours — require the right to publish it.
How the weighting works
Each question carries a weight between 5 and 14 points. A "yes" earns the full weight, a "no" earns nothing, and "not sure" earns half — because a thing you have not checked is a thing that will surprise you later. The heaviest items are the ones that break the app entirely (HTTPS, mobile layout, in-app loading); the lighter ones are polish that affects reviews rather than function.
| Score | What it means | Do this |
|---|---|---|
| 85–100 | Ready | Build, install, test each screen once. |
| 60–84 | Nearly there | Build now; fix the top two items before publishing. |
| Below 60 | Not yet | Work through the list. Most fixes are an afternoon. |
The fixes that come up most
No way home
The single most common complaint about a converted site: a visitor taps into a page and cannot get back, because the site relied on the browser's back button. The app has a back gesture, but the fix that feels native is a bottom tab bar — the builder adds one on the Pro tier — or simply a header logo that links to the home page on every template.
Sign-in that leaves the site
"Continue with Google" often bounces through accounts.google.com, which refuses to complete inside embedded browsers. If your login has to be social, use a flow that finishes on your own domain; otherwise email and password are the safest bet in a WebView.
Nothing to show offline
A URL-based app needs a connection, and Android's default error page — grey text on white, a "webpage not available" in a system font — is what a visitor sees in a tunnel. A branded offline page with a retry button costs nothing and makes the moment feel intentional.
Beyond the score
A high score means the site will work as an app. Whether it should be one is a different question: a PWA covers some of the same ground without an install, and Google Play's minimum functionality policy decides whether a store listing is possible. Both guides are short.