Sources: Microsoft's Project Astoria for emulating Android apps on hold indefinitely, may be shelved completely
Microsoft's Project Astoria and Android app emulation not happening anytime soon — During Microsoft's Build conference earlier this year the company announced their software Bridges for developers.
Context & Ripple Effects
Project Astoria was unveiled at Build 2015 as part of Microsoft's Bridges program, pitched alongside iOS and Win32 porting tools as a way to close Windows' app gap — an approach Ars Technica framed at the time against similar Android-compatibility plays by BlackBerry and IBM in its comparison of those strategies. This report says the Android leg of that plan is now on indefinite hold and may never ship.
The hold proved terminal: within months Microsoft formally canceled Astoria while keeping the iOS and Win32 Bridges alive, and the idea resurfaced years later as project Latte, reportedly aimed at letting developers bring Android apps to Windows with little to no code change as early as 2021.
First-order effects
- Developers who had pinned Windows 10 app plans on Astoria must fall back on the surviving iOS and Win32 Bridges or write native UWP code, since the Android emulation path is off the table indefinitely.
- Microsoft's Bridges program effectively drops from three pillars to two, leaving the Windows Store short of the Android catalog that was supposed to pad it.
Second-order effects
- Without Android emulation, the burden of filling Windows' phone-era app gap shifts entirely onto the iOS bridge and native development — the same trade-off BlackBerry faced when its own Android runtime failed to attract a viable catalog.
- Any partner or OEM counting on Android apps to make Windows devices competitive now has no near-term compatibility story to sell against iOS and Android hardware.
Third-order effects
- If the pattern holds, Android-on-Windows becomes a recurring promise rather than a shipped product: the shelving here precedes the Latte revival report, suggesting each attempt gets rebuilt rather than abandoned outright.
- Structurally, the episode points toward compatibility layers being treated as strategic options — announced to reassure developers, paused when maintenance costs bite — rather than committed platform infrastructure.
The trend: Microsoft keeps cycling through Android-compatibility schemes for Windows — announce, shelve, revive years later — because the underlying app-gap problem never gets solved any other way.