Can a WebView app pass closed testing?

Yes. The requirement applies to every kind of app, and testers count once they opt in. But apps whose first screen loads slowly are easy for testers to close before really trying them, which can weaken the tester engagement Google looks at when reviewing your request.

What's the difference between a TWA and a PWA?

A PWA is a website that behaves like an app in the browser, and a TWA (Trusted Web Activity) wraps that website in an Android app so it can go on the Play Store. The TWA is what gets published on the Play Store, but in both cases most of what users see is web content.

I only see the splash screen, then a white screen for a long time.

If the web content loads slowly, the first launch looks like a blank screen. If testers close the app right away, it doesn't count as having used it, so cut initial loading time and add a loading indicator.

Will I be rejected in the questionnaire review just for being a WebView app?

That alone isn't a reason for rejection. But if your app simply wraps a website and adds no value as an app, it can run into policy problems. Put particular care into the value proposition question in the questionnaire.

← Blog

Requirements

Why PWA, TWA, and WebView apps struggle in closed testing

Apps built with PWA, TWA, or WebView face the same Google Play closed testing requirement (12 testers, 14 days). The requirement doesn't care what kind of app you build, but apps that fill the screen with web content load their first screen slowly, making it hard for testers to really try them. We explain why the tester engagement Google reviews tends to suffer, the symptoms it causes, and how to prepare, such as cutting first-load time.

Last checked Oct 13, 2026.

Same requirement — so why is it harder?

The closed testing requirement applies to every kind of app. Testers count once they opt in, so being built on the web doesn’t make your 14 days fill up more slowly. Where PWA, TWA, and WebView-based apps are at a disadvantage is the next step: the tester engagement Google looks at when reviewing your request.

Google lists “testers weren’t engaged enough during the test” as a reason for sending requests back. Apps whose screens are mostly web content can take a long time to show the first screen, or testers close them before the web content finishes loading. The result is more testers who installed the app but never really tried it.

Google’s documentation doesn’t say how much more often web-based apps are rejected, and we don’t have our own figures either. Read this as a caution based on the simple fact that a slow first screen makes it hard for testers to try the app.

How it shows up

On first launch, a white screen lingers, or nothing loads on devices with a slow network.
Testers close the app before seeing the first screen, so they've barely tried any features.
When the questionnaire asks which features testers used, you don't have much to say.

How to reduce the risk

Keep the first load short. Don’t jump straight from the splash screen to the web view — draw a minimal native screen first, then load the web content on top. The shorter the time to the first screen, the more likely testers are to actually use the app.
Show something even offline. If the network drops, show a message instead of a blank screen. Device conditions vary widely, so this makes a big difference.
Keep extra testers. Don’t stop at the exact minimum; keep a buffer so one uninstall doesn’t break the requirement.
Ship updates during the test. Even a small change like faster loading leaves a version history you can point to in the questionnaire.
Make your app’s value clear. An app that just wraps a website can be flagged on policy grounds. It’s worth having at least one thing that only works because it’s an app, such as notifications, offline support, or device features.

What to check before testing

Is your minimum SDK too high? The higher it is, the fewer devices can install the app.
Does the first launch require a login? If testers get stuck on the login screen, it's hard to confirm the app actually ran.
Do permission requests cover the first screen? On some OS versions they appear in a different order.
Does the web content load on low-end devices? Sometimes the app is killed for lack of memory.

DUIRE runs your app every day on real devices from various manufacturers and OS versions, and keeps one screenshot per device per day. For WebView-based apps these screenshots are especially useful: you can see exactly which devices showed the first screen and which showed a white screen.

How the 14 days are counted, and what to look at when the numbers show up late, is covered in the 14-day counting rules.

Frequently asked questions

Can a WebView app pass closed testing?: Yes. The requirement applies to every kind of app, and testers count once they opt in. But apps whose first screen loads slowly are easy for testers to close before really trying them, which can weaken the tester engagement Google looks at when reviewing your request.
What's the difference between a TWA and a PWA?: A PWA is a website that behaves like an app in the browser, and a TWA (Trusted Web Activity) wraps that website in an Android app so it can go on the Play Store. The TWA is what gets published on the Play Store, but in both cases most of what users see is web content.
I only see the splash screen, then a white screen for a long time.: If the web content loads slowly, the first launch looks like a blank screen. If testers close the app right away, it doesn't count as having used it, so cut initial loading time and add a loading indicator.
Will I be rejected in the questionnaire review just for being a WebView app?: That alone isn't a reason for rejection. But if your app simply wraps a website and adds no value as an app, it can run into policy problems. Put particular care into the value proposition question in the questionnaire.

Meet the requirement without recruiting testers

DUIRE joins your closed test with real Android devices and opens your app every day for 14 days. Registering your app and checking installability are free.

Check installability See how it works