Search results
Android™ App Installer for Windows 10/11 makes sideloading Android applications easy for WSA, Anbox, etc.: Just double-click the app package, and you won't have to run Android Debug Bridge manually to install apps.
- WSA Manager with APK Installer
WSA Manager with APK Installer. Install and run Android APK...
- WSA Manager with APK Installer
WSA Manager with APK Installer. Install and run Android APK files on Windows 10 and 11, eliminating the need for a simulator. The app provides a comprehensive solution designed to enable Windows 10 and 11 users to seamlessly install and run Android APK files directly on their PCs.
- (159)
- Windows 10 Version 17763.0 or Higher
- Developer Tools
Install and run Android APK files on Windows 10 and 11, eliminating the need for a simulator. The app provides a comprehensive solution designed to enable Windows 10 and 11 users to seamlessly install and run Android APK files directly on their PCs.
- Overview
- Developer GitHub
- Preview Program
- Set up your development environment
- Windows Subsystem for Android™️ Settings
- Test and debug
- Input compatibility considerations for Windows devices
- Window management and resizing
- Application Lifecycle Events
- VM lifecycle considerations
Windows Subsystem for Android™️ enables your Windows 11 device to run Android applications that are available in the Amazon Appstore. Android is a trademark of Google LLC. If you're a developer interested in targeting Windows desktop devices and optimizing for the Windows operating system, this guide is for you.
To make your Android app available on Windows 11 devices, you must:
•Submit your app to the Amazon Appstore.
For more information or support:
•Sign up for updates to the Amazon Appstore on Windows program.
•Visit the Amazon developer support portal where you can find articles, forums, FAQs, or reach out for direct support via the Appstore "Contact us" page once you set up an Amazon Developer account.
Want to learn more about Windows Subsystem for Android™️ roadmap, discuss developer issues and file bugs or feature requests with the subsystem team? Visit the Windows Subsystem for Android™️ Developers GitHub.
The Windows Subsystem for Android™️ Preview Program allows users to receive early-preview builds of the Windows Subsystem for Android™ and Amazon Appstore on Windows. For more details, visit the Preview Program page.
Prerequisites
Windows Subsystem for Android™️ is available on Windows 11. Your device must meet specific requirements: Device requirements.
Install the Amazon Appstore
The Microsoft Store will automatically install Windows Subsystem for Android™️ silently in the background when either of the two following user actions are taken: 1.Install the Amazon Appstore from the Microsoft Store. Selecting Get will begin the installation of the app. 2.Install an Android app from the Microsoft Store for the first time, which will also install the Amazon Appstore.
To modify Windows Subsystem for Android™️ settings, go to: Start > All Apps > Windows Subsystem for Android™️. Learn more about specific settings app features: Manage settings for mobile apps on Windows.
Enable developer mode in Windows Settings
You must first enable developer mode. Open the Windows Subsystem for Android™️ settings. Once open, enable Developer mode under Advanced settings.
Connect to the Windows Subsystem for Android™️ for debugging
To connect to the Windows Subsystem for Android™️ VM for debugging: 1.Launch an Android app that was installed using the Amazon Appstore. 2.You can connect using adb connect with the following command (you must have adb installed):
Connect to a test device
To connect to a test device (with Windows Subsystem for Android™️ installed) on the same network from Windows/Mac: 1.On the test device (where Windows Subsystem for Android™️ is installed) open a PowerShell window and identify the IP address of the test device by running the command: 2.Using the debugging device terminal where Android Studio and the Android SDK is installed (Mac/Windows), enter the command:
Keyboard input
For text input fields handled by an on-screen virtual keyboard input method (or IME), such as EditText, apps should behave as expected. (EditText class in the Android docs). For keystrokes that cannot be anticipated by the framework, apps will need to handle the behavior themselves. If this is already implemented in-app, no extra work is required. As an example, some games may already support movement facilitated via keyboard, through w a s d keys, alongside touch input. The following are keyboard inputs that developers should consider code updates for when building for Windows 11 devices: •Enter Key •Arrow-key and Tab-key Navigation •Change Selected Item Highlight Color •Ctrl-based Shortcuts Learn more about how to optimize for these keyboard input scenarios on desktop devices by following the Android documentation: •Input compatibility guide in the Android docs •Handle keyboard input guide in the Android docs •Use touch gestures guide in the Android docs
Mouse input
Developers should consider updating code for the following mouse inputs when building for Windows devices: •Right Click •Tooltips / Hover Text •Hover Effects •Mouse Scroll Wheel Action •Drag and Drop Mouse input, similar to keyboard input, must follow the official Android app guidelines. This means using the InputDevice class paired with the SOURCE_MOUSE constant. Learn more about how to optimize for these mouse input scenarios on desktop devices by following the Android documentation: •Input compatibility guide in the Android docs •InputDevice reference in the Android docs •SOURCE_MOUSE reference in the Android docs
Minimum screen requirement
Windows 11 enforces a minimum screen requirement of 720p resolution (1280x720) with a >9” screen.
Letter & pillar boxing
When the aspect ratio of a window size does not align between the device screen sizes that window is being displayed on, the result may be Letterboxing (the window is wider than it is high, or horizontally longer) or Pillarboxing (the window is more narrow than it is wide, or vertically longer). The result is bars being placed on the sides of the window in order to center it. These bars may be light- or dark-themed depending on the system settings selected. This will only occur as necessary when the Android app is snapped or maximized, allowing Android apps to take advantage of the rich snapping features in Windows and integrate into the windowing model.
Additional resizing considerations
The following should also be considered when updating an Android app to run on a Windows 11 device with respect to window management and resizing: •Initial launch size •Window dimensions •Content bounds •Free form resizing •Screen Orientation
Developing Android applications for a multi-window environment has an impact on the lifecycle events that you choose to utilize in your application. While overriding the onPause event may achieve the results you’d like on a phone or tablet, it’s typically the wrong event to use if you’re changing your app’s UX.
See the Android documentation for a description of the lifecycle events. More often than not, you’ll want to use the onStop event and not the onPause or onUserLeaveHint events. In fact, many multi-window Android implementations do not deliver the onUserLeaveHint notification, and thus any business critical logic that might be in that event handler will not be called on these platforms, including Windows Subsystem for Android™️.
Windows Subsystem for Android™️ utilizes a virtual machine (VM) which provides compatibility with the AOSP framework and devices like keyboards, mice, touch, pen, etc.
There are three possible states for the VM running apps with Windows Subsystem for Android™️:
1.Running
2.Lightweight Doze: Activated after no app activity for 3 minutes. Deactivated by user activity or an app notification.
3.Not Running: Activated after no app activity for 7 minutes.
Transitions between these states are triggered by user activity, such as launching or interaction with the Android app or an app notification. Android apps are paused and then stopped when their window is minimized.
Easy-to-use APK installer (and more!) for Windows Subsystem for Android. WSATools is a simple APK installer for Windows 11's Subsystem for Android, designed to be intuitive and to make the user instantly feel at home. It also features other helpful tools, like the ability to make and restore backups!
In the WSA settings, go to the System tab. Locate the Files control and click the launch button to open the WSA file browser window. It is crucial to keep the WSA file browser window (shown below) open while using the app for installing and running APK files.
People also ask
Why should I use the WSA manager & APK installer app?
How do I install a WSA app?
What is Windows Subsystem for Android (WSA)?
How do I install and run APK files on a Windows OS?
How to install & run WSA?
How do I open WSA files on Android?
Dec 24, 2023 · Since you can't readily install the official WSA pack on Windows 10, you must unpack the installer first, insert the patched components, alter some routines, and then sideload the modified setup....
