Microsoft is ending support for the Windows Subsystem for Android (WSA)

Original Article ↗ Hacker News Discussion ↗

Microsoft’s decision to end support for the Windows Subsystem for Android (WSA) raises questions about the viability of Android apps on the desktop and the company’s long‑term commitment to experimental platforms. Commenters point to low usage, the reliance on Amazon’s limited app store instead of Google Play, and the high engineering cost of tracking Android releases as likely reasons for the shutdown, while noting that WSL for Linux remains strategically important and is not seen as at risk. Many users lament lost workflows (from Kindle and podcast apps to niche IoT controls), weigh alternatives like emulators and Waydroid, and express broader frustration with big vendors repeatedly launching and then abandoning platforms.

Announcement & Timeline

  • WSA support ends in 2025; announcement and EOL date were effectively made together, surprising many who feel it “just came out.”
  • Feature had been in beta / limited rollout for years but was never widely available; some regions still don’t have it.

Comparison to WSL and Microsoft Strategy

  • Many see WSL as critical and heavily used (especially for ML/AI and dev) and believe it’s safe; WSA is viewed as a niche “toy” by comparison.
  • Some confusion between older Android‑on‑Windows attempts (Project Astoria, Your Phone / Phone Link) and WSA.
  • A few speculate that Microsoft’s broader embrace of Linux makes them more likely to double down on WSL than on WSA.

Why WSA Failed (Per Thread)

  • Core limitation: tied to Amazon Appstore, which is considered sparse and unappealing; most “good” apps are missing.
  • Lack of Google Play Store and Play Services is seen as fatal; Google’s CTS/GMS requirements and business incentives make official cooperation unlikely.
  • Maintaining Android compatibility is described as a heavy, ongoing engineering burden even for Google; doing this for a small, niche Windows feature may not be worth it.
  • Discovery and onboarding were poor (store friction, insider rings confusion, little promotion).

Real-World Usage & Reactions

  • Minority but real use cases: Kindle and other Android-only readers, mobile-banking / ISP apps, smart‑device controllers, challenger banks, podcast clients, camera viewers, some games.
  • Android devs on Windows report WSA was nicer and faster than traditional emulators, especially for MAUI and layout testing.
  • Others say the standard x86 emulator with virtualization is “fine,” and saw WSA as redundant.
  • Some ARM Windows buyers feel especially burned, having chosen hardware expecting long-term WSA support.

Alternatives Mentioned

  • Android emulators (BlueStacks, LDPlayer, Android‑x86, Google Play Games for Windows).
  • Waydroid on Linux (sometimes via WSL2, though kernel limitations apply).
  • Phone mirroring / “apps on PC” via Phone Link, Samsung DeX, scrcpy, KDE Connect, Google Messages on Web, etc.

Trust, Platform Risk, and Broader Context

  • Several compare this to other killed Microsoft platforms (Silverlight, J++, “Your Phone” variants) and argue it erodes trust.
  • Some call for norms like minimum support contracts or open‑sourcing discontinued subsystems, though practical/legal obstacles are noted.
  • Broader takeaway debated: perhaps “phone apps belong on phones,” but others point to real desktop use cases for mobile‑only apps.