Google Play Games is in open beta.

Configure graphics for Google Play Games

In addition to the requirements in the PC compatibility guide, Google Play Games requires that you update the graphics capabilities of your game and add support for large screens. This topic describes the requirements and related recommendations.

Texture compression

Since Google Play Games passes through compressed textures whenever possible, you should use DXTC or BPTC to take advantage of PC hardware. Sometimes these textures still need to be decompressed if OpenGL features need to be emulated for compatibility reasons, so it's always advisable to profile your games.

Formats such as ETC1 and ETC2 are decompressed by the OpenGL translation layer before being sent to the native graphics stack. These will continue to work, but won't have the same memory or runtime efficiency benefits as you'd expect on mobile hardware.

OpenGL ES version

Google Play Games supports OpenGL ES 3.0. In order to maintain compatibility with Google Play Games, make sure you don't specify a version higher than OpenGL ES 3.0 in your AndroidManifest.xml file.

Vulkan version

Google Play Games supports Vulkan 1.1. In order to maintain compatibility with Google Play Games, ensure your game does not require a version higher than Vulkan 1.1.

Increase maximum frame rate limits

Some players will be able to run your game at a much higher frame rate on PC than on mobile. To give your players the best experience, we recommend either ensuring that the cap is at least 60 fps or removing your frame rate limits altogether.

Large screen optimization

The following large-screen optimizations are require by Google Play Games:

High resolution assets and textures

On PC, you can expect a performance level that matches a high-end Android device released in the last 12 months. This means that you can rely on your higher resolution game assets. When possible, make these available on first launch. Remember that players are more likely to notice lower resolution textures and models on a large PC screen than a phone.

If you're using Opaque Binary Blob OBB files (also known as APK expansion files) to deliver assets, additional high resolution assets might cause the total size to go over the OBB limit of 2 GB main plus 2GB patch). In this case, consider using Play Asset Delivery to deliver your assets.

Play Asset Delivery is supported on Unity 5.6 and above through the Play Unity Plugin, and on Unreal Engine 4.25. For other engines, we provide Java and Native SDKs.

With Play Asset Delivery, you can automatically deliver the textures that match a device's best supported texture compression format without increasing the game size. You can also target devices based on their performance level, and automatically deliver higher or lower resolution textures accordingly.

UI scaling

On a larger screen, your game's UI may need adjustments to ensure all elements are appropriately sized. We recommend that HUDs take up no more than 20% of the screen.

Aspect ratios

Google Play Games requires support for the 16:9 aspect ratio. For an ideal player experience, we recommend that games also support 16:10 and 3:2.

Dynamic display

Google Play Games requires the following changes for dynamic display sizing:

  • Specify supported orientations in your Android manifest with android:screenOrientation, unless both orientations are supported.
  • Specify supported min and max aspect ratios with android:minAspectRatio and android:maxAspectRatio, unless the game supports all of the 16:9, 16:10, and 3:2 ratios.

We recommend that you Support DPI changes in onConfigurationChanged() and declare "density" as a supported change using android:configChanges in your Android manifest.