Micro Markets

The kiosk shift: Why Android and ARM are gaining ground in automated retail

As Android and ARM-based hardware gain ground in automated retail, Windows faces growing competition. T-ROC's Ben Wheeler examines how licensing, energy efficiency, remote management and maintenance costs are reshaping kiosk platform decisions, emphasizing total cost of ownership over upfront hardware pricing.

SDF_QWE - stock.adobe.com

October 15, 2026 by Ben Wheeler — Dir. of Business Dev. - Automated Retail, T-ROC

Summarize with

Part 1: The economics behind the platform decision

At the recent NACS Show in Las Vegas, I was talking with Ed Crowley, better known across the industry as the "Kiosk Guru," about Android, Windows, and where automated retail hardware is heading.

Ed made a statement that caught my attention:

"Windows is pricing itself out of the automated retail kiosk industry."

That is a bold claim considering how deeply Windows has been embedded in kiosks, POS systems, and self-service technology for decades.

I would not write Windows off. It remains a capable platform and makes sense in many enterprise environments. But Ed's larger point deserves attention because the economics behind automated retail are changing.

Devices are becoming smaller and more purpose-built. Fleets are growing. Remote management is expected. Touch-first customer experiences have become standard. Operators also want equipment that consumes less energy, creates less heat, and requires fewer service visits.

Against that backdrop, Android and ARM-based hardware are becoming increasingly attractive.

The story is not simply about which operating system costs less. It is about what the entire kiosk costs to deploy, manage, support, and maintain over its useful life.

Licensing is only the first cost

Most Windows-versus-Android discussions begin with software licensing.

Android's open-source foundation gives manufacturers more flexibility when building commercial devices. Windows IoT Enterprise, by comparison, is a licensed commercial operating system built for fixed-purpose devices such as kiosks, POS terminals, and digital signage.

Across one kiosk, that difference may not determine the business case. Across hundreds or thousands of devices, it starts to matter.

Ed also pointed out that the license is only one expense. Maintaining the environment, managing upgrades, testing compatibility, and supporting major migrations can add considerable cost over time.

That is why operators need to think beyond the purchase price.

A platform that looks affordable on day one can become expensive if it requires more hardware, more IT resources, more field support, or more intervention during its lifecycle.

Mobile computing changed the hardware equation

For years, many kiosks were essentially commercial PCs placed inside purpose-built enclosures. Windows ran the application, Intel or AMD processors handled the computing, and the system relied on familiar PC components.

Then mobile computing changed what was possible.

ARM-based processors became more capable while maintaining lower energy requirements and smaller physical footprints. Phones and tablets pushed manufacturers to improve touch performance, thermal management, and computing capacity without relying on traditional desktop hardware.

Kiosk manufacturers can now build certain systems more like purpose-built appliances than PCs inside metal cabinets.

That matters operationally.

Lower-power processors can reduce heat inside the enclosure. Fanless designs remove a mechanical component that may eventually require service. Smaller computing platforms can also give manufacturers more flexibility when designing the unit.

For many automated retail applications, operators do not need desktop-class processing. They need a dependable interface, payment connectivity, product control, telemetry, and remote management.

Ed referred to this shift as a move toward a more "mobile-native" hardware model. We have already watched that model reshape consumer technology, and it is now influencing kiosks, POS systems, self-service devices, and AI-supported customer experiences.

The bigger expense may come after deployment

Hardware gets attention because operators can see and compare it before purchase. Once a kiosk fleet is in the field, the bigger challenge becomes managing those devices efficiently.

A network of several thousand kiosks cannot depend on a technician visiting every machine whenever software needs an update, a configuration changes, or a basic problem needs to be diagnosed.

That simply does not scale well.

Android has benefited from growing up in an environment where large groups of devices were expected to be managed remotely. Enterprise device-management platforms can give operators centralized control over applications, policies, updates, security settings, and device status.

That fits automated retail well.

If an application can be updated remotely or a device issue can be diagnosed without sending someone to the location, the savings extend beyond IT. It can mean fewer truck rolls, less downtime, and faster recovery.

Windows also has mature enterprise-management capabilities. For organizations already built around Microsoft infrastructure, that can be a major advantage.

This is why I do not see the platform decision as a simple contest.

Windows still has a strong case

Windows is not disappearing from automated retail.

Many retailers have years of investment in Windows-based applications, specialized peripherals, enterprise security tools, and internal support teams. Existing kiosk systems may depend on drivers or software that were built specifically for Windows.

In those environments, moving to another operating system simply to reduce hardware or licensing costs could create a much larger expense elsewhere.

Application compatibility matters. Existing infrastructure matters. Support experience matters.

The change I see is that Windows is no longer necessarily the automatic starting point for every new kiosk program.

A new automated retail deployment may begin with very different requirements. The experience may be touch-first and cloud-connected from the beginning, with remote management built into the operating model and thousands of possible endpoints planned from the start.

That is where Android and ARM can become especially compelling.

The real decision is total cost of ownership

At T-ROC, we see automated retail as a connected operating system rather than a collection of individual technologies.

The operating system affects the hardware. Hardware affects power requirements and serviceability. Software affects remote management. Remote management influences field-service demand, and field service has a direct impact on uptime and revenue.

Those connections matter much more than one line on a hardware quote.

That is why I would not choose Android simply because the licensing structure may be less expensive. I also would not choose Windows simply because it is familiar.

The business requirements should drive the platform.

A kiosk expected to remain in the field for seven years has different needs from a short-term deployment. A retailer managing several thousand units faces a different support challenge from a business operating 20 machines. A company with an established Microsoft environment may reach a different conclusion from one building its technology stack from the ground up.

Each of those decisions can be right.

What Ed's comment really gets right

The more I thought about Ed's statement after NACS, the more I realized that the most important word was not "Windows."

It was pricing.

And pricing in this case means much more than the operating-system license.

It includes hardware, memory, cooling, energy use, device management, IT resources, field support, downtime, upgrades, and eventual replacement.

Android and ARM are gaining ground because, in the right application, they can affect several of those costs at once.

That does not mean Windows is finished, and it does not mean Android automatically wins.

It means automated retail operators now have more viable architectural choices than they did 15 or 20 years ago, and those choices should be evaluated against the full lifecycle of the fleet.

For an industry focused on reducing friction for customers, it makes sense to apply the same discipline behind the scenes by reducing unnecessary cost and technical burden wherever the business case supports it.

That may be the more meaningful kiosk shift taking place.

Coming in Part 2: Ed and I will look at the technical side of that shift, including I/O, peripheral communication, and how newer Android- and ARM-based architectures are changing the way kiosk hardware communicates with the devices around it.