Android web app starts Multi-App Kiosk instead of Single App KioskSolved

Participant
Discussion
4 weeks ago Oct 15, 2026

I’m setting up an Android tablet to run a web app in kiosk mode. I added the web app to the policy under Background Apps, but when the policy reaches the device, it switches to Multi-App Kiosk instead of launching only that web app.

I want the web app to open automatically in full screen. What is the correct way to configure a web app as a single app kiosk on Android?

Replies (3)

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Oct 15, 2026
Marked SolutionPending Review

Hello @vance_j ,

For Android kiosk policies, adding a web app only under Background Apps will not start Single App Kiosk mode. Background Apps are treated as supporting apps and are not launched as the primary foreground kiosk app.

Configure it this way:

  1. Go to Policies > Android > Kiosk Lockdown >Android Kiosk Lockdown > Single App.
  2. Add the web app as the Single App.
  3. Remove the same web app from Background Apps, because the same app cannot be added as both the foreground kiosk app and a background app.
  4. If the web app requires a browser to render, add the required browser to Background Apps.
  5. Go to Website Kiosk Settings in the same policy.
  6. Set Open web apps with to Hexnode Browser Lite/Kiosk Browser or select another browser.

Once the policy is applied, the web app should auto-launch in fullscreen when kiosk mode starts.

Regards,
Simon Scott
Hexnode UEM

Marked SolutionPending Review
Participant
4 weeks ago Oct 15, 2026
Marked SolutionPending Review

After moving it to Single App and setting it to open with Hexnode Kiosk Browser, the web app launches, but now I’m seeing a blocked access message for the site URL.

Marked SolutionPending Review
Hexnode Expert
4 weeks ago Oct 15, 2026
Marked SolutionPending Review

A blocked access message in Website Kiosk usually means the page being opened, or one of its redirect destinations, is not included in the allowed URLs.

Check the URL behavior outside kiosk first if possible. If the initial URL redirects to another path, both the original URL and the redirected URL must be allowed.

For example, if the web app starts at: https://<domain>/<path>/

but redirects to: https://<domain>/<another-path>/

add both URLs to the allowlist in Website Kiosk Settings. If the URL path requires a trailing slash, include it exactly as used by the site. For URLs with query parameters, use the complete URL provided by the web app/vendor and avoid adding an extra slash after the query string unless the site specifically requires it.

As a quick test, removing the allowlist temporarily can confirm whether the issue is caused by URL filtering or by the web app itself. If the page loads without the allowlist, add back the required original and redirect URLs one by one.

Save