Independent browser engine
The application includes its own supported web runtime so compatible content can work even on devices without a current Chrome or Android System WebView installation.
Activation and protected settings
After entering the licence key, an authorised person creates a PIN used to leave the kiosk or open Android settings. The control strip can be positioned to match the device.
Always-on kiosk behaviour
Launcher and lock-task options can keep the kiosk experience in the foreground. Opening protected system settings temporarily releases the restriction where required.
Content and remote updates
The Android app receives the selected website, media, presentation, menu or game from the same KioskSide dashboard used by other platforms.
Device differences matter
Commercial Android displays often use customised firmware. Test certificates, media decoding, touchscreen behaviour, autostart and device-owner support on the exact model.
Frequently asked questions
Does the device need Google Chrome?
No. The current KioskSide Android build uses an embedded browser engine and does not depend on Chrome being installed.
Why should the final display be tested?
Android firmware and management capabilities vary significantly between manufacturers and device models.
Can the app be prevented from going into the background?
Supported kiosk, launcher and device-owner controls can enforce foreground operation, subject to device permissions.
Send us the basic kiosk specifications and the content you plan to display.