Madeira and DroidDeck Run Windows Games on Phones, No Cloud

A Windows game running on a phone, offline, with nothing streamed from a server somewhere else. That's the claim, and unlike most phone-gaming hype this one comes with a parts list instead of an adjective. The channel Water CS2 laid out how two open-source projects, Madeira on iOS and DroidDeck on Android, are reportedly getting unmodified Windows PC titles executing natively on mobile silicon, no cloud rig doing the work off-screen.

The trick, per the channel's breakdown, isn't new magic so much as recycled Valve plumbing pointed somewhere Valve never aimed it. Translation layers and compatibility tooling built for the Steam Deck's x86 chip have apparently been retooled for ARM, and once you have that, a phone stops being a thin client and starts being an actual, if cramped, PC.

The parts doing the heavy lifting

According to Water CS2, the stack leans on pieces Valve already open-sourced for its own ecosystem:

• FEX-Emu, handling the x86-to-ARM instruction translation that lets unmodified Windows binaries even start
• a native ARM64 build of the Steam client itself, rather than a shimmed-in x86 version run through emulation on top of emulation
• ARM-compiled Proton layers, doing the same Windows API translation on phone chips that it normally does on Deck hardware

Stack those three and you get something that, on paper, sidesteps both a cloud subscription and the usual mobile OS sandboxing that keeps this kind of software out in the first place. That's the part worth sitting with: iOS and Android are not exactly welcoming environments for running arbitrary unsigned executables, and getting around that without Apple's or Google's blessing is its own small feat of engineering stubbornness, 'sideloaded' doing a lot of quiet work in that sentence.

What nobody's measured yet

Here's where I put the brakes on, because a demo booting is not a frame-time graph. Water CS2's description doesn't hand over benchmark numbers, battery drain, thermal throttling curves, or a list of which titles actually run versus which ones crash to desktop the moment a shader compiles. Translation layers running on phone-class ARM chips, usually Snapdragon handhelds rather than your average iPhone, are going to hit a thermal ceiling that a Deck's fan and vapor chamber don't have to fight nearly as hard. x86-to-ARM translation already taxes a chip before a single polygon gets drawn; stacking Proton on top of that is asking a phone to do two jobs it wasn't built for, simultaneously, without the active cooling a dedicated handheld gets away with.

GitHub links for both Madeira and DroidDeck are out there for anyone who wants to test this instead of trusting a thumbnail. Test it yourself before you believe a single frame of marketing footage, because open-source and offline don't automatically mean playable, and the gap between 'it launched' and 'it's running at a number you'd actually tolerate' is exactly where projects like this tend to go quiet.