Microsoft Cancels Project Astoria, Its Android-on-Windows Bridge
Before WSL let Windows run real Linux binaries, Microsoft was building a bridge to run Android apps on Windows 10 Mobile instead. That project was shelved in February 2016 — clearing the way for what came next.
In February 2016, Microsoft officially confirmed the cancellation of Project Astoria, the “Windows Bridge for Android” initiative that would have let developers port Android applications to Windows 10 Mobile with minimal code changes.
What Project Astoria actually was
Announced at Build 2015, Astoria let Android apps run on Windows 10 Mobile through an emulation-based compatibility layer — one of two parallel “bridge” efforts Microsoft was pursuing at the time, the other being a corresponding bridge for porting iOS code to Windows.
Why Microsoft chose to cancel it specifically
Microsoft’s own stated reasoning was one of focus: “We received a lot of feedback that having two Bridge technologies to bring code from mobile operating systems to Windows was unnecessary, and the choice between them could be confusing.” The company chose to consolidate around the iOS-focused bridge (Project Islandwood) as its single mobile-porting strategy going forward, rather than maintain both approaches in parallel.
What happened around the same time, contextually
Microsoft’s acquisition of Xamarin closed around this same period, eventually contributing to what became .NET MAUI — a cross-platform framework covering iOS, Android, and Windows through a different technical approach than either original bridge project had taken.
Why this cancellation is relevant to WSL’s own history
Astoria’s abandonment freed up organizational focus and engineering attention that, within roughly two months, contributed to a different compatibility direction entirely — Windows Subsystem for Linux’s own first public reveal came just weeks after Astoria’s cancellation was confirmed, redirecting Microsoft’s “run foreign code on Windows” ambitions from Android apps specifically toward Linux command-line tooling instead.
Sources: