Is a WebAPK the same thing as a regular APK file?

No — a regular APK contains the app's code inside the file itself, while a WebAPK is a minimal wrapper that just launches a web page in an app-like mode. All the actual functionality still runs through the web, not native code.

Why does a PWA install as a plain bookmark for some users instead of a WebAPK?

Usually because one of the requirements isn't met: no HTTPS, an incomplete PWA manifest, or no registered service worker. Without those, Android can't build a full WebAPK wrapper and falls back to a plain shortcut.

Does the user need to go through Google Play to get a WebAPK?

No, the WebAPK is built automatically on the device when the PWA is installed through Chrome — no separate app-store download is involved.

What happens to the WebAPK when a funnel's domain changes?

Since a WebAPK is tied to a specific domain, a domain change is effectively a new install from the user's point of view — the old icon might keep working for a while, but it's not something to rely on.

What Android WebAPK Actually Is

Android WebAPK is the mechanism the OS uses to turn an installed PWA into something that behaves like a native app instead of just a shortcut to a website. Here's what that changes technically, and why it matters if you're running PWA funnels on Android.

What a WebAPK actually is, technically

When a user installs a PWA on Android through Chrome — usually via an «Add to Home Screen» prompt or an automatic banner — the device itself builds a minimal APK file that wraps that PWA. It's not a full native app with code inside — it's essentially a wrapper that runs the same web content but looks and behaves like an installed app.

How a WebAPK differs from a plain website shortcut

A regular home-screen shortcut just opens the browser at a given address. A WebAPK, on the other hand, shows up in the device's general app list, gets its own icon with no browser branding, can run full-screen, and gets access to some system-level capabilities — push, background behavior — that a plain bookmark can't reach.

What has to be true for Android to build a WebAPK

Android only builds a WebAPK for pages that meet valid-PWA criteria: a manifest with the required fields (name, icons, start_url), HTTPS, and a registered service worker. Miss even one of those, and the user gets a plain bookmark shortcut instead of a full WebAPK wrapper — and some of the benefits of the PWA approach simply don't kick in.

What this means in practice for a media buyer

If a funnel doesn't qualify for a WebAPK — say, because of an HTTPS issue on the domain or a broken manifest — the user ends up with a less convincing experience: a plain bookmark instead of an «app», and part of the audience may not register it as an installed app at all. A WebAPK is also tied to a specific domain, so a domain change almost always means the user has to reinstall.

How APEX makes sure a PWA actually qualifies for a WebAPK

PWAs built in APEX ship with their own domains on automatic HTTPS and a correctly configured manifest and service worker out of the box — exactly the conditions Android needs to build a proper WebAPK instead of falling back to a bookmark. One-click domain rotation stays a fast operation on the infrastructure side, even though users on the new domain technically go through install again.

FAQ

Is a WebAPK the same thing as a regular APK file?: No — a regular APK contains the app's code inside the file itself, while a WebAPK is a minimal wrapper that just launches a web page in an app-like mode. All the actual functionality still runs through the web, not native code.
Why does a PWA install as a plain bookmark for some users instead of a WebAPK?: Usually because one of the requirements isn't met: no HTTPS, an incomplete PWA manifest, or no registered service worker. Without those, Android can't build a full WebAPK wrapper and falls back to a plain shortcut.
Does the user need to go through Google Play to get a WebAPK?: No, the WebAPK is built automatically on the device when the PWA is installed through Chrome — no separate app-store download is involved.
What happens to the WebAPK when a funnel's domain changes?: Since a WebAPK is tied to a specific domain, a domain change is effectively a new install from the user's point of view — the old icon might keep working for a while, but it's not something to rely on.

Build your PWA in APEX in minutes

Cloaking, anti-bot, push, split tests and your own domains — in one service.

Get started free