Every so often a device does something it was not meant to do, and the value is in what the attempt reveals. This week's example, per Golem: Windows 11 running on an iPhone Duo, with no jailbreak required.

The headline invites the wrong question. The interesting one is not whether it runs — it is what running costs, because Apple's rules decide that, not the chip inside the phone.

iOS forbids the feature that makes emulation fast. An efficient emulator translates or compiles guest instructions into host code, and the fast version of that trick — just-in-time compilation — requires marking memory as executable at runtime, which the platform does not allow for third-party apps. That is not an accident of configuration; it is a security boundary, and Apple has kept it. What is left is interpretation: decode one guest instruction, dispatch to a host routine, repeat. Correct, portable, and roughly an order of magnitude or more slower than translation.

Emulators have shipped on iOS anyway since Apple relaxed its rules to permit them, using exactly that trick. A JIT-less interpreter can boot an old, simple system well enough to be charming. Windows 11 is not an old, simple system: it is a modern OS with a compositor, an update stack, a driver model and a memory footprint measured in gigabytes, and on ARM it expects hardware the emulator has to invent. Add the folding display — the first iPhone screen large enough for a desktop window layout to be legible — and you have the two halves of a very good demo that is still a demo.

None of this is a criticism of whoever did it. Getting a desktop OS to a login screen under those constraints is real engineering, and it says something genuine about how much overhead modern software carries that a phone can absorb it at all.

The practical caveats are the usual ones. Without hardware acceleration, graphics are drawn by the CPU; thermals and battery become the binding constraint long before the software does; power management is approximate at best; and a device with no fan will throttle to protect itself. "It boots" and "I could work on it" are separated by the JIT rule, and no amount of cleverness closes that gap on a platform that forbids it.

Which makes the exercise a useful boundary marker. For a decade the pitch for phones has been that they are computers, and the hardware argument is now essentially settled — the silicon in a flagship phone would have been a workstation not long ago. What still separates a phone from a PC is not the transistor budget but the set of things the operating system is permitted to do. This demo shows both halves at once: enough performance to run the software, not enough permission to run it well.

Worth watching is not whether someone posts a faster video next month. It is whether the platform's rules on executable memory move — for emulators, for browsers, for anything that wants to compile at runtime. Until they do, Windows on an iPhone will remain a screenshot people admire and nobody uses.

One thing the report does not establish is how the software got onto the phone; "no jailbreak" is not the same as "from the App Store". That distinction is exactly the sort of detail that decides whether this is a curiosity or a signal.