Application: Nomid MDM
Document: V1.0.0
Last updated: 03/08/2026
Editorial owner: Nomid MDM Documentation
Last editorial review: 03/08/2026
Editorial language: en-US
(Managed Google Play web apps model through EMM)
This manual explains, from both an operational and conceptual perspective, how to create, configure, and make available a Web App in Managed Google Play through the EMM/Nomid MDM flow, without publishing a public app in Play Store.
This model:
This manual does not cover PWA + TWA or native Android applications.
To turn a shared route link into an individual Web App, see Create a Web App for a Google Maps route. The guide explains how to create and test the route, register the link, distribute Maps and Chrome, and validate the shortcut on the device.
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 |
| Managed Google Play access through the EMM/Nomid | Yes |
To create the Web App and associate it directly with a policy, use the confirmed path:
Nomid MDM > Policies > select the policy > Home Screen > Add App > Create Web App
This path opens the creation form in the context of the policy that will distribute the shortcut. Other screens may show application catalogs or records, but they should not be treated as an equivalent path unless the flow displayed in the portal has been confirmed.
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.
Effect in use: provides a more immersive presentation but leaves fewer visible controls for checking the address, refreshing the page, or returning during troubleshooting. Validate return, authentication, and navigation on the pilot device before adopting this mode.
An intermediate mode.
Effect in use: presents the content in a separate window with the device bars but without the full URL bar. Certify this mode when return and navigation work without additional controls.
Displays:
Why use it:
Use Minimal UI as the starting point for the first pilot, not as a universal requirement. After testing, the organization may certify another mode. The mode controls Web App presentation; by itself, it does not determine which application opens an external link.
Requirements:
An incompatible file may prevent registration from being completed or make the application difficult to recognize. Confirm dimensions, format, and readability before selecting Create.
Why: this mode keeps visible controls that help verify the address, refresh content, and return during the pilot.
What it lets you validate:
Why: each redirect may take the user to another domain or authentication flow. Test the complete path in the Web App before distribution.
Risks:
Why: testing in Chrome for Android helps identify layout, redirect, and authentication issues before creating the Web App.
Practical rule: the Chrome test is preparation, not certification. Repeat the flow in the Web App and on the pilot device.
Why: a page designed for mobile screens reduces touch, reading, and navigation errors on the device.
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:
Deleting the Web App from the catalog removes future distribution, but it does not replace access revocation in the web system. If the site must no longer be accessed, also block or remove access in the application backend.
This model is suitable for:
It does not replace: