Microsoft once promised to make Android apps feel at home on Windows 11, complete with desktop windows, taskbar icons, and keyboard support. The feature arrived, worked surprisingly well, and then took an unexpected exit. Here is how the technology worked, why it mattered, what ended, and which practical alternatives remain available today.
For years, Windows users who wanted Android apps on a PC had to reach for an emulator, mirror a phone, or perform the sort of technical ritual that usually ended with 14 browser tabs and a mild headache. Windows 11 promised something cleaner: Android applications running beside regular desktop software as if they had always lived there.
The idea was genuinely exciting. A user could open an Android reading app, pin it to the taskbar, resize its window, and switch to it with Alt+Tab. Mobile games could run with a keyboard and mouse. Touch-focused apps could make Windows tablets more useful. It was not quite “your phone is now inside your laptop,” but it came surprisingly close.
However, the story did not end with Android taking over the Windows desktop. Microsoft discontinued the technology after only a few years. Understanding what happened requires looking at the original architecture, the compromises behind the app catalog, and the alternatives that survived.
What Microsoft Originally Announced
When Microsoft unveiled Windows 11 in June 2021, Android app support was one of the operating system’s most attention-grabbing features. The company said users would be able to discover Android apps in the Microsoft Store and obtain them through the Amazon Appstore.
That arrangement involved two storefronts. The Microsoft Store acted as the familiar front door, while Amazon supplied the Android catalog and account system. It was a little like entering a department store only to discover a second, smaller store behind the electronics counter.
The feature did not ship with the first public release of Windows 11 in October 2021. Instead, Microsoft introduced it gradually through the Windows Insider Program. A public preview arrived for American users in February 2022, and support later expanded into additional markets. By September 2022, Microsoft said the preview offered more than 20,000 Android apps and games on eligible devices.
Users could install titles such as Kindle, Audible, TikTok, and a selection of mobile games. Installed Android apps appeared in Windows Search and the Start menu rather than remaining trapped inside a traditional emulator dashboard.
How Android Apps Worked on Windows 11
The Windows Subsystem for Android
The technology behind the experience was called the Windows Subsystem for Android, commonly shortened to WSA. Its name echoed the Windows Subsystem for Linux, although the two products served different purposes.
WSA created a virtualized Android environment inside Windows 11. Early versions were based on the Android Open Source Project, or AOSP, and included a Linux kernel. Instead of booting a complete phone interface, the subsystem presented each supported Android application in its own Windows-style window.
That distinction mattered. A conventional emulator often displays an entire simulated phone, complete with virtual navigation buttons and a tiny home screen floating on a giant monitor. WSA integrated applications more directly into the desktop. Users could resize them, snap them beside other programs, receive notifications, and pin them to the taskbar.
Integration With Windows Features
Android applications could participate in several familiar Windows behaviors. Clipboard sharing made copying text between mobile and desktop apps possible. File access improved over time, while input support expanded to include keyboards, mice, touchscreens, pens, and certain controllers.
Microsoft also released updates that improved networking, camera compatibility, picture-in-picture behavior, graphics performance, and application resizing. The subsystem eventually moved to Android 13, demonstrating that it was more than a one-week experiment forgotten behind the office vending machine.
Nevertheless, Android applications remained virtualized workloads. Starting the subsystem consumed memory and processor resources, and the first app could take longer to open while WSA woke up. Performance depended heavily on the PC, the application, and whether the program had been designed to adapt to a large screen.
Hardware and Software Requirements
Running Android apps locally required more than simply installing Windows 11. Hardware virtualization had to be supported and enabled. Microsoft recommended solid-state storage, and smoother performance generally required at least 8 GB of RAM. Systems with 16 GB had more breathing room when WSA, a web browser, and several desktop programs were open simultaneously.
Users also needed a supported processor and an eligible Windows configuration. Requirements and regional availability changed during the feature’s lifetime, which created occasional confusion. A computer could run Windows 11 perfectly well yet still encounter an unavailable Amazon Appstore listing or a virtualization-related installation error.
This complexity weakened the feature’s most attractive promise. Android apps were supposed to feel like ordinary Windows programs, but reaching that stage sometimes required checking BIOS settings, Windows components, Store updates, region support, and processor compatibility. That is a lot of paperwork for opening a mobile crossword puzzle.
The Biggest Limitation: No Official Google Play Store
The most important weakness was not technical performance. It was the app catalog.
Most Android users obtain applications through Google Play, and many apps rely on Google Play Services for sign-in, location features, notifications, payments, maps, or other functions. Windows 11’s official Android environment used the Amazon Appstore instead. Consequently, numerous familiar Google apps and popular third-party titles were missing.
This made WSA less useful to mainstream users. The technology could run Android software, but the official installation path did not provide the Android library people expected. It was similar to opening a well-equipped movie theater that only screened a fraction of the films audiences wanted to watch.
Technical users discovered ways to sideload APK files or modify the subsystem, but those methods were not the supported consumer experience. Sideloading also introduced security, compatibility, and update concerns. Downloading an APK from an unknown website remains an excellent way to turn a convenient app experiment into an exciting conversation with antivirus software.
What Android Apps Added to the Windows Experience
Despite its limitations, Android support filled several legitimate gaps in the Windows ecosystem.
Mobile-Only Services on a Larger Screen
Some businesses and online communities released capable mobile apps but offered weak desktop alternatives. Running those applications locally provided access to mobile features without repeatedly reaching for a phone. Reading, messaging, smart-home, education, and lightweight content apps were natural candidates.
A Better Experience on Windows Tablets
Windows has strong desktop software but a comparatively limited selection of touch-first applications. Android apps could make a convertible laptop or Surface-style tablet more versatile. A portrait-oriented app was often more comfortable under touch than a website designed around a mouse pointer and several acres of navigation menus.
Convenient Mobile Gaming
Mobile games benefited from larger displays and, when supported, physical input. However, results varied. Games built exclusively for touch controls could feel awkward with a mouse, while some titles did not scale correctly or perform as expected. A 27-inch monitor does not automatically make every phone interface majestic; sometimes it merely produces a much larger “Tap here” button.
New Testing Options for Developers
WSA gave developers another way to test Android applications on Windows hardware. Developer Mode, Android Debug Bridge connectivity, and diagnostic tools supported local testing. Still, WSA was never a complete replacement for testing on real phones, tablets, and official Google Play environments.
Why Microsoft Ended the Windows Subsystem for Android
Microsoft announced the deprecation of WSA in March 2024. The Amazon Appstore and applications dependent on the subsystem remained supported until March 5, 2025. After that date, both products reached end of support and became unavailable through the Microsoft Store.
Microsoft did not publish a detailed explanation of the business decision. Any single claimed cause should therefore be treated as analysis rather than confirmed fact. Still, several weaknesses probably reduced WSA’s long-term value.
- The Amazon Appstore catalog was much smaller than Google Play.
- Many Android apps were already available as capable websites or Windows applications.
- Virtualization added memory, storage, and maintenance costs.
- Some mobile interfaces did not translate well to large PC screens.
- Users often had to enable virtualization or troubleshoot compatibility.
- Developers had limited incentive to optimize apps for a relatively small Windows audience.
In short, the engineering was impressive, but the ecosystem never became essential. A compatibility layer is only as valuable as the applications people can conveniently obtain through it.
Can You Still Install WSA on Windows 11?
New users cannot officially download the Windows Subsystem for Android or Amazon Appstore from the Microsoft Store. Microsoft’s software terms state that the products have been unavailable there since March 5, 2025.
Old installations may continue operating on some computers, but they are unsupported. That means users should not expect security fixes, Android platform upgrades, application compatibility work, or technical assistance. A future Windows update or app change could break an existing setup.
Unofficial packages and modified WSA projects can be found online, but installing an abandoned subsystem from an unverified source involves meaningful risk. Users would be trusting the distributor with a virtualized environment capable of running third-party Android packages. For banking, business, health, or password-related applications, unsupported builds are particularly difficult to justify.
Practical Ways to Run Android Apps on Windows 11 Today
Use Microsoft Phone Link
Phone Link connects a compatible Android phone to Windows. Depending on the phone model, users can view notifications, send messages, make calls, access recent photos, mirror the screen, or stream mobile apps into separate windows.
The important difference is that the app still runs on the phone. Windows displays and controls it remotely. This approach avoids maintaining a complete local Android subsystem, but the phone must remain connected, and advanced app streaming is limited to supported devices.
Use Google Play Games on PC
For gaming, Google Play Games on PC is the most direct official alternative. Google provides a Windows client for compatible Android games, with features such as keyboard support, cross-device progress, and access to a growing catalog.
Google lists minimum requirements that include Windows 10 or newer, an SSD with available space, 8 GB of RAM, four physical CPU cores, a compatible graphics processor, administrator access, and enabled hardware virtualization. The service focuses on games, so it does not replace WSA for general Android productivity apps.
Choose a Reputable Android Emulator
Established Android emulators remain useful for games, development, and mobile-only applications. They often provide resolution controls, key mapping, multiple instances, virtual location tools, and access to a broader application catalog.
Users should download emulators only from official vendor websites, review bundled software carefully, and avoid entering sensitive information into questionable environments. Emulators can also compete with other virtualization products, so running several at once may make a powerful PC behave as though it is trudging through wet cement.
Check for a Web or Native Windows Version
Before emulating anything, look for a progressive web app, browser version, or native Windows client. Web applications often use fewer resources and receive updates automatically. Microsoft Edge and Chrome can install supported websites as app-like windows with their own taskbar icons.
This solution is less dramatic than running Android inside Windows, but it is frequently faster, safer, and easier to maintain. Technology occasionally rewards the boring answer.
Real-World Experience: What Using Android Apps on Windows 11 Felt Like
The best part of the original WSA experience was how ordinary it could feel. After an Android app was installed, it appeared in the Start menu beside desktop software. Launching it produced a normal window rather than an illustration of a smartphone. It could be moved to another monitor, snapped beside a browser, minimized, or pinned to the taskbar.
For reading apps, this approach worked beautifully. A user could keep an ebook or educational app on one side of the display and notes on the other. Clipboard integration reduced the friction between mobile and desktop software. On a touchscreen laptop, scrolling and tapping felt natural enough that it was easy to forget the application had been designed for another operating system.
The illusion weakened when an app expected a narrow phone screen. Some interfaces stretched poorly, left large empty spaces, or refused to resize beyond a fixed portrait window. Tiny icons could become awkward mouse targets, while gestures designed for two thumbs did not always have intuitive desktop equivalents. A mobile app on a monitor can feel liberating, but it can also resemble a refrigerator magnet projected onto a movie screen.
Startup and Performance
The first Android app opened after a reboot was often slower because Windows needed to start the subsystem. Subsequent apps usually launched more quickly. On a PC with an SSD, a modern processor, and 16 GB of RAM, everyday utilities generally felt responsive. Machines closer to the minimum requirements could show pauses, longer loading times, or increased memory pressure.
Casual games often ran acceptably, especially when their controls translated cleanly to a mouse or keyboard. Demanding 3D titles were less predictable. Graphics drivers, architecture translation, app optimization, and virtualization overhead all influenced performance. The feature was convenient, but it was not a magical gaming accelerator hiding behind the Start button.
The Catalog Problem in Daily Use
The biggest disappointment usually arrived before an app even launched: it was not in the Amazon Appstore. Users familiar with Google Play naturally searched for favorite communication, banking, productivity, and entertainment apps. Many were unavailable, and others depended on Google services that the official WSA environment did not include.
This created an odd gap between possibility and practicality. Windows 11 could run Android apps impressively, yet it could not officially install many of the applications that made people interested in the feature. Enthusiasts could sideload software, but ordinary users were unlikely to treat command-line tools and APK research as a relaxing afternoon activity.
Life After WSA
Today, the best replacement depends on the goal. Phone Link is convenient when a compatible Android phone is already nearby. Google Play Games on PC offers a supported route for gaming. An established emulator provides more flexibility, while a native Windows program or web app is often the simplest choice for work.
No single replacement reproduces everything WSA attempted to provide. Phone Link streams from another device, Google’s client concentrates on games, and emulators feel more separate from Windows. Even so, these options can cover most practical needs without relying on an unsupported subsystem.
The short life of WSA also offers a useful lesson. Technical integration alone does not create a successful platform. Users need a complete catalog, developers need a reason to participate, and the experience must be easier than opening the same service in a browser. WSA built an elegant bridge between Android and Windows, but too few important apps crossed it.
Conclusion
Android apps did come to Windows 11, and for a while they offered an impressively integrated desktop experience. The Windows Subsystem for Android made mobile applications behave more like native Windows programs, but limited app availability and ecosystem challenges prevented the feature from becoming indispensable.
With WSA and the Amazon Appstore now unsupported, users should choose maintained alternatives instead of depending on unofficial copies. Phone Link, Google Play Games on PC, trusted emulators, progressive web apps, and native Windows software each solve a different part of the problem. Android has not disappeared from the PC; it simply arrives through several smaller doors rather than one official Windows subsystem.
