WebAPK
WebAPK is Android's own mechanism for turning a PWA into an app-like install: Chrome generates a small signed APK on the fly when a user adds the PWA to their home screen, provided the site meets install criteria (manifest, service worker, HTTPS). From then on the PWA shows up in the app list and opens full-screen, just like a native app, with no store and no developer packaging step. That's what separates WebAPK from TWA, which a developer builds and publishes deliberately.
How it works
Chrome checks the manifest (icons, name, start_url), confirms a working service worker, and verifies the domain is on HTTPS, then offers the user an install prompt. The resulting APK is signed by Google, the PWA runs without browser chrome, and it shows up in system settings like any other app.
Why it matters for arbitrage
The WebAPK criteria — HTTPS, a valid manifest, a working service worker — are exactly what decides whether an offer feels like a real app to the user or just another website. A home-screen icon means repeat visits without another ad click, which matters a lot for gambling and betting verticals with high visit frequency. APEX builds PWAs with a correct manifest, service worker, and HTTPS on your own domain from the start, so the install check passes without manual tuning.
FAQ
- Do you need to configure anything separately for WebAPK to appear?
- No — if the PWA meets Chrome's criteria (manifest, service worker, HTTPS), the WebAPK is generated automatically when the user adds it to their home screen.
- Is a WebAPK a separate app on Google Play?
- No, a WebAPK is never published to the store — it's a local wrapper Chrome builds right on the user's device.
Cloaking, anti-bot, push, split tests and your own domains — in one service.
Get started free