Here’s How Google Is Making It Easier For Developers To Port PC Games To Android

Mishaal Rahman / Android Authority

Mobile gaming has come a long way since the early days of Android, but even the best Android games don’t stack up to what’s available on consoles and PCs. This is why retro console emulation is so popular among Android gamers, as emulation unlocks access to game catalogs that are far superior to what’s natively available on Android. Google wants to make Android and its Google Play platform to be gamers’ one-stop shop for everything gaming-related, though, so it’s announcing new features, tools, and programs in an effort to simplify porting PC games to Android.

Ahead of the annual Game Developers Conference (GDC) next week, Google announced changes coming to the Android platform and Google Play as well as partnerships with device vendors and game engine makers to reduce the friction of porting PC games to Android. These changes include first-class support for the Vulkan graphics API on Android, enhanced stability for the Android Dynamic Performance Framework, new tools in the Google Play Console to fix game crashes, and the launch of a pilot program to aid developers in their journey of bringing their games to Android.

The main benefit of this change, according to Google, is that it enables developers to add more immersive visuals in their games. Vulkan allows developers to capitalize on the performance of modern smartphone GPUs to unlock features like ray tracing in games or multithreading. Games like Diablo Immortal and Pokémon TCG Pocket leverage the Vulkan graphics API to implement splashy special effects and optimize graphics across a broad range of devices.

Although Google says that it is now transitioning Android to a “modern, unified rendering stack with Vulkan at its core,” Android has actually supported the Vulkan graphics API since Android 7.0 Nougat’s release in 2016. The reason the company didn’t pursue this change earlier is simply due to fragmentation. Even a few years after Vulkan’s introduction to Android, only a small percentage of active devices supported it, and among those devices, only a handful offered robust support. Today, though, more than 85% of active Android phones support Vulkan, and over 45% of sessions from new Android games built on the Unity game engine use Vulkan. Support for Vulkan among Android devices is in a much better place now than it was several years ago, which is why Google feels comfortable making it the official graphics API for Android.

What does it actually mean for Android to make Vulkan its official graphics API, though? Essentially, Google aims to establish Vulkan as the GPU hardware abstraction layer (HAL) for Android, requiring all apps and games utilizing the phone’s GPU to do so through Vulkan. This includes: game engines, middleware, and layered APIs like Android’s HWUI, Skia, WebGPU, and ANGLE.

ANGLE is particularly important. It allows apps and games running on OpenGL ES (GLES) to support both legacy devices without modern Vulkan drivers and new devices without native GLES drivers. ANGLE, short for Almost Native Graphics Layer Engine, is a layered implementation of GLES on top of Vulkan. It translates GLES calls to Vulkan and essentially acts as the GLES driver on some modern Android devices running Android 15.

Starting with the upcoming Android release, i.e. Android 16, though, Google says that “more devices will use Vulkan to process all graphics commands.” Specifically, Android 16 will require some newer devices to use ANGLE for some applications (meaning, only applications on an approved list will use ANGLE). Next year’s Android 17 release, however, will require new devices to use ANGLE for most applications (essentially, switching from an allowlist, meaning only certain apps utilize ANGLE, to a denylist, meaning all apps utilize ANGLE except for those on a specific list.) By “new devices,” Google is referring to devices that ship with chipsets built for the new Android release, as devices upgrading to the new release won’t be forced to meet these new ANGLE requirements in accordance with the Google Requirements Freeze program.

Although most Android devices on the market today support the Vulkan graphics API, there’s little uniformity when it comes to what Vulkan features are actually available. This is because there are many Android devices with old, outdated Vulkan drivers as well as many devices running older versions of Android. Vulkan feature availability can also differ between chipset vendors, further complicating game development.

To improve the consistency of Vulkan support among Android devices, Google introduced Vulkan Profiles for Android (VPA) last year. VPA is a collection of Vulkan functionality that chipsets must support in order to pass Google’s certification requirements for a specific Android release. The VPA for Android 16, for example, requires that chipsets support these Vulkan features at minimum, which build upon the requirements from the VPA for Android 15 as well as the 2022 Android Baseline Profile.

Google also worked with the Khronos Group—the industry group behind the Vulkan graphics API—to develop the latest Vulkan 1.4 release, ensuring that Android devices will broadly support its featureset. The Vulkan 1.4 specification was developed to largely be a subset of the VPA for Android 16, meaning that new devices that meet the VPA16 requirements will support most features in Vulkan 1.4. New SoCs launching with support for Android 17, though, will be required to fully support Vulkan 1.4.

By mandating support for newer versions of Vulkan, Google is essentially culling older GPUs from the market, as devices with those older GPUs won’t be allowed to update to newer Android versions. This is important because it means that robust Vulkan API support will only get better and better among Android devices as time goes on, eliminating a huge reason why mobile game developers don’t take advantage of the latest graphical features available on Android devices.

Google also teamed up with the Samsung Austin Research Center to create a new open source profiler and debugger for Vulkan and AI/ML optimization. This new tool is an integrated GPU profiler toolchain that enables developers to make graphics, memory, and compute workloads more efficient. The tool will be launching later this year.

Next, Google says it has collaborated with MediaTek to optimize the Android Dynamic Performance Framework (ADPF) for MediaTek chips. ADPF is a feature that lets developers adjust the performance demands of their games in real-time based on the thermal state of the device. With MediaTek’s help, Google has made the ADPF more stable, allowing it to “provide longer and smoother gameplay sessions.” Furthermore, several game engines now offer built-in ADPF support, making it easier for game developers to integrate. The feature works on many existing devices without MediaTek chips, such as the Pixel 9 and Galaxy S25, so today’s announcement simply means ADPF is now available in more places and on more devices.

Once developers have launched their games on Android, they can use the new Low Memory Killers feature in the Google Play Console to monitor and improve their games’ performance. This feature offers insight into memory constraints that contribute to game crashes.

Got a tip? Talk to us! Email our staff at [email protected]. You can stay anonymous or get credit for the info, it’s your choice.