Microsoft cancels Project Astoria for porting Android apps to Windows 10, still working on tools for porting iOS and Win32 apps
Microsoft: Our Android Windows 10 bridge is dead, but iOS, Win32 ones moving ahead — Microsoft's iOS bridge will be the only Microsoft toolkit …
Context & Ripple Effects
The cancellation closes out a strategy announced in April 2015, when [[a:828750|Microsoft shipped paired SDKs for bringing Android and iOS apps into the Windows Store as universal apps]]. By November, sources told Windows Central the Astoria emulator was on hold indefinitely and possibly shelved; today Microsoft made that outcome official.
What survives is the other half of that plan: the iOS bridge, which Microsoft open sourced in preview last summer and confirmed would debut within weeks in January, remains in active development alongside Win32 porting tools. Microsoft's app-gap fix is now a one-ecosystem bet.
First-order effects
- Android developers who were waiting on Astoria to bring existing apps to Windows 10 with minimal rework have lost that path entirely — their realistic options are native development, the iOS bridge via an iOS codebase, or packaged web apps.
Second-order effects
- Delivery pressure now concentrates entirely on the iOS bridge, whose debut was already imminent; any slip there leaves Microsoft with no working cross-platform porting tool at all, since Win32 tooling serves only its legacy desktop ecosystem.
Third-order effects
- If the pattern holds, Microsoft's store strategy shifts from emulating rival app ecosystems wholesale to courting them selectively — accepting that the Windows app gap gets closed only where iOS developers choose to make the jump, not by technical shortcut.
The trend: Microsoft is narrowing its app-gap strategy from a two-bridge approach spanning Android and iOS to an iOS-and-web-first bet, after its Android emulation effort stalled and died.