You have a specific x86 Windows fleet, and you want to know whether it can be flipped from Windows to Android. The answer isn't a blanket yes or no. Eligibility is real, knowable, and decided by two concrete things we work with for qualified enterprises. 

TL;DR

• Eligibility depends on two things: your hardware configuration and required peripheral set, and whether your POS or kiosk application has an Android build.
• The application gate is the one most teams miss. Windows-only software means no in-place flip, regardless of how capable the hardware is.
• On the hardware side, many x86 hardware configurations are mature and proven today by enterprise customers that have used Firebolt with Foundation.
• Esper confirms eligibility, hardware and software both, during a scoped assisted evaluation. For the current supported-device matrix, see the Foundation docs.

What makes an x86 device eligible for a Windows-to-Android flip?

The question has a clock on it. Per Microsoft, Windows 10 IoT Enterprise LTSB 2016 loses security support on October 13, 2026. Replacing healthy hardware to fix a software deadline is the most expensive default available.

That rip-and-replace reflex treats an OS deadline as a hardware deadline. It usually isn't one.

There's a second clock, and it's less visible. Microsoft's Secure Boot certificate schedule retires the 2011 certificates starting in mid-2026, with the last expiring on October 19, 2026. Devices that never receive the updated certificate firmware stop getting Secure Boot and boot-chain security updates once the old certificates lapse.

A converted device runs Esper Foundation for Android, which doesn't depend on the Windows Secure Boot chain, so it steps around that second problem instead of inheriting it.

Hardware lifespan and OS support windows are separate clocks. Treating them as one clock is a capital-planning error, not a technical necessity. The flip question exists because the two clocks can be decoupled.

Eligibility for a Windows-to-Android flip comes down to two gates, and both have to clear before any conversion is real. The first is the hardware gate. The second is the application gate.

The hardware gate is not about the badge on the case. It's about the system design and required peripheral set. An x86 terminal qualifies when it can boot and run a supported Foundation image, which is a property of the machine's overall design, not its brand name.

The application gate is about your software. Your POS or kiosk application has to have an Android build, because the flip converts the operating system and leaves the application to you. If the app exists only for Windows, no hardware clears this gate.

So the useful question isn't "is my device supported." It's “can my device run on Android, potentially with scoped engineering work?” Firebolt is what makes the conversion possible at all, but remember it does not rewrite your application.

Does my POS or kiosk software need an Android version?

Yes. Esper Firebolt converts the operating system on the machine you already own. It does not port your application to Android.

The fastest way to answer the software gate is to ask your ISV or enterprise app development team directly. Confirm whether a supported Android build exists and where it sits on their roadmap. If the answer is no and not planned, the flip is off the table for that fleet, regardless of how strong the hardware case looks. The only option there is to switch ISVs. 

Set expectations on one more point: preserving application data or state across the flip is not an automatic, shipping capability. 

If you need to prove Android in production before committing, a dual-boot install keeps the Windows partition on disk. You select the default OS as a Firebolt configuration.

If a pilot doesn't hold, you just boot into Windows, because it never left. Dual-boot applies to x86 and supports Android up to version 13, which is worth confirming against your application's minimum Android target.

The practical order of operations starts with your software, not your hardware. Identify your ISV, confirm whether an Android build exists, and only then scope the hardware. If you are looking for Android ISVs servicing your industry, we know them. AOSP for dedicated devices is the Android target the flip lands on, and it's the model behind most restaurant and POS deployments. When you're ready, route the specific device and app to a scoped assisted evaluation.

Which devices have a proven flip path today?

Most x86 hardware configuration paths are mature and proven in production today. But given the richness and diversity of the x86 device world, we haven’t covered everything. Which bucket your hardware falls into is a technical fact about the device, not a marketing claim, and it's confirmed per model variant. Several classes of 2016-era Windows terminals have been validated as flip candidates. 

A validated class is not a promise about a specific unit. Every device is confirmed per variation before any commitment. Watch the model year, too: a device brand relaunched in a later year may not carry the 2016-era Windows IoT LTSB base that makes the class a candidate in the first place.

As far as compatibility is concerned, not-yet-supported is not the same as impossible. Eligibility is assessed at bring-up, where the image and bootloader behavior on your specific hardware get tested directly. If your device isn't on the current list, route it to a scoped assisted evaluation. Whether your fleet should move off Windows at all is a useful question to settle first if you're still deciding.

A scoped assisted evaluation confirms both gates on your actual hardware and your actual application. It tests the behavior on the device, and it verifies the Android build for your POS or kiosk software. Nothing is committed until this initial technical validation is done.

Set the commercial expectation up front. Firebolt is scoped and priced to your specific hardware and peripheral configuration, not sold at a flat per-device rate. Where the support work across device variants is large, expect meaningful engineering lift before a true proof of concept.

Brand and form factor don't decide eligibility. The device, required peripherals, and Android app availability do.

Most teams expect a brand-keyed compatibility list. They want to look up the manufacturer, find a checkmark, and move on. That instinct produces wrong answers, because eligibility is decided one layer down.

Eligibility is decided by the device’s complete build from BIOS/UEFI to hardware components, and by whether the application software has an Android build. Two devices from the same manufacturer can land in different buckets, because they ship different implementations. The badge tells you almost nothing on its own.

The application gate cuts across every brand at once. A Windows-only POS app disqualifies a flip no matter the OEM. Asking "is my brand supported" skips the two questions that actually decide the outcome.

A static compatibility list also ages badly. Model-year refreshes with different components shift underneath it. A per-SKU answer at bring-up reflects what's true for your hardware right now, not what a table claimed when you purchased.

Esper answers flip eligibility per fleet, not with a blanket yes

Whether you can flip an x86 device from Windows to Android comes down to the specific hardware and whether your software has an Android build, not the logo on the case. That's why Esper confirms eligibility per fleet instead of hand-waving a blanket yes.

‍See how Esper Firebolt works

Frequently Asked Questions

Can any x86 device be flipped from Windows to Android?

No. There's no "any x86 device" answer. A device qualifies only when it can run a supported Foundation image and its POS or kiosk application has an Android build. Both gates are investigated per device.

Does my POS software need an Android version to flip?

Yes. Firebolt converts the operating system, not your application. Windows-only software cannot be flipped in place. Confirm an Android build exists before you scope hardware.

Which x86 bootloaders does the flip support?

The flip depends on the design of your hardware system, not on it being x86 and running Windows today. If there are blockers to running Foundation on your hardware, we’ll scope out the engineering work required with you. 

How do I find out if my specific device and software are supported?

Route your specific device to a scoped assisted evaluation, where Esper investigates compatibility for qualified enterprises before any commitment.