<i>In order to be available on a Windows 11 device...only a small set of apps selected by Microsoft and Amazon are available.</i><p>WHY? Maybe give me a warning when installing, but at least let me try.<p>I hate how Apple gave devs the choice to make their apps unavailable on MacOS, so even though I can run theoretically run iOS apps on my M1 MBP, there are no apps I care about available for MacOS, so the feature might as well not exist.<p>At least with Android you can sideload the APK, so that's a plus..
Two interesting notes that I found here:<p>1) This also utilizes a VM for the Android system, like the Linux one.<p>2) "Unlike traditional mobile form factors, Android apps running on Windows 11 can be freely resized, should be responsive in their resizing, and can be snapped using Windows actions/gestures."
Does it also make Android development easier on Windows? i.e. can I build an Android app and open it via the subsystem, without having to run an emulator?
If you're looking for a quick way to determine if your favorite app will run well in WSA, check out this table I created (and the community contributes to).<p><a href="https://github.com/riverar/wsa-app-compatibility" rel="nofollow">https://github.com/riverar/wsa-app-compatibility</a>
First it was Windows Subsystem for Linux.<p>Now Windows Subsystem for Android has been added too.<p>It is the OS/2-ization of Windows as more subsystems are added to try to make Windows a clearinghouse for any possible desktop use.<p>What could come next?<p>Windows Subsystem for Xbox - so anything that plays on Xbox will play on Windows
I seem to remember hearing a rumor that WSL was originally intended to be a WSA, but that failed internally for some reason so they cleaned it up just enough to run console applications and shipped it as WSL1?
I was wondering with WSL already: why is it not called “Android Subsystem for Windows” but the other way around. Is there a historical reason for it to be called that way?
Yesterday I commented here [0] that having a phone running NT (because it maintains a strong ABI compatibility) with an Android Userland (for app compatibility) would solve the 3 years support window most android phones have (because of patched kernels the devs won’t care to update and recompile to the latest version).<p>I wonder how well this subsystem could run on existing phone hardware. There are, after all, Nokia phones that are running NT kernels (the last windows phone on the market).<p>[0] <a href="https://news.ycombinator.com/item?id=30079874" rel="nofollow">https://news.ycombinator.com/item?id=30079874</a>
There's always <a href="https://www.android-x86.org/" rel="nofollow">https://www.android-x86.org/</a><p>You can run a full-featured Android on any VM on a PC or Mac.
Does this mean WSL will be enabled by default on Windows, or at least that you can enable it without admin rights? That would be handy for draconian corporate environments.
I don't care if MS is a huge company, I <i>cannot</i> take this seriously with the ridiculous doublespeak.<p>The last thing was a Linux Subsystem for Windows, and this is an Android Subsystem for Windows.