Skip to main content

🛠️ Recommended set up of devices

Setup guide: hardware, network, and OS settings for reliable Merlin Cloud kiosks. Use our checklists to prep devices for deployment.

Leo avatar
Written by Leo
Updated over 5 months ago

Supported hardware

Official

  • Android 8.0 or later

  • Minimum 8 GB RAM for smooth, no lag experience

  • Minimum 64 GB storage

Devices

  • Off-the-shelf tablets like Samsung and Lenovo

  • Bespoke or built-to-spec tablets can be supplied on request

  • Peripherals such as scanners or printers are optional and supported

Power

  • Keep kiosks plugged in during operating hours

  • Devices we supply support 8+ hours of battery for power cuts

Network and connectivity

Throughput

  • Recommended 10 Mbps or higher

  • Video heavy sites 30 Mbps or higher

  • Absolute minimum 2 Mbps, not recommended unless unavoidable

  • 4G SIMs are supported where Wi-Fi is unreliable, prioritise stability over peak speed

Wi-Fi and LAN

  • Use a dedicated SSID or VLAN for kiosks where possible

  • Disable captive portals on kiosk networks or pre-authorise devices

  • Allow outbound HTTPS to Merlin Cloud services and our CDN

  • Ensure DNS is reachable and not filtered for required domains

  • Time must be accurate, enable automatic date and time

Offline expectation

  • Devices should be online daily so analytics sync and releases apply promptly

Android OS configuration

  • Install the Merlin Cloud Package and enable Merlin Cloud Lockdown

  • Set Merlin Cloud as the default launcher or pinned app

  • Enable auto start on boot so the app launches after power restore

  • Keep screen awake during operating hours and set an appropriate screen timeout

  • Disable or relax battery optimisation for the kiosk app

  • Schedule OS updates outside customer hours

  • Set the correct timezone and default locale for the site

Technician tip

  • To exit Lockdown on a kiosk, tap the screen 7 times in the bottom-right corner

Storage and asset guidance

  • Keep several GB of free storage so the service worker can cache releases

  • Compress media before uploading to the CMS

  • Files over 1 MB increase update time and may fail on poor links

  • Prefer modern, web-optimised image formats and reasonable video bitrates

  • Local images are cached by the service worker and update when the app updates

Cache, reload and invalidation behaviour

  • The experience reloads every 15 minutes when online to fetch the latest code and files

  • Invalidation also runs:

    • On idle after 60 seconds when online

    • When the service worker updates after a new build is deployed

  • While offline the kiosk continues to serve the last cached release

Analytics and privacy defaults

  • Interactions are captured locally while offline and uploaded when online

  • Data is stored in localStorage and removed only after successful insertion into the database

  • Sessions use UUID v4 to dedupe; the most recent duplicate wins

  • We do not store sensitive data locally; sensitive inputs are redacted

  • Default retention on device: up to 30 days and 1,000 sessions

  • Enterprise options are available on request

Site readiness checklist

  1. Hardware

    • Android 8.0+, 8 GB RAM, 64 GB storage

    • Mounting secure and accessible for staff

    • Power available and device charges correctly

  2. Network

    • Stable connectivity that meets the throughput guidance

    • No captive portal or the device is pre-authorised

    • Firewall allows outbound HTTPS and DNS resolution

    • Time and timezone auto-set

  3. App

    • Merlin Cloud Package installed and set as launcher

    • Lockdown enabled, exit gesture confirmed

    • Device name and location match your naming convention

  4. Content

    • Campaign assigned to the device

    • Assets compressed, single files kept under 1 MB where possible

    • Preview checked on the device for the correct locale

  5. Health

    • Heartbeat visible in the dashboard within 30 seconds

    • Status shows Green

    • Allow one 15-minute reload cycle to confirm update behaviour

  6. Fallback and resilience

    • Confirm the branded No internet available splash appears when network is disabled

    • Restore network and verify analytics upload completes

Go-live steps

  1. Connect device to production network and power

  2. Sign in and link the device to its location in the dashboard

  3. Assign the intended campaign version or the latest release

  4. Verify Last seen and heartbeat history are updating

  5. Trigger a small content change and wait for the next reload to confirm delivery

  6. Use Beep device to locate hardware on site and confirm remote actions work

Ongoing operations

  • Keep devices online daily

  • Monitor Device health and act on Yellow or Red alerts

  • Use Kiosk remote capabilities and actions for day-to-day support

  • Review large assets regularly and re-compress where needed

Did this answer your question?