Application: Nomid MDM
Document: V1.0.0
Last updated: 02/07/2026
Editorial owner: Nomid MDM Documentation
Last editorial review: 02/07/2026
Editorial language: en-US
(Google Play Console "Web Apps" model)
This manual explains, from both an operational and conceptual perspective, how to create, configure, and publish a Web App on Google Play using the native Web Apps feature in Play Console.
This model:
This manual does not cover PWA + TWA or native Android applications.
A Web App is an application that:
It should be understood as:
A website installed as an application, not a traditional Android app.
| Item | Required |
|---|---|
| Public URL | Yes |
| Valid HTTPS | Yes |
| Mobile-friendly website | Yes |
| 512 x 512 icon | Yes |
| Google Play Developer account | Yes |
PWA manifest: not required
Service Worker: not required
Play Console > Create app > Web App > New Web App
The application name displayed in the Play Store.
Best practices:
The initial URL opened when the application starts.
Rules:
https://Completely removes the browser interface.
Why it is not recommended in this model:
An intermediate mode.
Characteristics:
Displays:
Why use it:
Requirements:
An unsuitable icon may cause rejection.
Why: this mode treats the app as an installed website and reduces technical restrictions.
What it prevents:
Why: WebView may block or lose context between redirects.
Risks:
Why: the app uses the same engine as Chrome for Android.
Practical rule: if it works in Chrome for Android, it tends to work in the Web App.
Why: Google Play evaluates mobile quality.
Common problems:
It is not possible to:
Everything must be controlled through the web backend.
It cannot:
It does not receive parameters from the MDM.
Alternatives:
It does not participate in the initial Android provisioning flow.
It cannot access:
Only browser-supported APIs are available.
Required when there is:
Review with the technical team:
This model is suitable for:
It does not replace: