1. Define the user journey
Specify who will use the kiosk, what they need to achieve, which actions are allowed and how the interface should return to its start state after use.
2. Audit hardware and connectivity
Record the device model, operating system, processor, memory, storage, screen resolution and orientation, touch controller and internet connection.
- Windows, Android or Linux version
- portrait or landscape display
- Ethernet, Wi-Fi or mobile network
- audio, printer and other peripherals
- physical access and cooling
3. Prepare and optimise content
Test the exact website, video, presentation or HTML package on target hardware. Large media should be compressed to the resolution actually required by the display.
4. Configure kiosk security and recovery
Set autostart, trusted domains, PIN-protected settings, refresh rules and an authorised maintenance path. Confirm how the device returns to service after a power or network interruption.
5. Pilot, document and scale
Run a pilot on one or a small number of devices. Once content, performance and recovery are accepted, reuse the verified configuration across the fleet and document responsibilities.
Frequently asked questions
Do you recommend testing on the final device?
Yes. Browser, graphics, touch, video and power-management behaviour can differ significantly between device models.
Can deployment start with one kiosk?
Yes. A single-device pilot is the safest way to validate the setup before expanding.
What usually causes kiosk problems?
Common causes include unstable connectivity, oversized media, outdated system components, missing permissions and an untested recovery process.
Send us the basic kiosk specifications and the content you plan to display.