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.
Don't miss new tech stories on Google
Add Shattered once in the Google app and our stories show up in your news suggestions.
What WindowsiOS Is and Who Built It #
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.
What the Reports Confirm About Windows 11 on iPhone Duo #
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.
| Claim | Status | Basis |
|---|---|---|
| WindowsiOS is open source and attributed to Ammaar Reshi | Confirmed | Multiple reports, including Techgenyz |
| Runs Windows 11 24H2 ARM64 locally on an iPhone Duo, no jailbreak | Confirmed (as reported) | Project coverage across outlets |
| Software VM with touch controls, not cloud streaming or remote desktop | Confirmed (as reported) | Project coverage across outlets |
| Touch, networking, speaker, microphone, virtual keyboard and trackpad when folded | Confirmed (as reported) | Project coverage across outlets |
| Uses just-in-time translation, not Apple’s Hypervisor.framework | Confirmed (as reported) | Project coverage across outlets |
| Gemini 4 Carbon helped develop the project | Confirmed (as reported) | Reshi’s post and several outlets |
| Development took about two hours | Unconfirmed | One report only |
| Apple or Microsoft endorsed the project | Unconfirmed | No official statement found |
How the Virtual Machine Approach Works #
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.
Just-in-Time Translation Without Hypervisor.framework
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.
What It Takes to Set Up WindowsiOS #
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 itself, which the project does not bundle.
That last point deserves attention. Windows is licensed software, and the reports describe the user supplying their own image. This is the standard pattern for emulator and VM projects, because it keeps the open-source repository free of Microsoft’s code. It also puts licensing questions on the user, a topic we return to later.
Anyone who has set up virtualization on a PC knows the ritual of flipping a firmware switch before a hypervisor will start. Our walkthrough on how to enable virtualization in BIOS covers that PC-side step. The iPhone story runs the other direction. There is no firmware toggle to flip, so the developer worked around the missing feature in software instead.
Gemini 4 Carbon’s Role: Helper, Not Sole Author #
Reports from several outlets, Techgenyz among them, identify Gemini 4 Carbon as the AI model used to help develop WindowsiOS. The key verb is help. Available coverage describes the model assisting a human developer, not independently producing the whole implementation. Reshi’s own sentence says he used the model to get Windows running, which is a statement about a tool in a person’s hands.
That distinction matters for how readers should weigh the headline. A claim that an AI alone built a Windows-on-iPhone VM would be extraordinary and, per our fact check, is unconfirmed. A claim that an experienced developer used a strong coding model to speed up hard parts of the work is ordinary by 2026 standards and consistent with every report we reviewed.
Gemini 4 Carbon has drawn attention for serious engineering uses before. We covered its role in a verification effort in our report on Gemini 4 Carbon access, Signal’s libsignal and 6.5M lines of Lean proofs. WindowsiOS adds a very different data point. One is formal verification of cryptographic code. The other is low-level systems work that mixes translation, device input, and operating system plumbing.
The Two-Hour Claim Does Not Hold Up as Fact #
One report claims development took about two hours. We list that as unconfirmed, because it appears in a single report and Reshi’s public post, as quoted, says nothing about duration. The number is catchy, which is exactly why it travels. A two-hour build time would suggest that AI has collapsed months of systems work into an afternoon, and that story spreads fast on social feeds.
Several explanations could fit a short stretch of visible work without implying a short project. A developer may have spent earlier weeks studying how Windows boots on ARM, then used the model for one final push. The two hours could describe a single session, a recording, or a final integration pass. We do not know, and neither do the reports we reviewed.
The practical advice is to treat the figure as a rumor attached to a real project. If Reshi or an independent reviewer documents a timeline, the picture will sharpen. Until then, citing two hours as fact would repeat an unverified claim.
The iPhone Duo Question: No Official Specs #
The device name raises its own problem. Apple has not announced a product called the iPhone Duo, and we found no official price, release date, retail specification, or technical specification for it. The reports use the name, and the coverage mentions a folded mode with a virtual keyboard and trackpad, but those descriptions come from the project’s behavior and not from any Apple document.
Readers should therefore avoid building purchase or investment decisions on the name. We cannot say how large its screen is, how much memory it holds, what chip powers it, or whether it will ever go on sale. Anyone who quotes numbers for it today is guessing.
What we can say is narrower and still interesting. The project runs on the device the reports call an iPhone Duo, the operating system it boots is a real shipping Windows build, and the code is public. The mystery around the hardware does not erase the software result, but it does limit how far anyone can generalize from a single demo.
Apple and Microsoft: Silence, Not Endorsement #
No report we reviewed shows Apple announcing or endorsing the iPhone Duo or WindowsiOS. The same goes for Microsoft. We found no statement from either company approving Windows 11 running through the project, and we treat both endorsements as unconfirmed.
That silence fits history. Both companies tend to stay quiet about independent hobbyist projects until a project grows large or crosses a policy line. For Apple, a tool that sidesteps a platform component raises questions about its app rules. For Microsoft, the open question is licensing, since the project depends on a user-supplied Windows image. Neither question has an official answer in the coverage.
The developer community will likely test those boundaries. If the code stays public and the approach avoids jailbreaking, the project occupies a gray zone that could attract attention in either direction. We will update this story if either company responds.
Windows on a Phone: How the Approaches Compare #
People have tried to bring Windows to phones in several ways. The table below compares the three broad approaches on the questions that matter most to users: where the operating system runs, whether a connection is needed, and what the reports say about WindowsiOS. We deliberately use qualitative descriptions, because we have no verified performance data for any of them.
| Approach | Where Windows runs | Needs a network | Main tradeoff |
|---|---|---|---|
| Cloud streaming | Remote data center | Yes, constantly | Depends on connection quality and a subscription or host |
| Remote desktop to a PC | Your own PC | Yes | Needs a PC that stays on and reachable |
| Local VM (WindowsiOS, as reported) | On the phone | No for the OS itself, yes if the guest uses networking | Software translation, developer-grade setup |
| Hardware-assisted VM on Apple platforms | On the device | No | Relies on Hypervisor.framework, which WindowsiOS avoids |
The row that stands out is the local VM. It is the only option that puts the full operating system in your pocket without a server. It is also the least polished. Streaming and remote desktop tools are mature products with support teams. WindowsiOS is a repository and a build process.
Memory design plays a role in how well any local approach can work. Apple’s chips share one memory pool between the processor and graphics, which we explained in our comparison of unified memory versus traditional RAM. That shared pool is one reason an ARM guest on Apple silicon has a better shot at a usable experience than it would on older mobile designs, though the reports offer no measurements to prove it.
Market Impact: AI-Assisted Systems Engineering Goes Mainstream #
The market story here is less about phones and more about what coding models now touch. For years, AI coding assistants earned praise for web apps, scripts, and tests. Low-level work such as binary translation, device input handling, and operating system integration sat on the hard end of the spectrum. A public project that reports using Gemini 4 Carbon for that work shows the frontier moving.
For AI vendors, a demo like this works as marketing. Developers love a vivid example, and a Windows desktop on a phone is vivid. Competing model makers will notice, and we expect them to point to their own systems-level showcases. The comparison tends to play out in public repositories, and open-source results are easy to inspect, which keeps claims honest.
For developers, the lesson is practical. Strong models can shorten the path through unfamiliar territory, but they do not replace the person who knows what to ask. Reshi’s post credits the model with helping, and the project required a developer to choose the approach, set it up on real hardware, and judge when it worked. Teams weighing local tools should read our guide to the [best local LLM for coding](https://shattered.io/best-local-llm-for-coding-free-weights-vs-2-api-2026/), which compares free open weights with paid APIs.
Phone makers and PC makers should watch too. If hobbyists can run a desktop operating system on a pocket device in software, the line between a phone and a laptop looks thinner. We stress the conditional because a rough demo is not a product, and the reports include no usability or battery data.
Historical Context: Why Running Desktop Software on Phones Keeps Returning #
The idea of a phone that doubles as a computer is old. Docking concepts, desktop modes, and remote access tools have all circled the same dream: carry one device and use it as a full computer when a screen and keyboard appear. Each attempt ran into the same set of walls. Phone processors were slower, software ecosystems were separate, and platform owners limited what apps could do.
Two shifts changed the odds. First, mobile chips grew powerful enough to compete with laptop chips in many tasks. Second, Windows itself gained a mature ARM build, so a guest and a host can share an instruction family. Windows 11 24H2 ARM64, the build named in the reports, sits on that second shift.
Emulation has a long record of community-driven progress. Hobbyist teams routinely crack problems that vendors consider too niche, then see their techniques adopted more widely. Just-in-time translation is one of those techniques, used in many emulators because it often runs faster than interpreting each instruction one at a time. WindowsiOS applies that old tool to a new target.
The Apple angle also has history. Apple has long drawn a firm boundary around what code may run on iPhones, which is why projects like this depend on workarounds. A Mac-based build process and a no-jailbreak approach reflect that boundary. Developers adapt, and the platform owner decides how to respond.
Risks, Limits, and Open Questions #
Several limits are worth stating plainly. The reports offer no verified performance numbers, so we cannot say whether Windows feels smooth or sluggish on the phone. They do not describe battery impact, thermal behavior, or app compatibility. They also do not say how stable the build is across repeated use. Any of those could turn a striking demo into a frustrating daily tool.
Security deserves a mention as well. Running a full operating system inside another app creates a layered environment, and each layer adds surface for mistakes. Users who connect the guest to a network should treat it like any other Windows machine, with updates and sensible habits. The project’s open code helps here, since security researchers can audit it, but audits take time.
Licensing is the remaining gap. The project needs a user-supplied Windows image, and Microsoft’s terms govern how that image may be used. We found no Microsoft statement on this project, so we make no claim about its compliance. Readers who plan to try it should read the license terms attached to their own Windows image.
Signals That Would Change the Picture
| Signal | What it would tell us | Current status |
|---|---|---|
| Independent reviewer benchmarks | Whether the VM is usable or only a demo | None found in reports |
| Reshi publishing a development timeline | Whether the two-hour claim holds | Not published in coverage reviewed |
| Apple statement on the iPhone Duo | Whether the hardware is real and sold | No official announcement |
| Microsoft statement on licensing | Whether Windows images may be used this way | No official statement |
| Forks or ports by other developers | Whether the method generalizes beyond one device | Not reported |
What Readers and Developers Should Do Now #
If you are a curious developer with an Apple-silicon Mac, the project’s documentation is the place to start, and you should expect developer-grade friction. Read the setup notes before you begin, confirm you have a legitimately licensed Windows ARM image, and avoid running the guest on a device you rely on for daily work until you understand the limits.
If you are a general reader, the safest reading of the story is modest. A developer used an AI model to help build an open-source VM that reportedly runs Windows 11 on a phone. That is a real and interesting result. It is not proof that phones replace laptops, and it is not proof that AI builds operating system software unaided.
If you follow AI models for a living, the takeaway is about calibration. Treat vivid demos as evidence of direction and not as evidence of reliability. Ask who did the judging, what remains unverified, and whether the code is public. WindowsiOS passes the last test, which is a point in its favor. For wider context on the models behind stories like this, see our [AI and machine learning coverage](https://shattered.io/ai-machine-learning/).
Predictions: Where This Goes Next #
The following are our own forecasts, not reported facts. They rest on the pattern of the story so far, and any of them could prove wrong.
- Other developers will fork the project. Open code that reportedly works draws copycats. We expect forks that target other Apple devices and other guest operating systems, and we expect at least some to report bugs the original misses.
- Independent testers will publish usability reports. A project this visible attracts reviewers. Their findings on speed, battery, and stability will decide whether the demo becomes a toy or a tool.
- AI vendors will copy the showcase format. Rival model makers will highlight their own low-level engineering demos, since a vivid public project sells better than a benchmark chart.
- Platform owners will clarify their rules. If the project gains traction, expect Apple or Microsoft to address the platform and licensing questions, either by statement or by policy change.
- The two-hour claim will fade or get corrected. As reporting matures, the unverified duration will either gain a source or drop out of coverage.
The common thread is that open code invites scrutiny. Whatever the project becomes, the public repository means the community, and not a press release, will settle the open questions. People with more specific interest in local AI setups can also look at how Apple-silicon machines might pool resources in our report on the Apple Harbor app for local AI clusters.
The Takeaway on Windows 11 on iPhone Duo #
Strip away the hype and the story holds together. Ammaar Reshi released WindowsiOS, reports say it runs Windows 11 24H2 ARM64 locally on an iPhone Duo without a jailbreak, and Gemini 4 Carbon helped with development. The method is a software VM with just-in-time translation, and it skips Apple’s Hypervisor.framework. Setup needs an Apple-silicon Mac, development tools, and a Windows ARM image.
Everything beyond that stays soft. No official word exists on the iPhone Duo’s price, release date, or specifications. Apple and Microsoft have not endorsed the project in anything we found. The two-hour development claim rests on one report. And Gemini 4 Carbon did not build the thing alone, since the coverage describes a model that helped a developer.
That honest summary is still a strong story. It shows how far AI-assisted engineering has moved into hard systems territory, and it shows that open code can turn a bold claim into something anyone can test.
FAQ: Windows 11 on iPhone Duo and Gemini 4 Carbon #
Who built WindowsiOS?
WindowsiOS is an open-source project attributed to Ammaar Reshi. Reports from Techgenyz and other outlets name him as the developer, and he publicly wrote that he used Gemini 4 Carbon to get Windows 11 running on his iPhone Duo.
Does Windows 11 on iPhone Duo run locally or stream from the cloud?
Reports say it runs locally. The project uses a virtual-machine approach in software with touch controls, and coverage states it is not cloud streaming and not a remote desktop connection.
Does the project require a jailbreak?
No. Reports say the project reportedly runs Windows 11 24H2 ARM64 on the iPhone Duo without jailbreaking the device. It does rely on a Mac-based setup, though.
What do I need to set it up?
The documented setup requires an Apple-silicon Mac, development tools, and a Windows ARM image. It is a developer project and not a consumer app.
Did Gemini 4 Carbon build the whole thing?
No evidence supports that. Reports identify Gemini 4 Carbon as the AI model used to help develop the project, and they describe it as assisting a developer, not independently creating the full implementation.
Did development really take two hours?
That claim is unconfirmed. It appears in one report, and Reshi’s public post as quoted does not mention a timeline. Treat it as unverified until a documented source appears.
Is the iPhone Duo a real Apple product?
We found no official Apple announcement of a device by that name. Any price, release date, or specification for it is unconfirmed, so avoid relying on figures you see elsewhere.
Have Apple or Microsoft endorsed WindowsiOS?
Neither company has endorsed it in anything we found. Official support from Apple or Microsoft is unconfirmed, and the project relies on a user-supplied Windows image, so licensing remains the user’s responsibility.