A systems integrator inherits a production line with a WinForms application last compiled in 2014. The customer wants a 10-inch panel on the wall for the operator station, and the question lands in your inbox: does our app run on the Android panel you quoted, or do we need Windows? That single question shapes the budget, the hardware and the delivery date. Here is the comparison we walk customers through, and a checklist to run before you commit to an industrial panel PC operating system.
Start from the code you already have
Most industrial software of the past two decades targets Windows. .NET Framework, WinForms, WPF, MFC, Delphi frontends, vendor DLLs for PLC protocols, dongle-based licensing. None of it runs on Android as-is. Moving that code means a rewrite in Kotlin or Java, or a port to a cross-platform framework such as Qt, and then every PLC connection gets retested on new hardware. A 40-screen SCADA client can easily consume months. If the Windows build still works and will keep working, staying on Windows protects that asset.
Android flips the picture when the interface is new. Android Studio, Kotlin, Jetpack Compose for touch UI, WebView hybrids for teams with existing web assets. The developer pool is deep, touch behaviour is native to the platform, and a first clickable prototype tends to appear in days rather than weeks. On the hardware side, ARM boards cover the sizes most terminals use: the P-S1-070 7-inch panel ships in A133P, RK3288, RK3568 and RK3576S variants, so the SoC is chosen from the part number rather than discovered after the order.
Licensing, and what it does to unit cost
AOSP carries no per-unit license fee. Windows does. A panel that runs Windows needs Windows IoT Enterprise, usually an LTSC build, licensed per device with activation handled at the factory. On a 500-unit rollout the license line is real money. On a 15-unit pilot it barely registers. Price both ways before you commit; volume changes the answer.
There is a hardware coupling too. Desktop Windows runs on x86 processors (a Windows-on-ARM edition exists, but x86 application compatibility is usually the reason a project wants Windows in the first place). Most low-power HMI panels, ours included, are built on ARM SoCs such as the Rockchip RK3568 or Allwinner A133P and ship with Android. Choosing Windows narrows the board to x86, which typically means higher power draw and a higher unit price. Where Windows is a fixed requirement, pick a range that is offered both ways: the AY-T03 10.1-inch enclosed panel PC comes in Android, Windows and monitor-only configurations, so the same housing and cutout survive a late change of OS. Choosing Android keeps the standard panel range open, and the ARM end of it goes further than a simple terminal: the AY-TJ101-H pairs a quad-core RK3568 running at up to 2.0 GHz with dual isolated RS485 and dual gigabit Ethernet.
Boot behaviour and OS maintenance
An Android panel boots straight to the launcher, starts your application on power-up, and locks into kiosk mode if you let it. Updates are yours to schedule: you ship one tested image, push it by USB, Ethernet or MDM, and the operator never meets a system dialog at 6 a.m. Power and cabling belong in the same decision: the P-H1-070 takes PoE as an option, which removes the mains drop at the panel position.
Windows patches on its own schedule unless you take control. LTSC builds reduce feature churn and stretch support to roughly ten years per release, which is why plant IT departments like them. Patches still need a maintenance window, disk images still need an owner, and an unattended reboot mid-shift is a real risk if nobody planned for it.
Neither OS is real-time. When a spec sheet calls for deterministic response in single-digit milliseconds, that job belongs to a PLC. The panel remains what it should be: a visualization and input layer. How an HMI talks to a PLC covers where that split usually falls and what belongs on the gateway.
Building and maintaining the UI
Windows gives you desktop-grade tooling: Visual Studio, WinForms or WPF, a large component market, multi-window layouts, keyboard and mouse alongside touch. Android is touch-first. Large hit targets, gesture support and single-app focus are defaults, which suits a wall-mounted terminal. The trade-off sits at the BSP level: Android versions track what the SoC vendor maintains, so plan to freeze on a tested image instead of chasing OS upgrades. On Windows, application compatibility across versions is more forgiving; the OS itself simply changes more often.
Side by side
| Dimension | Windows (IoT Enterprise) | Android |
|---|---|---|
| License | Per-device fee, activation managed by the OEM | Free (AOSP) |
| Hardware fit | x86 boards, higher power draw and unit cost | ARM SoCs, standard low-power panels |
| Existing code | Runs legacy .NET and Win32 software unchanged | New build or a port required |
| Boot and updates | Slower boot; patch windows must be planned | Fast boot, auto-start, image-level updates |
| UI tooling | WinForms/WPF, multi-window desktop patterns | Kotlin and Compose, touch-first patterns |
| Best fit | Heavy client software, engineering workstations | Dedicated touch terminals, kiosks, controllers |
Which projects suit which
Windows suits the heavy end: SCADA and MES clients, machine vision suites, legacy .NET applications, an engineering station beside the line. The code exists, the license fits the budget, and x86 hardware is part of the plan. For an operator station on that side of the line, the AY-T02 21.5-inch wall-mount panel PC is offered with a Windows motherboard configuration and a 1920 x 1080 display.
Android suits the dedicated terminal: room controllers, self-service kiosks, thermostats, dashboard panels, anywhere the touch interface is the product. Unit cost stays low, boot behaviour is predictable, and a 10-inch panel covers most of these jobs. Self-service terminals are the common version of this, and what a self-service kiosk asks of a touch panel sets out those requirements; the self-service retail page shows where these panels end up. Plenty of projects use both. An Android panel on the wall for operators, a Windows box in the cabinet doing computation. They share the network already; the panel shows, the PC calculates.
A checklist before you sign anything
- Existing code: which OS does it target, and does a port fit the schedule?
- Volume: what does the per-device license cost at 15 units versus 500?
- Hardware: does the board road map survive the OS choice, x86 or ARM? Reading an industrial HMI spec sheet walks through the lines that answer it.
- Power events: after a cut, what boots, in what order, and how fast?
- Ownership: who applies OS patches for the next five years, and when?
- Scope of the panel: visualization only, or computation too?
Where our panels sit
Our S, P, M and B series ship with Android as standard on ARM SoCs. For a dedicated terminal, the B S1 10.1" Touch Panel PC and B H1 10.1" are the economical 10-inch options. The P M1 10.1" comes in RK3568, RK3288 and A133P variants; the part number names the SoC before you ask. For dashboards read from across the room, the P X2 21.5" Smart Control Panel buys screen area. If your project needs Windows, say so early. The OS and the board should be chosen together, and OS availability varies by model. If your fork in the road is Android versus embedded Linux instead, we covered that in a separate article: Android vs Linux for Industrial HMI.
Can an Android HMI panel run my existing Windows application?
Not unchanged. .NET Framework, WinForms, WPF and MFC builds target Windows and need a rewrite or a port before they run on Android. If that application is the reason the project exists, and the port does not fit the schedule, Windows is the cheaper answer even after the license fee.
How much does a Windows license add to an HMI panel?
Windows IoT Enterprise is licensed per device. On a 15-unit pilot the license line is small next to the engineering cost; on a 500-unit rollout it changes the unit price in a way most procurement teams want to see in writing. Ask for both quotes before the board is chosen.
Which operating system boots faster on an industrial panel?
Android, in practice. It starts the application on power-up and stays in kiosk mode if you configure it that way. Windows needs a longer boot and a planned maintenance window for patches, though LTSC builds keep feature changes to a minimum.
Can one project mix Windows and Android panels?
Yes, and many do. An Android panel on the wall handles visualization and input, while a Windows machine in the cabinet runs the heavy client software. They share the network, so the split costs nothing in integration terms.
Do AOYU panels come with Windows?
Android on ARM SoCs is the standard configuration across the S, P, M and B series. Windows is available on specific ranges: the AY-T02, AY-T03 and AY-T05 industrial panel PCs are offered in Android, Windows and monitor-only configurations. OS availability varies by model, so confirm it before the enclosure and cutout are fixed.
Get the OS matched to the software you already run
Send us the application you have to run, the panel size and the volume you are planning. We will say which board and OS combination carries it, and what the per-device license does to the unit price. Send an inquiry, or start from the industrial machine control page if the machine is still being defined.
Not sure which OS fits your project? Send us your requirements and get a quote in 24 hours: request a quote.
Related products
Explore our HMI panels
P-S1-070 7-inch HMI Panel
Display size: 7 inches. Resolution: 1024 × 600 px. Brightness: standard: 500; optional: 10…
View product →
AY-T03 10.1-inch Enclosed Industrial Panel PC
AY-T03 10.1-inch Enclosed Industrial Panel PC combines a fully enclosed aluminum housing, …
View product →
AY-TJ101-H 10.1-inch RK3568 ARM Touch Panel PC
An ARM interface for connected equipment AY-TJ101-H combines a quad-core RK3568 Cortex-A55…
View product →Ready to start your HMI project?
Our engineers help you choose the right HMI hardware and software for your project.