乳山市访琴科技有限公司

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.

• Amazon Appstore on Windows 11 discontinuation notice.
• Windows Subsystem for Android™️ repository on GitHub
• Apps from the Amazon Appstore
• Accessibility for mobile apps on Windows

To test your Android app in the Windows desktop environment, a bit of set up will be required.

Device requirements.

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.

The Amazon Appstore app will then appear in the Windows 11 Start menu and be available on search, offering a catalogue of Android apps. The Windows Subsystem for Android™️ app, which lets you control mobile app settings and features, will also appear in the Start menu.

inktype="relative-path">

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.

inktype="relative-path">

To test and debug your app on a Windows 11 device using the Windows Subsystem for Android™️ the following set up steps are required.

You must first enable developer mode. Open the Windows Subsystem for Android™️ settings. once open, enable Developer mode under Advanced settings.

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):

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:

The can be found in the output of "ipconfig" from the test device. You can also deploy and debug apps from Android Studio.

To use Android Debug Bridge (ADB) to connect your development workstation directly to your Android device so you can install packages and evaluate changes, see Android Debug Bridge in the Android Open Source Project docs.

While apps should be installed using the Amazon Appstore, debugging an Android app on a Windows device is possible using an APK (Android application package) and adb (Android Debug Bridge).

To debug an APK using adb:

1. Follow the steps to connect to the Windows Subsystem for Android™️ VM above.

2. Install the APK using the adb install command:

   Expected Output:

3. A successful "app installed" notification will appear in the Windows notification menu and the app will launch once selected.

Windows Subsystem for Android™️ utilizes Intel Bridge Technology to enable Arm applications on x86 based processors. Arm applications will run on Arm-based processors natively. The emulation layer will induce a performance overhead – for optimal performance, submit your application for both the x86-64 and Arm64 architectures.

There are a few unique input behaviors to consider that will likely require updates to your Android app code, designed for handheld devices, to be compatible when running on a Windows desktop device via the Amazon Appstore.

For text input fields handled by an on-screen virtual keyboard input method (or IME), such as , 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 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

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 class paired with the 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

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.

Windows 11 enforces a minimum screen requirement of 720p resolution (1280x720) with a >9" screen.

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.

inktype="relative-path">

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

Learn more about how to optimize for window resizing scenarios on desktop devices by following the Window Management guide in the Android docs.

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 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 event and not the or events. In fact, many multi-window Android implementations do not deliver the 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.

inktype="relative-path">

The properties for the Windows Subsystem for Android™️ VM are listed below. Hardcoding these values is not recommended as that could cause future incompatibilities.