Quote from luishp on January 29, 2026, 1:42 pm

Not in the “100% universal, works the same everywhere” sense — full-screen kiosk behavior is ultimately controlled by the OS + the browser, and browsers intentionally restrict what a web app can do (to prevent abusive “you can’t escape” experiences).

What you can do in VisualNEO Web is get very close, using a combination of:

1) Make the app fill the screen (layout/responsive)

Use FitAppToScreen at app startup (Project ► Events) so your UI scales to any display size.

Example (Project ► Events ► startup):

FitAppToScreen false "top" "center"


This is the “universal” part: it’s just layout scaling.

2) Enter browser fullscreen (but only when the browser allows it)

VisualNEO Web includes EnterFullScreen (same effect as pressing F11 in the browser).

However:

• Many browsers require a user gesture (tap/click) before allowing fullscreen.

• Some environments (notably iOS Safari quirks) may limit or change fullscreen behavior.

If you’re using the PowerApp plugin commands, there’s also slRequestFullScreen, explicitly documented as “request… on mobile devices” and noting it must happen after a user interaction and that support varies by browser.

Practical pattern: show a “Tap to start” button → on click run EnterFullScreen (and/or slRequestFullScreen if you use that plugin).

3) Use PWA “standalone” to remove browser chrome where supported

If you deploy as a PWA, many platforms/browsers can run it in a more “app-like” window (no address bar) after installation — but installability and behavior varies by browser/device.

In your app source you’ll see properties like DisplayMode (e.g., standalone).
That’s the best cross-platform way to reduce browser UI, but it still isn’t identical everywhere.

4) Prevent screen sleep (important for kiosks)

For kiosk-style unattended use, enable neoNoSleep so the display won’t dim/lock while the app is open (where supported).

5) True “kiosk mode” is platform-specific

If by “kiosk” you mean locked down, auto-launch, no easy exit:

• On desktop, kiosk is usually achieved by launching Chrome/Edge/Firefox with OS-specific kiosk flags/policies (outside the app).

• For Windows-only packaging, VisualNEO includes neoEXE, which can create an .exe with options like fullscreen/frameless, but that’s Windows (WebView2) only.

• For Windows/Linux/macOS, VisualNEO Web mentions packaging as an NW.js standalone app.

• For Android/iOS, you typically rely on PWA install or a Cordova-style wrapper (not truly “any browser” anymore).

---

Bottom line

• Universal fullscreen kiosk across all browsers/OSes with only in-app code: No (browser security + OS kiosk controls prevent that).

• Best practical universal approach:
  FitAppToScreen + prompt user to “Tap to start fullscreen” (EnterFullScreen / slRequestFullScreen) + deploy as PWA (standalone) + neoNoSleep for unattended displays.

Quote from Alf.bogner on January 29, 2026, 2:40 pm

Thanks. I'll give it a try.