Changes

! Bluestacks

! Google Play Games

! <small>Windows Subsystem for Android</small>

|-

| {{✗}}

| {{~}}<ref group=N4 name=GooglePlayGamesDeveloper>Exclusive to developer builds, Demonstration: [https://youtu.be/2KEaPQpfzkQ?t=408 Home screen], [https://youtu.be/2KEaPQpfzkQ?t=280 Sideloading].</ref>

| {{✓}}

| {{✗}}

| {{?}}

| {{✓}}[https://tested.blissos.org/hardware/inputs/gamepad/ *]

| {{✓}}[https://learn.microsoft.com/en-us/windows/android/wsa/release-notes#build-22084000040 *]

|-

| {{✓}}

| {{✓}}[https://youtu.be/2KEaPQpfzkQ?t=153 *]

| {{?}}

| {{?}}

| {{✓}}

| {{✓}}[https://youtu.be/2KEaPQpfzkQ?t=153 *]

| {{?}}

| {{?}}

| {{✓}}

| {{N}}[https://old.reddit.com/r/BlueStacks/comments/z54s8p/usb_devices_in_bluestacks/iy2gtgb/ *]

| {{?}}

| {{?}}

| {{✓}}

| {{~}}[https://developer.android.com/games/playgames/faq#q_can_we_use_push_notifications_for_google_play_games *]

| {{✓}}

| {{✓}}[https://learn.microsoft.com/en-us/windows/android/wsa/release-notes#build-220440000190 *]

| {{✓}}<ref group=N4>If you're using latest version of BlueStacks you'll need to install a file manager to copy game cache when loading your own .apk files, or simply use .xapk containers.</ref>

| {{~}}<ref group=N4 name=GooglePlayGamesDeveloper></ref>

| {{✓}}

| {{~}}[https://github.com/Simizfo/WSATools#requisites *]

|-

| colspan=2 | [https://developer.android.com/develop/connectivity/wifi/wifi-scan Wi-Fi]

| {{✓}}

| {{✓}}

| {{?}}

| {{✓}}[https://tested.blissos.org/hardware/connectivity/bluetooth/ *]

| {{N}}[https://xdaforums.com/t/looking-wsa-for-windows-11-where-bluetooth-also-works.4610551/post-88829045 *]

|-

| {{?}}

| {{Y}}[https://support.bluestacks.com/hc/en-us/articles/360058638032-Advanced-settings-for-key-controls-in-BlueStacks-5-#%E2%80%9C9%E2%80%9D *]

| {{?}}

| {{?}}

| {{Y}}

| {{?}}

| {{?}}

|-

|-

| colspan=2 | [[Wikipedia:Android_version_history#Android_4.4_KitKat|KitKat]] (API 19)<br/><small>Supporting [[Wikipedia:Android_version_history#Android_4.4_KitKat|Android 4.4 (KitKat)]] is crucial for emulators due to compatibility and [[Preservation_projects|preservation]] reasons.<br/> Older applications and games often rely on the "[[Wikipedia:Dalvik_(software)|Dalvik]]", which isn't present in newer versions and there could be '''[https://web.archive.org/web/20141215220606/http://www.androidruntime.com:80/list compatibility issues]'''.<br/>Android 5.0 (Lollipop)(API 21) introduced the "[[Wikipedia:Android_Runtime|Android RunTime]]" (ART), [[Wikipedia:Android_Runtime#History|replacing "Dalvik" entirely]].<br/>Having said that ART is mostly backwards compatible with Dalvik. See these sources for more information: [https://xdaforums.com/t/explained-art-runtime-in-android-4-4-kitkat.2622098/ 1], [https://www.geeksforgeeks.org/difference-between-dalvik-and-art-in-android/ 2], [https://developer.android.com/guide/practices/verifying-apps-art 3].</small>

| {{N}}<ref group=N4>You need to use [[Wikipedia:BlueStacks#BlueStacks_3|BlueStacks 3 version]] (not 3N), because it is the latest version supports KitKat.</ref>

| {{N}}

| {{N}}

|-

| {{Y}}<ref group=N4 name=BluestacksOSsupport>[https://support.bluestacks.com/hc/en-us/articles/360058931031-How-to-utilize-the-different-Android-versions-available-on-BlueStacks-5#%E2%80%9C1%E2%80%9D Which Android versions are available on BlueStacks?].</ref>

| {{N}}

| {{N}}

|-

| {{N}}<ref group=N4 name=BluestacksOSsupport></ref>

| {{Y}}

| {{N}}

|-

|-

| colspan=2 | [https://web.archive.org/web/20180507120451/https://developer.android.com/ndk/guides/abis#sa armeabi]

|-

| colspan=2 | [https://developer.android.com/ndk/guides/abis#v7a armeabi-v7a]<br/><small>Supporting armeabi-v7a ABI is crucial for emulators due to compatibility and [[Preservation_projects|preservation]] reasons.<br/> Older applications and games often rely on the [[Wikipedia:ARM_architecture_family|ARM 32-bit (Cortex)]] architecture, which isn't used in newer hardware.</small>

|?

|{{Y}}<ref group=N4 name=BlueStacksABI>[https://support.bluestacks.com/hc/en-us/articles/360058929011-What-is-Application-Binary-Interface-ABI-in-BlueStacks-5 What is Application Binary Interface (ABI) in BlueStacks 5 ]</ref>

|?

|?

|{{Y}}<ref group=N4 name=BlueStacksABI></ref>

|{{Y}}<ref group=N4 name=GooglePlayGamesABI>[https://developer.android.com/games/playgames/start#playbility-architecture Google Play Games ABI Architecture support].</ref>

|?

|?

|{{Y}}<ref group=N4 name=BlueStacksABI></ref>

|{{Y}}<ref group=N4 name=GooglePlayGamesABI></ref>

|?

|?

|{{Y}}<ref group=N4 name=BlueStacksABI></ref>

|{{Y}}<ref group=N4 name=GooglePlayGamesABI></ref>

|?

|?

|-

|-

| colspan=2 | [https://registry.khronos.org/OpenGL/index_es.php#specs10 OpenGL ES 1.0]<br/><small>Supporting OpenGL ES 1.x is crucial for emulators due to compatibility and [[Preservation_projects|preservation]] reasons.</small>

|?

|?

|-

| colspan=2 | [https://registry.khronos.org/OpenGL/index_es.php#specs31 OpenGL ES 3.1]<br/><small>The OpenGL ES 3.x API is backwards-compatible with the 2.x API which is crucial for emulators due to compatibility and [[Preservation_projects|preservation]] reasons..</small>

|?

|?

|-

| colspan=2 | [https://registry.khronos.org/vulkan/#vulkan1.1 Vulkan 1.1]<br/><small>It's possible to use Vulkan 1.1 thanks to [https://developer.android.com/ndk/guides/graphics/android-baseline-profile Android Baseline 2022 profile].</small>

|?

|?