SINGAPORE – iMin showcased its KiwiCloud UEM platform at RetailNOW 2026, demonstrating how it can simplify the setup and management of a full fleet of Android devices.
Booth 831, RetailNOW. Two hours before doors open.
On the table: two floorstanding kiosks with fingerprint readers, a rounded demo monitor, half a dozen POS tablets at different angles, and the Penguin 1 series mounted on an articulating arm — built for the heat, grease, and rush of a real commercial kitchen. Behind those specs sit more than a dozen physical Android devices.
In the past, this meant: power on every device by hand, log into every account, install every app, set every wallpaper, join every Wi-Fi network, switch every unit into kiosk mode — one at a time. At 10–15 minutes per device, a fleet this size costs your team over three hours of manual setup before the first coffee even kicks in.
This time, the entire fleet was live in ~30min. Every device on display was managed through KiwiCloud (KC), iMin’s UEM platform for Android devices.
How do you enroll a dozen Android kiosks into UEM without touching a single setup screen?
Every device was enrolled using Zero-Touch Enrollment (ZTE), built on Android Enterprise (Google’s AMAPI framework). In plain terms: the moment a device powers on and connects to the network, it checks in with KiwiCloud and enrolls into management automatically — no manual login, no clicking through setup wizards, no accepting prompts one by one.
Here’s what that actually looks like. A device comes out of the box, connects to the network — and by the time it reaches the home screen, enrollment is done, policies are applied, apps are installed, and Kiosk mode is active. Zero configuration required on-site.
Over in the KC console, the device has already appeared in the device list. Open its details, and it’s already sitting in its pre-assigned group, with the pre-configured policy applied. And if that policy includes a wallpaper or a kiosk rule, you see it happen right on the screen: the moment the wallpaper and apps finish downloading, the device flips to its new look — or locks straight into the designated kiosk app. No one touched a settings menu.
And because KC is built by the same team that builds the hardware and its ROM, management goes deeper than a generic third-party MDM can reach: KC sees not just the Android device, but the peripherals hanging off it — cash drawer status, thermal printer paper and jam alerts, scanner connectivity — the layer where most retail incidents actually happen.
How do you push the same policy to a whole fleet at once?
With enrollment solved, the next problem was visual consistency — a dozen-plus screens across the booth all needed the same wallpaper, the same visible apps, the same kiosk multi-app for RetailNOW, not whatever state they shipped in.
In the KC console, we pre-built a “RetailNOW live” policy — wallpaper, network settings, and multi-app kiosk mode bundled into one package. (Unlike Android’s native single-app kiosk, KC’s multi-app kiosk locks the device to an approved set of apps, which is what a real demo floor, and a real store, actually needs.)
That’s what we mean by “one-click transition” — not adjusting each device individually, but a single action in the console that flips every screen on the floor in sync.
How do you remotely install and remove apps on a fleet of Android POS devices?
No trade show is complete without partners bringing their own web apps or APKs to demo on your hardware. That used to be a headache — borrow a device for the demo, remember to uninstall afterward, or risk the device getting “reconfigured” by accident through permission issues.
This time, we opened a live installation channel for ISV partners directly in the KC console: their APKs get pushed straight to the designated device over the air, and once the demo wraps, we manage, remove, or restore them remotely — without touching the hardware once. The device stays inside KC’s management scope the entire time, so a temporary third-party install never means losing control of it.
It’s the same answer to a question every fleet operator eventually asks: how do you update apps on a hundred POS devices in the field without sending a technician to each one? You don’t. The cloud does.
Underneath it all, this was a real-world stress test for Business IoT
Strip away the trade-show framing, and this was more a live pressure test of Business IoT capability: iMin’s fleet including kiosks, POS units, the Penguin 1 kitchen terminal proves it can hold up in real commercial conditions, while KiwiCloud proves a whole fleet of devices can be managed as one coherent system.
For retail and restaurant operators rolling out terminals at scale, the problems we hit on the show floor — too many devices, too little time, and third-party apps that still need to play nice — are nearly identical to what happens when a new batch of hardware goes live in stores. What we proved out at RetailNOW is the same capability set: power on and you’re managed, one push and your policy is live, and third-party apps stay under cloud control the whole time.
Beyond the device — managing what’s attached to it
At RetailNOW, iMin’s partner WinstonPOS demonstrated their Kitchen Display Software running on the iMin Penguin 1.
What made this more than a hardware demo: the Penguin 1, along with its display output, was fully enrolled and managed through KiwiCloud. That means the kitchen display isn’t just a screen, it’s a managed endpoint. Policy-controlled, remotely accessible, and visible in the KC console alongside every other device on the floor.
