For App Builders · Guide

Can You Put a Web App on Google Play? Yes, Here Is How It Works

By Will McCullough, DigiRune Studios ·

The short answer: Yes. A web app, especially a Progressive Web App you own, can go on Google Play as a Trusted Web Activity: a small Android app that opens your website full screen in the user's browser engine. Tools such as Google's Bubblewrap build the Android package from your web manifest. To hide the browser bar, the browser has to verify that the app and the website come from the same owner, using a file called assetlinks.json on your site.

What is a Trusted Web Activity?

A Trusted Web Activity (TWA) is a way to open your own web content, such as a Progressive Web App, inside an Android app. It is built on the same technology as Chrome Custom Tabs, and your pages are drawn by the user's browser. That means your web app has to work well in a normal mobile browser first; the Android app does not fix a site that is broken on phones.

Chrome's documentation is clear that this only works for websites that you own. It is not a way to wrap someone else's site.

What do I need before I start?

  • A website you own that meets Chrome's installability basics, such as HTTPS and a web app manifest.
  • A site that already behaves like an installable web app. Chrome says to expect the same requirements as Add to Home Screen, and suggests checking your site with Lighthouse.
  • A Google Play developer account and a way to test on a real Android phone.

How is the Android app built?

Google's tool for this is Bubblewrap, a command-line tool. It reads your web manifest, asks you to confirm the app name, colors and icons, and generates the Android project, then builds a signed package you can install on a test phone. Other tools wrap the same idea in a website instead of a command line. In our experience, for Google Play itself you upload an Android App Bundle, and it has to meet Google Play's current target API level requirement (see our target API level guide).

Why does my app show a browser bar at the top?

Until the browser verifies that your app and your website belong to the same developer, the app opens your site as a Custom Tab, with browser controls at the top. The proof is Digital Asset Links: a file named assetlinks.json that you host at /.well-known/assetlinks.json on your site's root.

That file points to your app and the key it is signed with. Chrome's guide notes that verification depends on the signing key, and that Google Play may sign your app with a different key than the one on your computer, so using the wrong fingerprint is a common cause of failure.

What traps should I watch for?

  • The fingerprint: in our experience, when Google Play signs your app, copy Play's app signing fingerprint from Play Console into assetlinks.json, not only your own key's.
  • The location: the file must sit at the root of the exact domain the app opens. In our experience, a site hosted in a sub-folder, such as a GitHub Pages project page, needs the file at the domain root, which can mean a separate root site just for that file.
  • Cached checks: in our experience, a phone that installed the app before the file was fixed may keep showing the bar until you uninstall and reinstall.
  • Account rules still apply: some new personal Google Play accounts must run a closed test first (see our 12 testers guide).

Is a web app good enough for Google Play?

It can be, if it is genuinely useful as an app: fast, works on a phone screen, and does something people come back for. Google Play still reviews it like any other app, so the same store listing, privacy and Data safety rules apply.

Taking your app to the stores?

The DigiRune Studios Store Launch Kit is a step-by-step guide and checklist for getting through Apple App Store and Google Play review, built from the process we use for our own apps. Apple and Google make every approval decision; the kit helps you submit ready.

See the Store Launch Kit

Sources

Store rules change. Check the official pages on the day you submit. Checked November 19, 2026.