A developer named Ammaar Reshi has published WindowsiOS, an open-source project that reportedly runs Windows 11 24H2 ARM64 locally on an iPhone Duo without jailbreaking the phone. According to Techgenyz and other outlets covering the release, Google’s Gemini 4 Carbon model helped write the code.

Windows 11 on iPhone Duo is the kind of headline that sounds like a prank, yet the reported details (a virtual machine, touch controls, no cloud streaming) describe real engineering work.

Reshi summed up the project in a public post, which coverage of the release quoted: “I used Gemini 4 Carbon to get Windows 11 running on my iPhone Duo!” That single sentence drives most of the attention. It also invites overreading, so this analysis separates what the reports confirm from what they do not.

Gemini 4 Carbon is the model at the center of the story, and readers who missed its rollout can catch up in our piece on the Gemini 4 Carbon intro price and uneven availability. Below, we walk through how WindowsiOS reportedly works, what the setup demands, how much credit the AI deserves, which claims remain unverified, and what the project signals for AI-assisted systems programming.

Add Shattered once in the Google app and our stories show up in your news suggestions.

WindowsiOS is an open-source project attributed to Ammaar Reshi. Its stated goal is simple to describe and hard to pull off: boot a full desktop build of Windows 11 on an iPhone and let the user touch the screen to drive it. Reports from Techgenyz and others identify the guest operating system as Windows 11 24H2 ARM64, the version of Windows built for ARM processors rather than the x86 chips found in most PCs.

The ARM64 detail matters. An iPhone runs on Apple silicon, which uses the same ARM instruction family that Windows 11 on ARM targets. A guest that speaks the host’s native instruction set avoids the heaviest cost of emulation, which is translating every instruction from one architecture to another. That alignment does not make the job easy, but it removes one of the largest obstacles.

The project’s open-source status also shapes how the story will age. Anyone can read the code, fork it, and test the claims. A closed demo video would leave readers guessing. A public repository lets independent developers confirm what runs, what breaks, and how much of the work came from a person versus a model.

As of this writing, the reports we reviewed describe the release but do not include independent benchmark data, and we do not cite any performance figures here.

Several details appear consistently across coverage. The project reportedly runs Windows 11 24H2 ARM64 on the device, locally, without a jailbreak. Reports state that the approach is a virtual machine built in software, paired with touch controls, and that it is neither cloud streaming nor a remote desktop connection. In plain terms, the Windows instance lives on the phone rather than on a server somewhere.

Reported functions include touch input, networking, speaker and microphone access, and a virtual keyboard and trackpad that appear when the phone is folded. That last item hints at the hardware the demo targets. A device that folds open into a larger screen and offers a different input layout when closed is a natural fit for a desktop operating system that expects a pointer and a keyboard.

The setup path is documented as well. The project requires an Apple-silicon Mac, development tools, and a Windows ARM image. That means this is a developer project today, not an app a casual user installs from a store. Techgenyz and the other outlets describe it that way, and nothing in the reports suggests a consumer release.

A virtual machine presents a guest operating system with a pretend computer. The guest sees a processor, memory, storage, a display, and input devices, and the host software supplies all of them. Reports say WindowsiOS builds this pretend computer in software and routes touch events from the phone’s screen into the guest as pointer input. Networking, audio output, and microphone access pass through the same layer.

The contrast with streaming is the heart of the story. Cloud gaming and remote desktop tools run the operating system on someone else’s hardware and send pictures to your screen. They need a good connection and a server. A local VM needs neither. Your phone does the computing, which is why the reports stress that the project is not a remote connection.

Two technical details stand out in the reports. First, the project uses just-in-time translation, a technique that converts guest code into host code while the program runs. Second, it does not rely on Apple’s Hypervisor.framework, the system component that normally hands virtualization work to the processor’s own features.

Skipping that framework is the clever part. Normal hardware-assisted virtualization on Apple platforms leans on it, and its availability on iPhones is limited by platform rules. By translating code in software, the project sidesteps the dependency. The tradeoff, which the reports do not quantify, is that software translation usually costs speed compared with hardware-assisted virtualization.

We have no verified numbers, so we do not offer any.

The documented requirements are an Apple-silicon Mac, development tools, and a Windows ARM image. The Mac acts as the build machine. The development tools compile the project and push it to the phone. The Windows ARM image supplies the operating system…