Игры Google Play | Обновленные правила повышения уровня

Обновленная программа Level Up от Google Play Games призвана отмечать и вознаграждать разработчиков, создающих отличные игровые проекты, предоставляя им льготы по тарифным планам, способствующие росту бизнеса. Участие в программе добровольное, и разработчики, решившие не участвовать, не потеряют в правах на льготы, предоставляемые в рамках других программ. Зарегистрироваться можно через Play Console начиная с 1 сентября 2026 года. Для получения дополнительной информации см. раздел «Регистрация в программе Level Up» .

Наша миссия — предоставить игрокам лучшие игровые возможности, обеспечивающие стабильный игровой процесс , доступность на всех экранах и более плавную работу игрового процесса .

Ожидания игроков и потребности разработчиков постоянно меняются, и программа разработана таким образом, чтобы развиваться вместе с ними. Рекомендации по пользовательскому опыту и преимущества могут обновляться со временем. Чтобы помочь вам поддерживать статус вашей программы, мы предоставим разумное уведомление и подробную документацию до вступления в силу любых обновлений программы, гарантируя вам достаточно времени для внедрения необходимых изменений.

На этой странице описаны рекомендации по улучшению пользовательского опыта. Чтобы узнать больше о программе Level Up и ее преимуществах, посетите страницу программы Level Up на сайте Google Play Games .

Рекомендации по пользовательскому опыту

Для получения доступа к преимуществам программы Level Up, ваша игра должна соответствовать всем рекомендациям по удобству использования, изложенным на этой странице. Эти рекомендации могут периодически обновляться по мере развития программы.

В следующих разделах изложены руководящие принципы, объединенные тремя основными темами:

• Обеспечьте стабильный игровой процесс для игроков.
  • Помощник в играх Play Games
  • Достижения
  • Статистика игры
  • Награды
  • Сохранение в облаке
• Расширьте охват аудитории на всех экранах.
  • Оптимизация для больших экранов
  • Игры Google Play на ПК
  • Точное управление вводом
  • Распределение форм-факторов
  • Доступность названия
• Обеспечьте стабильный и плавный игровой процесс.
  • Стабильность
  • Производительность
  • Память
  • Вулкан
• Список справочных устройств

Обеспечьте стабильный игровой процесс для игроков.

Наша игровая платформа представляет новые механики и интерфейсы, обеспечивающие игрокам улучшенный, приятный и стабильный игровой процесс. Для этого игры должны соответствовать следующим рекомендациям по пользовательскому опыту.

ИДЕНТИФИКАТОР	Руководство
LU-PA-GAA	Аутентификация платформы : Интегрируйте SDK Google Play Games Services v2 и убедитесь, что он инициализируется при запуске. Эта интеграция обеспечивает работу достижений, игровой статистики и синхронизации между устройствами для игроков, которые включили эти функции платформы. Для получения дополнительной информации см. Play Games Services .

Для аутентификации на платформе Play Games не требуется использовать систему идентификации Google или даже иметь собственную внутриигровую систему идентификации. Если вы хотите использовать систему идентификации, вы можете использовать любого поставщика идентификации (например, Sign in with Google, сторонних поставщиков или собственную серверную часть) для управления собственными внутриигровыми учетными записями. Игры с внутриигровыми учетными записями могут использовать API Play Games Recall для синхронизации учетных записей между устройствами, что упрощает вход в систему.

Исключения

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-PA-EAA	Для соответствия требованиям Level Up играм, ориентированным в первую очередь на игроков младше 13 лет, не требуется инициализировать сервисы Play Games Services или развертывать другие функции из этого раздела (достижения, GSAPI, Sidekick, награды или облачное сохранение).

Помощник в играх Play Games

Play Games Sidekick — это всплывающее окно, которое помогает игрокам оставаться в игре, предоставляя им актуальный контент, функциональность и предложения напрямую. Игроки ожидают, что Sidekick будет доступен в играх на платформе Play Games.

ИДЕНТИФИКАТОР	Руководство
LU-SK-GAA	Добавьте Sidekick в свою игру. Это можно сделать, включив эту функцию в консоли разработчика Play, если ваша игра опубликована в формате App Bundle. В качестве альтернативы, вы можете скомпилировать SDK Sidekick непосредственно в свою игру, если используете устаревший формат APK для публикации или несовместимое решение DRM.

Исключения

Хотя Sidekick полезен для всех игроков, он доступен не для всех категорий пользователей. В соответствии с этим правилом существуют следующие исключения:

ИДЕНТИФИКАТОР	Исключения
LU-SK-EAA	Игры, предназначенные в первую очередь для игроков младше 13 лет. Поскольку функция Sidekick отключена на детских аккаунтах, игры, разработанные специально для детей младше 13 лет, не подпадают под это ограничение.
LU-SK-EAB	Если в игре возникла проблема, препятствующая работе Sidekick, и об этом было сообщено Google, и сообщение было принято к рассмотрению, то игре может быть предоставлено исключение на соответствующий период времени для поиска обходного пути или решения проблемы.

Дополнительные ресурсы

Для получения более подробной информации см. Sidekick .

Достижения

Достижения являются неотъемлемой частью игрового процесса, призванной признавать и вознаграждать игроков за их успехи в играх.

ИДЕНТИФИКАТОР	Руководство
LU-AC-GAA	Нам необходимо как минимум 10 достижений, распределенных на протяжении всего жизненного цикла игры. Обратите внимание, что мы рекомендуем иметь 40 и более достижений для обеспечения активного и глубокого взаимодействия с игроками на платформе Google Play Games.
LU-AC-GAB	Все достижения должны иметь уникальное название и описание . Они должны четко показывать игрокам, что им нужно сделать, чтобы получить достижение.
LU-AC-GAC	Для участия в квестах необходимо , чтобы как минимум 4 достижения были выполнимы разумным и надежным образом в течение первого часа игры всеми участниками.

Исключения

Хотя достижения доступны всем игрокам, они могут быть неактуальны для каждой аудитории. В соответствии с этим правилом, существует следующее исключение:

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-AC-EAA	Игры, ориентированные в первую очередь на игроков младше 13 лет.
LU-AC-EAB	Игры освобождаются от возможности получения достижений, если в них недостаточно четких событий, прогресса или достижений игрока. Следует отметить, что механизмы прогресса, такие как личные рекорды за все время, уровни, разблокировка или открытие локаций, победы над врагами или соперниками, сюжетные этапы, опыт, процент завершения или сбор предметов, могут использоваться для создания достижений.

Дополнительные ресурсы

Информацию о том, как интегрировать достижения в игру, и о лучших практиках см. в разделе «Достижения» .

Статистика игры

Раскройте потенциал вовлеченности игроков и повысьте видимость своей игры на платформе Google Play Games с помощью функции «Статистика игры». Функция «Статистика игры» позволяет пользователям просматривать свои показатели в профиле игрока и используется для запуска дополнительных функций вовлечения игроков в Play, таких как квесты, социальные задания и многое другое в будущем.

ИДЕНТИФИКАТОР	Руководство
LU-GS-GAA	Для отображения игровой статистики в профиле игрока необходимо предоставить не менее 5 повторяющихся статистических данных. Все повторяющиеся данные должны отражать регулярно повторяющиеся действия игроков в игре. По крайней мере, один из показателей должен быть пригоден для использования в функциях, связанных с вовлечением игроков в соревновательный процесс.
LU-GS-GAB	Если у вас есть основной механизм развития персонажа, добавьте как минимум один дополнительный показатель развития персонажа , чтобы функция игровой статистики хранилась в профиле игрока. Уровень прогресса должен представлять собой показатель, отражающий успех игрока в игре.

Данные об игроках для игровой статистики должны передаваться с помощью API игровой статистики, используя либо клиентскую, либо серверную реализацию. Прогресс каждого игрока или повторяющаяся статистика должны быть настроены в инструментах, предоставляемых Play. Необходимо объявить схему исходных данных и сопоставить ее с пользовательской версией игровой статистики, включая строку отображения, уникальный значок и любые правила агрегации.

ИДЕНТИФИКАТОР	Руководство
LU-GS-GAC	Каждый показатель должен соответствовать требованиям, описанным в разделе «Игровая статистика» .

В большинстве игр должны быть доступны соответствующие сигналы. Есть примеры, которые помогут вам выбрать правильные данные, необходимые для активации механики взаимодействия.

Исключения

К данному руководству применяются следующие исключения:

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-GS-EAA	В играх, ориентированных в первую очередь на игроков младше 13 лет, игровая статистика недоступна для игроков младше 13 лет.
LU-GS-EAB	Игры освобождаются от обязанности предоставлять информацию о состоянии игрока только в том случае, если в них отсутствуют четкие механизмы прогресса. Если ваша игра включает такие функции, как рекорды за все время, уровни, опыт, процент завершения или сбор основных предметов, она не подпадает под это исключение, поскольку эти элементы могут использоваться в качестве механизма прогресса.
LU-GS-EAC	Игры, доступные в рамках программы раннего доступа для ПК (EAP) , пока не поддерживаются нашим SDK. (Примечание: это относится только к версии вашей игры для ПК).

Дополнительные ресурсы

Для получения более подробной информации см. раздел «Статистика игры» .

Награды

Создавайте предложения Play Games Reward , которые Play Games может бесплатно распространять среди игроков в качестве поощрений и наград, включая предметы, уже имеющиеся в игре, или новые предметы для повышения вовлеченности:

ИДЕНТИФИКАТОР	Руководство
LU-RE-GAA	Все предметы должны быть доступны каждому игроку хотя бы один раз при использовании функции «Играть».
LU-RE-GAB	Все предметы должны быть значимыми или привлекательными для игроков, чтобы эффективно стимулировать вовлеченность.
LU-RE-GAC	30 сентября 2026 г.: Как минимум 2 одноразовых награды в рамках игрового процесса , такие как определенные персонажи, скины или оружие. Эти награды будут начислены игрокам после успешного выполнения задания.
LU-RE-GAD	1 марта 2027 г .: Как минимум одно повторяющееся предложение «Награда за участие в играх» , например, жизни, временные бонусы, ежедневные награды, внутриигровая валюта или другие расходные материалы. Эти награды будут начисляться игрокам после успешного выполнения социальных заданий, максимум 1 награда в неделю на игрока.

Исключения

К данному руководству применяются следующие исключения:

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-RE-EAA	Игры, ориентированные в первую очередь на игроков младше 13 лет. Наградные предметы используются для таких функций, как квесты и социальные испытания, которые, как правило, недоступны игрокам младше 13 лет. Если ваша игра ориентирована в первую очередь на эту возрастную группу, вы освобождаетесь от обязанности предоставлять наградные предметы.
LU-RE-EAB	Платные игры. Игроки ожидают получить полный игровой опыт в платных играх после первоначальной покупки. Это относится к любой игре с разовой покупкой, будь то предоплата при установке или единовременная внутриигровая покупка. Мы не будем предоставлять дополнительные внутриигровые предметы в платных играх.

Дополнительные ресурсы

Для получения более подробной информации см. раздел «Награды Play Games» .

Сохранение в облаке

Игроки используют несколько устройств и устанавливают игры на одно и то же устройство несколько раз. В результате им всегда приходится начинать игру с последнего достигнутого прогресса. Для этого необходимо внедрить в игру облачное сохранение.

ИДЕНТИФИКАТОР	Руководство
LU-CS-GAA	Игра должна сохранять состояние игры игрока вне устройства, в облаке, и восстанавливать его при запуске игры.
LU-CS-GAB	Политика разрешения конфликтов необходима , если у игрока несколько внутриигровых учетных записей или если возникает конфликт между сохраненными игровыми данными на его устройстве и в облаке. Обычно игрок сам решает, как разрешить эти конфликты. Ваша политика разрешения конфликтов должна учитывать следующие сценарии: Несколько учетных записей на пользователя: Обработка случаев, когда один игрок взаимодействует с приложением, используя разные учетные записи. Конфликты состояний: Устранение несоответствий, возникающих между локальным состоянием игры и состоянием игры, сохраненным в облаке.

Если у вас нет существующего решения для сохранения прогресса игрока в облаке, мы рекомендуем использовать API сохранений игр в рамках сервисов Play Games для обеспечения этой функциональности. Вы можете использовать любое решение, соответствующее этим рекомендациям.

Мы считаем, что в каждой игре должна быть возможность для игроков возобновить прохождение после каждой новой установки игры.

Исключения

К данному руководству применяются следующие исключения:

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-CS-EAA	Сохранение в облаке не требуется для игр, которые не предоставляют внутриигровые учетные записи и предлагают только гостевые учетные записи или не сохраняют состояние игры между игровыми сессиями.
LU-CS-EAB	Игры, в которых размер файлов сохранения превышает лимит API сохранений (3 МБ), и внедрение автоматизированного облачного решения сторонними разработчиками было бы слишком дорогостоящим, освобождаются от требований к облачным сохранениям. Однако мы рекомендуем разработчикам предложить альтернативное решение, например, позволить игрокам вручную загружать и выгружать свои файлы.

Дополнительные ресурсы

Для получения более подробной информации см. раздел «Сохранение в облаке» .

Расширьте охват аудитории на всех экранах.

Игроки хотят играть в свои любимые игры без проблем на всех своих устройствах, и мы расширяем охват Android на новые экраны и пространства. Чтобы помочь разработчикам извлечь выгоду из растущей аудитории, им необходимо публиковать оптимизированные версии своих игр для разных форм-факторов.

Для участия в программе Level Up все игры должны соответствовать этим рекомендациям, чтобы обеспечить совместимость с различными форм-факторами устройств:

Оптимизация для больших экранов

Игроки ожидают возможности играть в свои игры на любых устройствах, поддерживаемых платформой Google Play Games. Это включает в себя устройства Android с большими экранами, такие как планшеты или складные телефоны. Ваша игра должна обеспечивать возможность изменения размера экрана, чтобы игроки получали наилучшие впечатления на этих форм-факторах.

ИДЕНТИФИКАТОР	Руководство
LU-LS-GAA	Используйте отступы, чтобы предотвратить блокировку элементов управления игрой или пользовательского интерфейса, которые перекрываются с системными панелями (состояние, навигация, жесты) или вырезами на дисплее (выемками, отверстиями).
LU-LS-GAB	Поддержка изменения конфигурации (поворот устройства, сворачивание/разворачивание, разделение на несколько окон, изменение размера окна в произвольном порядке) без сбоев, ошибок ANR, визуальных артефактов или смещения сенсорных кнопок, при сохранении активного состояния игры и прогресса.
LU-LS-GAC	Игры, отображаемые в альбомной ориентации, должны отображаться в полноэкранном режиме без черных полос сверху и снизу на эталонных устройствах и при соотношении сторон 4:3, 16:10 и 21:9. Игры, предназначенные только для альбомной ориентации, не обязаны поддерживать портретную ориентацию, но должны иметь чистые черные полосы сверху и снизу на экранах с вертикальной ориентацией. Изображения с соотношением сторон, отличным от вертикальной, также могут иметь черные полосы сверху и снизу.
LU-LS-GAD	Игры, отображаемые в портретном режиме, должны отображаться на весь экран без черных полос сверху и снизу на эталонных устройствах и при соотношении сторон 3:4, 10:16 и 9:21. Игры, предназначенные только для портретной ориентации, не обязаны поддерживать альбомную ориентацию, но должны иметь чистые черные полосы сверху и снизу на экранах с горизонтальной ориентацией. Изображения с соотношением сторон, отличным от вертикального, также могут иметь черные полосы сверху и снизу.

Дополнительные ресурсы

• Для получения информации об исключениях, специфичных для конкретного форм-фактора, обратитесь к руководству по распределению форм-факторов .

• Для получения дополнительной информации об обработке изменения размера экрана большого размера см. раздел «Поддержка изменения размера экрана большого размера» .

Игры Google Play на ПК

Google Play Games на ПК предоставляет игрокам лучшие возможности Google Play, обеспечивая захватывающий и бесшовный кроссплатформенный игровой процесс.

ИДЕНТИФИКАТОР

Руководство

LU-PC-GAA

Ваша игра должна распространяться в Google Play Games на ПК . Существует два способа выполнить это требование к распространению: Ваша мобильная игра соответствует требованиям к играбельности при запуске на эмуляторе Android Google Play Games для ПК . Убедитесь, что все неподдерживаемые функции и разрешения Android не помечены как необходимые для обеспечения корректного распространения. ИЛИ Ваша игра опубликована как нативная игра для ПК в Google Play Games и интегрирована с PC SDK * .

Исключения

Распространение некоторых игр на ПК сопряжено с трудностями. К данному правилу применяются следующие исключения:

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-PC-EAA	Ограничения по форм-фактору существенно ухудшат качество игрового процесса . Например, игры, критически важные с технической точки зрения, недоступные в форм-факторе Google Play Games на ПК, или игры, для которых форм-фактор Google Play Games на ПК приведет к существенному ухудшению игрового процесса: Дополненная реальность и игры, основанные на определении местоположения, в значительной степени зависят от физического географического перемещения устройства. Игры, использующие локальные аппаратные датчики мобильных устройств (например, датчики дыхания или отслеживание сна), не поддаются моделированию и имеют решающее значение для основного игрового процесса без обходных путей. Игры с механикой, требующей от пользователя физического вращения всего тела на 360 градусов в реальном пространстве для поиска цифровых объектов.
LU-PC-EAB	Ограничение на лицензирование интеллектуальной собственности на уровне отдельных платформ. Некоторые разработчики лицензируют интеллектуальную собственность своих мобильных игр у стороннего лицензиара. Такие соглашения могут ограничивать лицензию разработчика, запрещая публикацию игры на ПК без предварительного приобретения дополнительных лицензионных прав. Игры, в отношении которых лицензионное соглашение исключает публикацию таких игр на ПК, могут подпадать под это исключение.
LU-PC-EAC	( Только платные игры ) Разница в цене между мобильными и ПК-версиями. Платные игры, распространяемые через Play Store до 30 сентября 2026 года, для которых существовала разница в цене между ПК и мобильными устройствами.

Дополнительные ресурсы

Для получения дополнительной информации о распространении игр на ПК через Google Play см. раздел «Игры Google Play на ПК» .

Точное управление вводом

Поддержка различных форм-факторов означает поддержку естественного ввода устройства и, в целом, предоставление пользователю возможности играть так, как ему удобнее. Это значит, что игры должны поддерживать ввод с контроллера, клавиатуры и мыши для наилучшего игрового процесса на разных экранах.

ИДЕНТИФИКАТОР	Руководство
LU-IC-GAA	Игра должна быть полностью совместима с контроллером, клавиатурой и мышью (K&M) на всех устройствах, поддерживаемых платформой Play Games, где эти режимы ввода доступны. Полная совместимость означает, что в игру можно играть с самого начала, включая все игровые механики и меню настроек, без необходимости переключаться на сенсорный ввод.

Исключения

Не все игровые механики легко адаптируются к точному управлению. Следующие исключения обусловлены основными игровыми механиками и тем, как, по нашему мнению, различные режимы ввода принципиально влияют на игровой опыт.

ИДЕНТИФИКАТОР	Критерии	Контроллеры Необходимый	К&М Необходимый
LU-IC-EAA	GPS / Пространственное картирование на основе местоположения : дополненная реальность и игры, основанные на местоположении, в значительной степени зависят от физического географического перемещения устройства.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAB	Датчики окружающей среды (микрофон/отслеживание сна) : Игры, использующие локальные аппаратные датчики мобильных устройств (например, датчики дыхания или отслеживание сна), не могут быть смоделированы и имеют решающее значение для основного игрового процесса без обходных путей.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAC	Кинетическая камера / Панорамы дополненной реальности : механика, требующая от пользователя физического вращения всего тела на 360 градусов в реальном пространстве для обнаружения цифровых объектов.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAD	Гироскопическое/акселерометрическое пространственное прицеливание: игры, в которых для игрового процесса необходимо наличие гироскопа или акселерометра на устройстве, и которые в противном случае потребовали бы значительной переработки пользовательского интерфейса для поддержки точного ввода.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAE	Интенсивные быстрые движения пальцем и ритмичные движения с использованием нескольких касаний: ритм-игры (музыкальный жанр) требуют одновременного, синхронного управления несколькими элементами экрана, что математически невозможно выполнить с помощью одного курсора мыши. Контроллеры не обладают достаточной физической конфигурацией для интуитивного отображения динамических ритмических диаграмм с 6-8 дорожками.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAF	Рисование жестами / Векторные фигуры от руки : Точное воспроизведение определенных геометрических фигур или контуров от руки с использованием строгих радиальных ограничений джойстика контроллера практически невозможно.	❌ (необязательно)	✅ (необходимый)
LU-IC-EAG	Перетаскивание / Абсолютное наведение и щелчок : Быстрое перетаскивание с помощью относительного радиального джойстика нецелесообразно с кинетической точки зрения и значительно медленнее, чем абсолютное касание.	❌ (необязательно)	✅ (необходимый)

Дополнительные ресурсы

Для получения дополнительной информации о поддержке точного ввода в вашей игре см. раздел «Включение естественного ввода для всех форм-факторов» . При поддержке контроллеров обязательно добавьте этот флаг в свой манифест , чтобы пользователи могли найти вашу игру при поиске игр с поддержкой контроллеров в магазине.

Распределение форм-факторов

Платформа Google Play Games доступна на множестве различных форм-факторов устройств Android, и игроки ожидают, что смогут играть в свои игры на всех из них.

ИДЕНТИФИКАТОР	Руководство
LU-FF-GAA	Ваша игра должна распространяться на следующих платформах Android с безупречным качеством: 30 сентября 2026 г .: Мобильные телефоны , складные устройства и планшеты 30 сентября 2027 г .: Android XR , Android TV , Googlebook и Android Auto

Исключения

К данному руководству применяются следующие исключения:

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-FF-EAA	Ограничения форм-фактора существенно ухудшат качество игрового процесса . Речь идёт о играх, критически важных с технической точки зрения игровых характеристиках, которые недоступны для данного форм-фактора, или где форм-фактор существенно ухудшит игровой процесс.

Например:

Игровая механика	Форм-факторы, не подлежащие распространению
Дополненная реальность и игры, основанные на определении местоположения, в значительной степени зависят от физического географического перемещения устройства.	Игры Google Play на ПК, планшетах, GoogleBook, Android TV
Игры, использующие локальные аппаратные датчики мобильных устройств (например, датчики дыхания или отслеживание сна), не поддаются моделированию и имеют решающее значение для основного игрового процесса без обходных путей.	Игры Google Play на ПК, планшетах, GoogleBook, Android TV, Android Auto
Игры с механикой, требующей от пользователя физического вращения всего тела на 360 градусов в реальном пространстве для поиска цифровых объектов.	Игры Google Play на ПК, GoogleBook, Android TV, Android Auto

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-FF-EAB	Устройства с техническими характеристиками ниже минимальных требований к мобильному оборудованию. Игры не подлежат распространению на устройствах с аппаратными характеристиками (ОЗУ, процессор, память или графический процессор) или версиями Android, которые не соответствуют минимальным требованиям вашего мобильного телефона.
LU-FF-EAC	Доступность по форм-фактору. Игры не распространяются на устройствах, недоступных в регионах, где предлагается данная игра, — это означает, что региональная доступность устройства и игры не пересекается.

Доступность названия

Игроки могут выбирать предпочитаемые устройства, сохраняя при этом беспрепятственный доступ ко всей своей игровой библиотеке.

ИДЕНТИФИКАТОР	Руководство
LU-TA-GAA	Для того чтобы игры могли претендовать на льготы по программе льготных цен, они должны быть выпущены для форм-факторов, поддерживаемых Android, одновременно с появлением на любых других сопоставимых форм-факторах, не поддерживающих Android, начиная с 30 сентября 2026 года и далее.

В настоящее время для Android поддерживаются следующие форм-факторы:

• Мобильные устройства и устройства с большими экранами (планшеты, GoogleBooks, ПК)
• Android XR (с отображением игр в 2D-окне на устройстве XR)
• Android TV
• Android Auto

Названия игр, не соответствующие данным критериям доступности, получат право на льготы по программе Level Up после 6-месячного периода ожидания , когда будут полностью соблюдены все требования к удобству использования.

Примеры :

• Если игра подает заявку на участие в программе Level Up и в настоящее время доступна на других сопоставимых форм-факторах, отличных от Android, то она должна быть выпущена на всех сопоставимых форм-факторах Android не менее чем за 6 месяцев до регистрации в программе Level Up. В противном случае она не будет иметь права на преимущества программы до истечения 6 месяцев после запуска игры на форм-факторе Android. Шестимесячный период ожидания не применяется, если игра была выпущена на форм-факторе, отличном от Android, до 30 сентября 2026 года.
• Если игра, уже участвующая в программе, выходит на аналогичном форм-факторе, отличном от Android, и одновременно не выходит на аналогичном форм-факторе Android, она лишается права на участие в программе на 6 месяцев.

Исключения

К данному руководству применяются следующие исключения:

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-TA-EAA	Различия между платформами устройств. Не каждая игра технически или концептуально подходит для каждой аппаратной конфигурации; поэтому игра будет исключением, если разработчик сможет продемонстрировать, что ограничения конкретного форм-фактора Android существенно ухудшат пользовательский опыт по сравнению с аналогичной платформой, отличной от Android, или если для данного оборудования нет жизнеспособного технического решения.
LU-TA-EAB	Отсрочка запуска. Для учета непредвиденных технических проблем, задержек с проверкой в ​​магазинах или «мягких запусков» мы будем применять следующие меры: Стандартный льготный период. Разработчикам предоставляется 15 дней для получения статуса «запущенного» проекта в Google Play Store. Продленный льготный период. В исключительных случаях, когда разработчик может доказать, что задержка была вызвана технической проблемой на стороне Google или необычно длительным процессом проверки приложения, льготный период может быть продлен до 30 дней после ручной проверки.
LU-TA-EAC	ЕЭЗ. Данное руководство не распространяется на ЕЭЗ. Однако при распространении в ЕЭЗ пользователи Android должны иметь доступ ко всем новым функциям и возможностям, предоставляемым разработчиком в рамках Android-игры. Поэтому разработчики обязаны полностью оптимизировать свои игры для Android.

Обеспечьте стабильный и плавный игровой процесс.

Чтобы обеспечить безупречную работу игр на всех форм-факторах, мы вводим стандарты качества, гарантирующие как производительность, так и стабильность для игроков. Все игры должны соответствовать этим рекомендациям по пользовательскому опыту, чтобы обеспечить высокое качество игры и возможность присоединиться к программе Level Up.

Стабильность

Игроки ожидают, что игры будут стабильно работать на их устройствах, без сбоев и ошибок типа «Android не отвечает» (ANR). Игры должны соответствовать следующим критериям качества. Для снижения нестабильности эти критерии будут применяться на основе данных за последние 28 дней, учитывая только устройства из утвержденного набора, для которых ваше приложение имело не менее 1500 сессий за последние 28 дней.

	LU-ST-GAA	LU-ST-GAB
Основные параметры Android	Тестовые устройства	Устройства Android с 4 ГБ и более оперативной памяти
Аварии	<1% средний показатель аварийности Проверьте показатели в информации Play Console.	<2% средний показатель аварийности (Проверка показателей в Play Console ) информация
АНР	<2% средний показатель ANR Проверьте показатели в информации Play Console.	<3% средний показатель ANR (Проверка показателей в Play Console ) информация

Исключения

Исключений из данного правила нет.

Дополнительные ресурсы

Для получения дополнительной информации о диагностике и устранении критически важных проблем см. раздел «Критические параметры Android» .

Производительность

Плавная и стабильная частота кадров имеет решающее значение для обеспечения высококачественного игрового процесса на устройствах Android.

ИДЕНТИФИКАТОР

Руководство

LU-PR-GAA

На эталонных устройствах активные игровые сцены по умолчанию должны отображаться с частотой не менее 60 кадров в секунду. Это требование относится исключительно к активному игровому процессу в реальном времени и исключает неинтерактивные или переходные состояния, такие как экраны загрузки/заставки, загрузка контента, интерфейсы лобби, меню и кинематографические кат-сцены. Средняя частота кадров ≥ 55 FPS Низкие 10% (P90) FPS ≥ 50 FPS Низкий 1% (P99) FPS ≥ 30 FPS

Исключения

В мобильных играх приходится принимать множество сложных решений о том, что означает высокое качество для конкретного игрового процесса — например, что важнее: графическая составляющая или время автономной работы во время игры. К данному правилу применяются следующие исключения:

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-PR-EAA	Игры, не поддерживающие 60 кадров в секунду на других мобильных платформах, отличных от Android.
LU-PR-EAB	Игры, использующие HWUI или Composer вместо прямого рендеринга.
LU-PR-EAC	Игры, в которых новые кадры добавляются только при взаимодействии с игроком , а не на постоянной регулярной основе.
LU-PR-EAD	Для игр на планшетах и ​​складных устройствах соответствие этим требованиям не является обязательным из-за сложностей в проектировании системы охлаждения и вычислительных мощностях, необходимых для поддержки экранов высокого разрешения.

Дополнительные ресурсы

Для получения дополнительной информации о расчете и измерении производительности Level Up см. частоту кадров . Вы также можете ознакомиться с документацией по медленным сессиям , где описаны стратегии оптимизации плавности кадров.

Память

Для обеспечения превосходного пользовательского опыта в Android 17 были оптимизированы обработка памяти и ужесточены требования к платформе, что сопровождается новой, полезной телеметрией памяти в Play Console.

Начиная с февраля 2027 года , Play требует от игр соответствия установленным пороговым значениям некорректного поведения для динамического использования памяти (анонимный RSS + файл подкачки), использования растровых изображений и оптимизации кода во всех версиях Android. Теперь разработчики могут отслеживать эти показатели памяти и пороговые значения некорректного поведения в Android Vitals .

ИДЕНТИФИКАТОР	Руководство
LU-MM-GAA	После введения в действие требований к объему памяти игры должны соответствовать всем этим требованиям, чтобы получить право на повышение уровня или сохранить его. С требованиями к объему памяти и сроками их применения можно ознакомиться здесь . Оптимизируйте свою игру : следуйте последним рекомендациям для игр, чтобы максимально сэкономить память на разных этапах процесса.

Исключения

Исключений из данного правила нет.

Вулкан

Vulkan — это современный графический API для Android, который значительно улучшает производительность и снижает энергопотребление. Он также предлагает новые, более качественные графические технологии, которые улучшат игровой процесс на Android.

В старых играх может быть предпочтительнее использовать Vulkan через ANGLE , а не конвертировать собственный код под Vulkan. ANGLE — это соответствующий стандарту OpenGL ES слой трансляции от Google для Windows, Mac, Linux, iOS и Android. ANGLE использует Vulkan в своей основе.

ИДЕНТИФИКАТОР

Руководство

LU-VK-GAA

На устройствах с обновленными графическими драйверами, где DEQP ≥ 20240301 : Если вы используете Unity версии 2023 или новее , или Unreal Engine версии 4.25 или новее : В качестве основного графического API необходимо установить Vulkan . Незначительное использование OpenGL ES (например, для рекламы, веб-представлений и т. д.) допустимо, если оно составляет менее 10% кадров. Игры, использующие встроенный конвейер рендеринга Unity, могут перейти на использование ANGLE для устройств Android 17+. У этих игр есть время до 30 сентября 2027 года , чтобы установить Vulkan в качестве основного графического API. Для достижения этой цели настоятельно рекомендуется перейти на универсальный конвейер рендеринга Unity, но это не единственный допустимый путь. Если вы используете более старую версию Unity, Unreal или любого другого игрового движка, вам необходимо либо использовать Vulkan, либо включить рендеринг ANGLE, чтобы соответствовать этим рекомендациям. Чтобы включить использование ANGLE, измените файл манифеста вашего приложения следующим образом: <application android:appCategory="game"> <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" /> </application>

Исключения

Наша позиция по умолчанию заключается в том, что все игры должны использовать Vulkan, поскольку он обеспечивает значительные преимущества в производительности и экономии заряда батареи. Следующее исключение учитывает, что у некоторых игр может не быть выбора графического API.

ИДЕНТИФИКАТОР	Освобождение от налогов
LU-VK-EAA	Игры, которые не контролируют собственную отрисовку и используют HWUI/SKIA (аналогично тому, как это делают приложения), не имеют контроля над графическим конвейером и будут автоматически переведены на Vulkan в следующих версиях Android.
LU-VK-EAB	Если ваша игра использует WebGPU в качестве API рендеринга, WebGPU — это новый язык высокого уровня, который использует Vulkan на более новых устройствах и OpenGL ES на более старых. Если по какой-либо причине WebGPU решит не использовать Vulkan на конкретном устройстве, это находится вне контроля разработчика. Мы работаем над развертыванием бэкенда Vulkan на как можно большем количестве устройств в кратчайшие сроки.
LU-VK-EAC	Если в игре возникла критическая проблема с Vulkan, и об этом было сообщено, и соответствующее сопровождение кода (например, игровой движок, поставщик GPU-IP или Google) приняло это к рассмотрению, то игре может быть предоставлено исключение на соответствующий период времени для поиска обходного пути или устранения проблемы.
LU-VK-EAD	Разработчик может быть освобожден от этого требования, если он сможет сократить количество инструкций, выполняемых процессором, аналогичным тому, что обеспечивает Vulkan. Vulkan обеспечивает приблизительно 30% сокращение количества инструкций процессора по сравнению с другими решениями. Если разработчик сможет продемонстрировать аналогичное улучшение с помощью альтернативного решения, то использование Vulkan не требуется.

Дополнительные ресурсы

Для получения дополнительной информации об обновлении графических API вашей игры см. Vulkan .

Список справочных устройств

The following devices are used to test our guidelines. Because Android hardware and features evolve, this list can be updated to ensure comprehensive coverage.

Список устройств

Год	System on a Chip продавец	System on a Chip модель	Производитель	Маркетинговое название	Форм-фактор
2026	GOOGLE	TENSOR G5	GOOGLE	PIXEL 10 PRO XL	ТЕЛЕФОН
				PIXEL 10 PRO FOLD	FOLDABLE
	MEDIATEK	MT6993	VIVO	X300	ТЕЛЕФОН
				X300 PRO	ТЕЛЕФОН
			OPPO	FIND X9 PRO	ТЕЛЕФОН
				FIND X9	ТЕЛЕФОН
	QTI	SM8845	ONEPLUS	ONEPLUS 15R	ТЕЛЕФОН
			ЛЕНОВО	MOTOROLA SIGNATURE	ТЕЛЕФОН
		SM8850	SAMSUNG	GALAXY S26 ULTRA	ТЕЛЕФОН
				GALAXY S26	ТЕЛЕФОН
				GALAXY S26+	ТЕЛЕФОН
			ONEPLUS	ONEPLUS 15	ТЕЛЕФОН
			OPPO	FIND N6	FOLDABLE
			СЯОМИ	СЯОМИ 17	ТЕЛЕФОН
				XIAOMI 17 ULTRA	ТЕЛЕФОН
				LEITZPHONE POWERED BY XIAOMI	ТЕЛЕФОН
				XIAOMI 17 PRO MAX	ТЕЛЕФОН
	SAMSUNG	S5E9965	SAMSUNG	GALAXY S26	ТЕЛЕФОН
				GALAXY S26+	ТЕЛЕФОН
2025	GOOGLE	TENSOR G4	GOOGLE	PIXEL 9 PRO XL	ТЕЛЕФОН
				PIXEL 9 PRO FOLD	FOLDABLE
	MEDIATEK	MT6991	СЯОМИ	XIAOMI 15T PRO	ТЕЛЕФОН
			SAMSUNG	GALAXY TAB S11	ПЛАНШЕТ
				GALAXY TAB S11 ULTRA	ПЛАНШЕТ
				GALAXY TAB S11 ULTRA 5G	ПЛАНШЕТ
				GALAXY TAB S11 5G	ПЛАНШЕТ
			VIVO	VIVO X200	ТЕЛЕФОН
				X200 PRO	ТЕЛЕФОН
				X200T	ТЕЛЕФОН
			OPPO	FIND X8	ТЕЛЕФОН
				FIND X8 PRO	ТЕЛЕФОН
	QTI	SM8735	СЯОМИ	XIAOMI PAD 8	ПЛАНШЕТ
		SM8750	SAMSUNG	GALAXY S25 ULTRA	ТЕЛЕФОН
				ГАЛАКСИЯ S25	ТЕЛЕФОН
				GALAXY S25+	ТЕЛЕФОН
				GALAXY S25 EDGE	ТЕЛЕФОН
				GALAXY Z FOLD7	FOLDABLE
			ONEPLUS	ONEPLUS 13	ТЕЛЕФОН
				ONEPLUS 13S	ТЕЛЕФОН
				PAD 3	ПЛАНШЕТ
			OPPO	FIND N5	FOLDABLE
			СЯОМИ	XIAOMI 15	ТЕЛЕФОН
				XIAOMI 15 ULTRA	ТЕЛЕФОН
			СОНИ	XPERIA 1 VII	ТЕЛЕФОН
			VIVO	IQOO 13	ТЕЛЕФОН

Comprehensive testing across every specific model may not be required because several devices in the list use identical SoCs and exhibit comparable performance. Developers are eligible to self-certify for the guidelines once they have successfully verified requirements on at least one device from each listed SoCs:

Телефоны

Год	System on a Chip	Устройства
2026	Тензор G5	PIXEL 10 PRO XL
2025	Tensor G4	PIXEL 9 PRO XL
2026	MTK MT6993	X300, FIND X9
2025	MTK MT6991	XIAOMI 15T PRO, GALAXY TAB S11, VIVO X200, FIND X8
2026	QCOM SM8845/8850	ONEPLUS 15R, MOTOROLA SIGNATURE, GALAXY S26, ONEPLUS 15, XIAOMI 17
2025	QCOM SM8750	GALAXY S25, ONEPLUS 13, PAD 3, XIAOMI 15. XPERIA 1 VII, IQOO 13
2026	Exynos S5E9965	GALAXY S26

Планшет

Год	System on a Chip	Устройства
2025	MTK MT6991	GALAXY TAB S11
2025	QCOM SM8735	XIAOMI PAD 8
2025	QCOM SM8750	OPPO PAD 3

Контроллеры

For controllers, make sure to test your game with the following as it covers the common styles of controllers supported on the platform today:

• Беспроводной контроллер Sony DualSense
• XBox Wireless Controller
• Nintendo Switch Pro Controller (note: This is for the original Switch console)

We recommend using the testing guidance here for more details.

Примечания к изменениям

Сентябрь 2026 г.

• Производительность

  • Guidelines updated: LU-PF-GAA

  • Previous text:

    Games that do not support 60 FPS on other platforms.

  • New text:

    Games that do not support 60 FPS on other non-Android mobile platforms.

• Large screen optimization

  • Guidelines updated: LU-LS-GAA , LU-LS-GAB LU-LS-GAC , LU-LS-GAD

  • Previous text:

    • Handle system bars , display cutouts , and configuration changes —such as device rotation and window resizing—to prevent crashes and visual artifacts. Ensure all UI and gameplay elements remain visible and interactive, avoiding any obstructions that block player input, while correctly maintaining or restoring the game state.

    • Games in a landscape layout need to be full screen, without letterboxing or pillarboxing, at the aspect ratios for each reference device and also at the anchor aspect ratios of 4:3, 16:10, and 21:9.

    • Games in a portrait layout similarly need to support the complement aspect ratios. For example, for the anchor ratios the equivalent is 3:4, 10:16, and 9:21.

    • Games are able to letterbox or pillar box themselves under the following conditions:

      • On a device with an aspect ratio that is not found on a flagship device or outside one of the anchor aspect ratios defined previously.
      • If the only game layout orientation (portrait or landscape) is different from the device's physical orientation.

  • New text:

    • Use insets to prevent blocking game controls or UIs that overlap with system bars (status, navigation, gesture) or display cutouts (notches, punch holes).

    • Support configuration changes (device rotation, fold/unfold, multi-window split, freeform window resizing) without crashes, ANRs, visual artifacts, or touch mapping offsets, while preserving active game state and progress.

    • Games displayed in landscape must render full screen without letterboxing or pillarboxing on Reference Devices and anchor ratios of 4:3, 16:10, and 21:9. Landscape-only games are not required to support a portrait layout, but must cleanly letterbox or pillarbox themselves on portrait displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.

    • Games displayed in portrait must render full screen without letterboxing or pillarboxing on reference devices and anchor ratios of 3:4, 10:16, and 9:21.Portrait-only games are not required to support a landscape layout, but must cleanly letterbox or pillarbox themselves on landscape displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.

• Google Play Games on PC

  • Guidelines updated: LU-GPGC-GAA

  • Previous text:

    Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC .

    • Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution.
    • OR, Your game is part of the Native PC Early Access Program (EAP) .

  • New text:

    Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC .

    • Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution.
    • OR, Your game is published as a Native PC game on Google Play Games and integrates with the PC SDK ^* .

    ^* If you publish as a Native PC Game, your title won't need to support Sidekick, Cloud Save, Achievements, and Game Stats API for the PC version until those features become available in the Google Play Games on PC SDK.

• Precision input controls

  • New text:

• Form factor distribution

  • Guideline updated: LU-FF-GAA

  • Previous text:

    • September 2026 : Mobile , Foldables, and Tablets
    • March 1, 2027 : Googlebook
    • September 2027 : Android XR , Android TV , and Android Auto

  • New text:

    • September 2026 : Mobile , Foldables, and Tablets
    • September 2027 : Android XR , Android TV , Googlebook , and Android Auto

• Vulkan

  • Guideline updated: LU-VK-GAA
  • Previous text:
  • Vulkan must be set as the primary graphics API if you are using Unity version 2021 or newer , or Unreal Engine version 4.25 or newer . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as it is <10% of frames.
  • Instead of using Vulkan directly, games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path.

  • All other games can decide to either use Vulkan as the primary graphics API or opt-in to using ANGLE for Android 17+ devices. To opt in to use ANGLE modify the app's manifest file as follows:

    <application android:appCategory="game">
    <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" />
    </application>
    

  • New text:

  • If you are using Unity version 2023 or newer , or Unreal Engine version 4.25 or newer :

  • Vulkan must be set as the primary graphics API . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as its <10% of frames.

  • Games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path.

  • If you are using an older version of Unity or Unreal, or any other game engine, then you are required to either use Vulkan or enable ANGLE rendering to meet this guideline. To opt-in to use ANGLE, modify your app's manifest file as follow:

    <application android:appCategory="game">
    <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" />
    </application>
    

• Память

  • Guidelines updated: LU-MM-GAA

  • Previous text:

    To deliver a premium experience, Android 17 is introducing optimized memory handling and stricter platform requirements later this year–accompanied by new, actionable memory telemetry in the Play Console. Because meeting these standard memory limits will be required for Level Up, we strongly encourage [implementing these memory optimization strategies][bbb] early to ensure app stability and a great user experience. More detailed compliance criteria to maintain your program status will be shared in the coming months.

  • New text:

    To deliver a premium experience, Android 17 introduced optimized memory handling and stricter platform requirements, which is accompanied by new, actionable memory telemetry in the Play Console.

    Effective February 2027 , Play requires games to meet established bad-behavior thresholds for dynamic memory usage (anonymous RSS + swap), bitmap usage, and code optimization across all Android versions. Developers can now monitor these memory metrics and bad behavior thresholds within Android vitals .

    Once enforcement for these memory thresholds are in effect, games must comply with all memory thresholds to qualify for or maintain Level Up eligibility. You can find the memory thresholds and enforcement timeline here .

    Optimize your game : Follow the latest guidance for games to maximize memory savings across process states.

Июль 2026 г.

• Статистика игры
  • Guidelines updated: LU-GS-GAA
  • Exemption updated: LU-GS-EAC
  • Previous text:
    • Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All stats need to represent regularly occurring actions by players in the game.
    • At least 1 stat needs to be usable for competitive player engagement features.
    • Stats should not require a purchase (For example, buy gems).
    • Stats should not require watching advertisements.
    • Stats should not be generic use of the game (For example, open the game; use settings).
    • Stats should be available to all users (For example, not a team-specific action).
  • New text:
    • Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All repetitive stats need to represent regularly occurring actions by players in the game.
      • At least 1 stat needs to be usable for competitive player engagement features.
    • Exemption: Titles on Native PC Early Access Program (EAP), given our SDK doesn't support this feature yet. (Note: This only applies to the Native PC version of your title).

,

Google Play Games revamped Level Up is a program to recognize and reward great gaming experiences with program rate card benefits to drive business growth for your game. Participation in this program is voluntary and developers that choose not to participate will not have a change in benefits they are entitled through other programs. Developers can enroll through Play Console starting September 1, 2026. For more information, see Enroll in the Level Up program .

Our mission is to connect players with the best gaming experiences—ones that provide a consistent gamer experience , reach across all screens and deliver stable and smoother gameplay sessions .

Player expectations and developer needs are always evolving, and the program is designed to evolve with them. User experience guidelines and benefits may be updated over time. To help you maintain your program status, we will provide reasonable notice and detailed documentation before any program updates take effect, ensuring you have sufficient time to implement required changes.

This page describes the user experience guidelines. To know more about the Level Up program and benefits, visit the Google Play Games | Level Up program page .

User experience guidelines

To gain access to the Level Up program rate card benefits, your game needs to adhere to all the user experience guidelines outlined on this page. These guidelines may be updated from time to time as the program evolves.

The following sections outline the guidelines with three main themes:

• Provide a consistent gamer experience
  • Play Games Sidekick
  • Достижения
  • Статистика игры
  • Награды
  • Cloud save
• Expand your reach across all screens
  • Large screen optimization
  • Google Play Games on PC
  • Precision input controls
  • Form factor distribution
  • Доступность названия
• Deliver stable and smoother gameplay sessions
  • Стабильность
  • Производительность
  • Память
  • Vulkan
• Reference device list

Provide a consistent gamer experience

Our gaming platform introduces new mechanics and surfaces delivering an elevated, delightful, and consistent gaming experience for players. To deliver this, games should integrate the following user experience guidelines.

ИДЕНТИФИКАТОР	Руководство
LU-PA-GAA	Platform authentication : Integrate the Google Play Games Services v2 SDK and ensure it initializes at startup. This integration powers achievements, game stats, and cross-device sync, for players who have opted into these platform features. For more information, see Play Games Services .

Using Play Games Platform authentication does not require using Google's identity system, or that you even have an in-game identity system. If you would like to use an identity system, you are free to use any identity provider (such as Sign in with Google, third party providers, or a custom backend) to manage proprietary in-game accounts. Games with in-game accounts can use the Play Games Recall API to sync accounts between devices to make sign-in easier.

Исключения

ИДЕНТИФИКАТОР	Exemption
LU-PA-EAA	Games that primarily target players aged under 13 are not required to initialize Play Games Services or deploy other features in this section (Achievements, GSAPI, Sidekick, Rewards, or Cloud Save) to meet Level Up guidelines.

Play Games Sidekick

Play Games Sidekick is an overlay that helps players stay in their game by delivering relevant content, functionality, and offers directly to them. Players expect Sidekick to be available on games on the Play Games platform.

ИДЕНТИФИКАТОР	Руководство
LU-SK-GAA	Add Sidekick to your game. This can be done through enabling the feature in the Play Developer Console if your game is published in the App Bundle format. Alternatively, you can compile the Sidekick SDK directly into your game if you are using the legacy APK format for publishing, or you are using an incompatible DRM solution.

Исключения

While Sidekick benefits all players, it is not available for every audience. We have the following exemptions for this guideline:

ИДЕНТИФИКАТОР	Исключения
LU-SK-EAA	Games that primarily target players aged under 13. Because Sidekick is disabled on children's accounts, games that are primarily designed for children under 13 are exempt.
LU-SK-EAB	If a game has encountered a blocking issue with Sidekick, and they have reported it and had it accepted by Google, then they may be granted an exemption for an appropriate period of time to find a work around or for the issue to be addressed.

Дополнительные ресурсы

For more information, see Sidekick .

Достижения

Achievements are a core gaming experience to recognize and reward players for their accomplishment in their games.

ИДЕНТИФИКАТОР	Руководство
LU-AC-GAA	We require a minimum of 10 achievements spread across the lifetime of the game. Note that we recommend having 40+ achievements to provide robust, deep engagement with your players on the Google Play Games platform.
LU-AC-GAB	All achievements must have a unique name and description . These should make clear to players what they need to do to get the achievement.
LU-AC-GAC	To be eligible for Quests , a minimum of 4 achievements must be reasonably and reliably achievable within the first hour of gameplay by everyone who plays.

Исключения

While achievements are available for all players, they may not make sense for every audience. We have the following exemption for this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-AC-EAA	Games that primarily target players aged under 13.
LU-AC-EAB	Games are exempt from providing achievements if they lack sufficient clear events, progression, or player accomplishment within them. Note that progression mechanisms like lifetime high scores, levels, area unlocking or discovery, enemy or challenger defeats, story stages, XP, completion percentages, or item collection can be used to create achievements.

Дополнительные ресурсы

For information on how to integrate achievements into your game and best practices, see Achievements .

Статистика игры

Unlock deeper player engagement and boost your game's visibility across the Google Play Games platform with Game Stats. The Game Stats feature enables users to view their stats in their gamer profile and is used to power additional player engagement features across Play, such as Quests, Social Challenges, and more in the future.

ИДЕНТИФИКАТОР	Руководство
LU-GS-GAA	Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All repetitive stats need to represent regularly occurring actions by players in the game. At least 1 stat needs to be usable for competitive player engagement features.
LU-GS-GAB	If you have a primary progression mechanic, submit at least 1 additional player progression stat to power the Game Stats feature stored against the player's gamer profile. Progression level needs to be a metric that represents the player's progress in the game.

Player data for Game Stats should be submitted using Game Stats API through either client or server implementation. Each player progression or repetitive stat needs to be configured in Play provided tools. Raw data schema needs to be declared and mapped to a user facing Game Stats, including display string, unique icon and any aggregation rules.

ИДЕНТИФИКАТОР	Руководство
LU-GS-GAC	Each stat must follow the requirements described in Game Stats .

Most games should be able to provide appropriate signals. Examples are available to help you choose the correct data points that will enable the engagement mechanics.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-GS-EAA	Games that primarily target players aged under 13 Game Stats is not enabled for players under 13 years of age.
LU-GS-EAB	Games are exempt from providing player states only if they lack clear progression mechanisms. If your game includes features such as lifetime high scores, levels, XP, completion percentages, or primary item collection, it does not qualify for this exemption as these can be used as a progression mechanism.
LU-GS-EAC	Titles on Native PC Early Access Program (EAP) , given our SDK does not support this feature yet. (Note: This only applies to the Native PC version of your title).

Дополнительные ресурсы

For more information, see Game Stats .

Награды

Create Play Games Reward offers that Play can distribute to players for free as incentives and rewards including items already in the game or new items to drive increased engagement:

ИДЕНТИФИКАТОР	Руководство
LU-RE-GAA	All items need to be available to every player at least once using Play.
LU-RE-GAB	All items must be meaningful or desirable for players to ensure they effectively drive engagement.
LU-RE-GAC	September 30, 2026: At least 2 single-use Play Games Reward offers , such as specific characters, skins, or weapons. These Play Game rewards will be awarded to players after the successful completion of a Quest.
LU-RE-GAD	March 1, 2027 : At least 1 repeatable Play Games Reward offer , such as lives, temporary power-ups, daily reward items, in-game currency, or other consumables. These rewards will be awarded to players after successful completion of social challenges, with a maximum of 1 reward per week per player.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-RE-EAA	Games that primarily target players aged under 13. Reward items are used for features like quests and Social Challenges, which are generally unavailable to players under 13. If your game primarily targets this age group, you are exempt from providing reward items.
LU-RE-EAB	Paid games. Players expect to get the full game experience for paid games after their initial purchase. This applies to any game with a single purchase, whether upfront at install time or through a one-time in-game purchase. We won't reward additional in-game items for paid games.

Дополнительные ресурсы

For more information, see Play Games Rewards .

Cloud save

Players play on multiple devices and install their games on the same device multiple times. As a result, they always need to start their game from their last progress state. To achieve this, you must implement a cloud save solution in your game.

ИДЕНТИФИКАТОР	Руководство
LU-CS-GAA	A game must save the player's game state off-device in the cloud and retrieve it when they start the game.
LU-CS-GAB	A conflict resolution policy is required when a player has multiple in-game accounts or if there is a conflict between saved game data on their device and in the cloud. Usually, the player decides how to resolve these conflicts. Your conflict resolution policy should address the following scenarios: Multiple accounts per user: Handle instances where a single player interacts with the application using different accounts. State conflicts: Resolve discrepancies that arise between the local game state and the cloud-saved game state.

If you don't have an existing cloud save solution for your player progress, we recommend the Saved Games API as part of Play Games Services to provide this functionality. You are free to use any solution provider to meet this guideline.

We believe that every game should provide the ability for players to resume their progress across installs of the game.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-CS-EAA	Cloud save is not required for games that don't provide in-game accounts and only provide guest accounts or do not provide any saved game state across gaming sessions.
LU-CS-EAB	Games where the save files exceed the size limits of the Saved Games API (3 MB) and implementing an automated third-party cloud solution would be cost-prohibitive are exempt from the cloud save guidelines. However, we recommend developers provide an alternative solution, such as allowing players to manually download and upload their files.

Дополнительные ресурсы

For more information, see Cloud save .

Expand your reach across all screens

Players want to play their favourite titles seamlessly across all their devices, and we are expanding Android's reach to new screens and spaces. To help developers reap the benefits of growing audiences, developers need to publish optimized versions of their games across form factors.

All games must follow these guidelines to deliver cross device form factor game experience to join the Level Up program:

Large screen optimization

Players expect to play their games on any device form factor that the Google Play Games Platform supports. This includes large screen Android devices like tablets or foldable phones. Your game needs to provide resizability functionality to ensure players get the best experience on these form factors.

ИДЕНТИФИКАТОР	Руководство
LU-LS-GAA	Use insets to prevent blocking game controls or UIs that overlap with system bars (status, navigation, gesture) or display cutouts (notches, punch holes).
LU-LS-GAB	Support configuration changes (device rotation, fold/unfold, multi-window split, freeform window resizing) without crashes, ANRs, visual artifacts, or touch mapping offsets, while preserving active game state and progress.
LU-LS-GAC	Games displayed in landscape must render full screen without letterboxing or pillarboxing on Reference Devices and anchor ratios of 4:3, 16:10, and 21:9. Landscape-only games are not required to support a portrait layout, but must cleanly letterbox or pillarbox themselves on portrait displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.
LU-LS-GAD	Games displayed in portrait must render full screen without letterboxing or pillarboxing on reference devices and anchor ratios of 3:4, 10:16, and 9:21. Portrait-only games are not required to support a landscape layout, but must cleanly letterbox/pillarbox themselves on landscape displays. Out-of-anchor ratios may also be letterboxed/pillarboxed.

Дополнительные ресурсы

• Refer to the Form factor distribution guideline for any form factor specific exemptions.

• For more information on handling large screen resizability, see Support large screen resizability .

Google Play Games on PC

Google Play Games on PC brings the best of Google Play by enabling players to experience an immersive and seamless cross-platform gameplay.

ИДЕНТИФИКАТОР

Руководство

LU-PC-GAA

Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC . Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution. OR, Your game is published as a Native PC game on Google Play Games and integrates with the PC SDK * .

Исключения

There are some games where distribution on PCs is challenging. The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-PC-EAA	Form factor constraints would meaningfully degrade a quality experience . Titles that have critical gameplay technical requirements that are not available on the Google Play Games on PC form factor or where the Google Play Games on PC form factor will create a meaningfully degraded player experience, for example: Augmented reality and location-based games rely fundamentally on the physical geographic displacement of the device. Games utilizing local mobile hardware sensors (like breath input or sleep tracking) cannot be simulated and are critical to the core gameplay loop without workarounds. Games with mechanics requiring the user to physically rotate their entire body in 360-degree real-world space to locate digital assets.
LU-PC-EAB	Platform-specific title-level IP-licensing limitation. Some developers have licensed their mobile game's title-level IP from a third party licensor. These agreements may restrict the developer's license, prohibiting the publishing of the title on PCs without first acquiring additional licensed rights. Such licensed-IP games for which the license grant excludes publishing such games to PCs may be eligible for the exemption.
LU-PC-EAC	( Paid Games Only ) Mobile to PC price differential. Paid games distributed through the Play store prior to September 30, 2026 with a pre-existing PC-to-mobile price differential.

Дополнительные ресурсы

For more information on distributing to PC with Google Play, see Google Play Games on PC .

Precision input controls

Supporting multiple form factors means supporting the device's natural input, and in general allowing the user to play the way they feel best. This means that games must support controller and keyboard and mouse input for the best cross-screen gaming experiences.

ИДЕНТИФИКАТОР	Руководство
LU-IC-GAA	The game must be fully playable with a controller, keyboard, and mouse (K&M) across all devices the game supports through the Play Games platform where these modes of input are available. Fully playable means the game can be played entirely from the start, including all gameplay mechanics and settings menus, without the need to fall back to touch input.

Исключения

Not all mobile mechanics translate seamlessly to precision input controls. The following exemptions are driven by core gameplay mechanics and how we believe different modes of input fundamentally affect the player experience.

ИДЕНТИФИКАТОР	Критерии	Контроллеры Необходимый	К&М Необходимый
LU-IC-EAA	GPS / Location-Based Spatial Mapping : Augmented reality and location-based games rely fundamentally on the physical geographic displacement of the device.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAB	Ambient Sensors (Microphone/Sleep Tracking) : Titles utilizing local mobile hardware sensors (like breath input or sleep tracking) cannot be simulated and are critical to the core gameplay loop without workarounds.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAC	Kinetic Camera / AR Panoramas : Mechanics requiring the user to physically rotate their entire body in 360-degree real-world space to locate digital assets.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAD	Gyroscopic / Accelerometer Spatial Aiming: Games that rely on a gyro or accelerometer being present on the device to play the game, and would otherwise require a significant reworking of the user experience in order to support precision inputs.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAE	Intense Rapid Swiping and Multi-Touch Rhythm: Rhythm games (Music genre) demand simultaneous, synchronous actuation of multiple screen nodes, which a single mouse cursor cannot execute mathematically. Controllers lack the physical layout to map dynamic 6-to-8 lane rhythm charts intuitively.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAF	Gestural Drawing / Freehand Vectors : Drawing specific geometric shapes or freehand paths is effectively impossible to replicate cleanly using the strict radial constraints of a controller thumbstick.	❌ (необязательно)	✅ (необходимый)
LU-IC-EAG	Drag-and-Drop / Absolute Point-and-Click : Executing rapid drag-and-drop mechanics with a relative radial thumbstick is kinetically unviable and vastly slower than absolute touch.	❌ (необязательно)	✅ (необходимый)

Дополнительные ресурсы

For more information about supporting precision inputs within your game, see Enable natural input on all form factors . When supporting controllers, make sure to add this flag to your manifest so that users can find your game when searching for controller-supported games in the store.

Form factor distribution

The Google Play Games platform is available across many different Android device form factors and players expect to play their games across them all.

ИДЕНТИФИКАТОР	Руководство
LU-FF-GAA	Your game must be distributed across the following Android form factors with exemplary quality: September 30, 2026 : Mobile , Foldables, and Tablets September 30, 2027 : Android XR , Android TV , Googlebook , and Android Auto

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-FF-EAA	Form factor constraints would meaningfully degrade a quality experience . Titles that have critical gameplay technical requirements that are not available on the form factor or where the form factor will create a meaningfully degraded player experience.

Например:

Gameplay mechanic	Form Factors exempt from distribution
Augmented reality and location-based games rely fundamentally on the physical geographic displacement of the device	Google Play Games on PC, Tablets, Googlebook, Android TV
Games utilizing local mobile hardware sensors (like breath input or sleep tracking) cannot be simulated and are critical to the core gameplay loop without workarounds.	Google Play Games on PC, Tablets, Googlebook, Android TV, Android Auto
Games with mechanics requiring the user to physically rotate their entire body in 360-degree real-world space to locate digital assets.	Google Play Games on PC, Googlebook, Android TV, Android Auto

ИДЕНТИФИКАТОР	Exemption
LU-FF-EAB	Devices with technical specifications below the minimum Mobile hardware requirements. Games are exempt from distribution on devices with hardware (RAM, CPU, storage, or GPU) or Android versions that fall below your minimum mobile phone requirements.
LU-FF-EAC	Form factor availability. Games are exempt from distribution on devices that are not available in any of the regions where the game is offered—meaning there is no overlap in regional availability between the device and the game.

Доступность названия

Players enjoy the flexibility of choosing their preferred devices while maintaining seamless access to their entire library of gaming experiences.

ИДЕНТИФИКАТОР	Руководство
LU-TA-GAA	For titles to be eligible for the program rate card benefits those titles must be released on Android supported form factors at the same time they become available on any other comparable, non-Android form factors from September 30th 2026 and moving forward.

Currently required Android supported form factors include:

• Mobile and Large Screen (Tablet, Googlebooks, PC)
• Android XR (with titles running in a 2D window on the XR device)
• Android TV
• Android Auto

Titles that do not meet this title availability guideline will become eligible for the Level Up program rate card benefits following a 6-month waiting period , once all user experience guidelines are fully met.

Examples :

• If a title is applying to be in the Level Up program and such title is currently available on other comparable non-Android form factors, such title must be launched on all comparable Android form factors for at least 6 months prior to enrollment into Level Up otherwise they will not be eligible for the program benefits until 6 months after the launch of their title on the Android form factor. The 6 month waiting period does not apply if the title was launched on the non-Android form factor prior to September 30th, 2026.
• If a title currently enrolled in the program launches a comparable non-Android form factor and does not launch on the comparable Android form factor simultaneously, they will become ineligible for program benefits for 6 months.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-TA-EAA	Differences between device platforms. Not every game is technically or conceptually suited for every hardware configuration; therefore, the title will be exempt if the developer can demonstrate that a specific Android form factor's constraints would meaningfully degrade the user experience against the comparable non-Android platform or if there is no viable technical solution for that hardware.
LU-TA-EAB	Launch grace period. To account for unforeseen technical hurdles, store review delays, or "soft launches," we will implement the following: Standard grace period. Developers are granted a 15-day window to achieve "live" status on the Google Play Store. Extended grace period. In exceptional circumstances where a developer can demonstrate that the delay was caused by a Google-side technical issue or an unusually long app review process, the grace period may be extended to 30 days upon manual review.
LU-TA-EAC	EEA. This guideline does not apply in the EEA. However, when distributing to the EEA, Android users should be able to access all new experiences and capabilities within the Android title provided by the developer. Developers are therefore required to fully optimize their titles for Android.

Deliver stable and smoother gameplay sessions

To ensure games run beautifully across all form factors, we are introducing quality benchmarks that guarantee both performance and stability for players. All games must follow these user experience guidelines to provide a high quality experience to join the Level Up program.

Стабильность

Players expect their games to provide a stable experience on their device that is free of crashes and Android Not Responding (ANRs). Games need to meet the following quality thresholds. To reduce volatility, these thresholds will be enforced based on the trailing 28 days of data considering only devices within the approved set for which your app has at least 1,500 sessions in the last 28 days.

	LU-ST-GAA	LU-ST-GAB
Основные параметры Android	Test devices	4GB+ RAM Android Devices
Аварии	<1% average crash rate Check metrics in Play Console info	<2% average crash rate Check metrics in Play Console ) info
АНР	<2% average ANR rate Check metrics in Play Console info	<3% average ANR rate Check metrics in Play Console ) info

Исключения

There are no exemptions for this guideline.

Дополнительные ресурсы

For more information diagnosing and fixing vital issues, see Android vitals .

Производительность

A smooth and stable framerate is critical to delivering a high quality gaming experience on Android devices.

ИДЕНТИФИКАТОР	Руководство
LU-PR-GAA	On reference devices , active gameplay scenes must target and render at a minimum of 60 fps by default. This requirement specifically applies to real-time, active gameplay and excludes non-interactive or transitionary states such as loading/splash screens, content downloads, lobby interfaces, menus, and cinematic cutscenes: Average FPS ≥ 55 FPS Low 10% (P90) FPS ≥ 50 FPS Low 1% (P99) FPS ≥ 30 FPS

Исключения

Mobile games have to make many difficult decisions about what high quality means for their specific experience – such as whether to favor graphical fidelity or battery life during a play session. The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-PR-EAA	Games that do not support 60 FPS on other non-Android mobile platforms.
LU-PR-EAB	Games that use HWUI or Composer rather than rendering directly.
LU-PR-EAC	Games that only push new frames on player interaction , rather than on a continuously regular basis.
LU-PR-EAD	Games are not required to meet this on Tablet and Foldable devices due to their challenges in thermal design and computations to support high-resolution screens.

Дополнительные ресурсы

For additional details on calculating and measuring Level Up performance, see frame rate . You can also explore the slow sessions documentation for optimization strategies regarding frame smoothness.

Память

To deliver a premium experience, Android 17 introduced optimized memory handling and stricter platform requirements, which is accompanied by new, actionable memory telemetry in the Play Console.

Effective February 2027 , Play requires games to meet established bad-behavior thresholds for dynamic memory usage (anonymous RSS + swap), bitmap usage, and code optimization across all Android versions. Developers can now monitor these memory metrics and bad behavior thresholds within Android vitals .

ИДЕНТИФИКАТОР	Руководство
LU-MM-GAA	Once enforcement for these memory thresholds are in effect, games must comply with all memory thresholds to qualify for or maintain Level Up eligibility. You can find the memory thresholds and enforcement timeline here . Optimize your game : Follow the latest guidance for games to maximize memory savings across process states.

Исключения

There are no exemptions for this guideline.

Vulkan

Vulkan is Android's modern graphics API that offers significant improvements in performance and battery usage. It also offers new higher fidelity graphical techniques that will improve the gameplay experience on Android.

Older games might prefer to access Vulkan through ANGLE rather than converting their own code to Vulkan. ANGLE is Google's conformant OpenGL ES translation layer for Windows, Mac, Linux, iOS and Android. ANGLE uses Vulkan under the hood.

ИДЕНТИФИКАТОР

Руководство

LU-VK-GAA

On devices that have updated graphics drivers, where DEQP ≥ 20240301 : If you are using Unity version 2023 or newer , or Unreal Engine version 4.25 or newer : Vulkan must be set as the primary graphics API . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as it is <10% of frames. Games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path. If you are using an older version of Unity or Unreal, or any other game engine, then you are required to either use Vulkan or enable ANGLE rendering to meet this guideline. To opt-in to use ANGLE, modify your app's manifest file as follow: <application android:appCategory="game"> <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" /> </application>

Исключения

Our default stance is that all games should adopt Vulkan because it offers considerable performance and battery benefits. The following exception recognizes that some games might not have a choice on graphics API.

ИДЕНТИФИКАТОР	Exemption
LU-VK-EAA	Games that don't control their own rendering and render through HWUI/SKIA (similar to how apps render). These games have no control over their graphics pipeline, and will be moved to Vulkan automatically over the coming versions of Android.
LU-VK-EAB	If your game uses WebGPU as its rendering API. WebGPU is a new higher level language that uses Vulkan on newer devices and OpenGL ES on older devices. If for some reason WebGPU decides not to use Vulkan on a focus device, that is beyond the control of the developer. We're working on deploying the Vulkan backend on as many devices as possible as quickly as possible.
LU-VK-EAC	If a game has encountered a blocking issue with Vulkan, and they have reported it and had it accepted by the relevant code-maintainer (For example, a Game Engine, GPU-IP Vendor, or Google), then they may be granted an exemption for an appropriate period of time to find a work around or for the issue to be addressed.
LU-VK-EAD	A developer may be exempt from this requirement if they are able to reduce their CPU instruction count in a similar fashion to what Vulkan provides. Vulkan provides an approximate 30% reduction in CPU instruction count as compared to other solutions. If the developer can show a similar improvement with an alternative solution, then the use of Vulkan is not required.

Дополнительные ресурсы

For more information on upgrading your game's graphics APIs, see Vulkan .

Reference device list

The following devices are used to test our guidelines. Because Android hardware and features evolve, this list can be updated to ensure comprehensive coverage.

Список устройств

Год	System on a Chip продавец	System on a Chip модель	Производитель	Маркетинговое название	Форм-фактор
2026	GOOGLE	TENSOR G5	GOOGLE	PIXEL 10 PRO XL	ТЕЛЕФОН
				PIXEL 10 PRO FOLD	FOLDABLE
	MEDIATEK	MT6993	VIVO	X300	ТЕЛЕФОН
				X300 PRO	ТЕЛЕФОН
			OPPO	FIND X9 PRO	ТЕЛЕФОН
				FIND X9	ТЕЛЕФОН
	QTI	SM8845	ONEPLUS	ONEPLUS 15R	ТЕЛЕФОН
			ЛЕНОВО	MOTOROLA SIGNATURE	ТЕЛЕФОН
		SM8850	SAMSUNG	GALAXY S26 ULTRA	ТЕЛЕФОН
				GALAXY S26	ТЕЛЕФОН
				GALAXY S26+	ТЕЛЕФОН
			ONEPLUS	ONEPLUS 15	ТЕЛЕФОН
			OPPO	FIND N6	FOLDABLE
			СЯОМИ	СЯОМИ 17	ТЕЛЕФОН
				XIAOMI 17 ULTRA	ТЕЛЕФОН
				LEITZPHONE POWERED BY XIAOMI	ТЕЛЕФОН
				XIAOMI 17 PRO MAX	ТЕЛЕФОН
	SAMSUNG	S5E9965	SAMSUNG	GALAXY S26	ТЕЛЕФОН
				GALAXY S26+	ТЕЛЕФОН
2025	GOOGLE	TENSOR G4	GOOGLE	PIXEL 9 PRO XL	ТЕЛЕФОН
				PIXEL 9 PRO FOLD	FOLDABLE
	MEDIATEK	MT6991	СЯОМИ	XIAOMI 15T PRO	ТЕЛЕФОН
			SAMSUNG	GALAXY TAB S11	ПЛАНШЕТ
				GALAXY TAB S11 ULTRA	ПЛАНШЕТ
				GALAXY TAB S11 ULTRA 5G	ПЛАНШЕТ
				GALAXY TAB S11 5G	ПЛАНШЕТ
			VIVO	VIVO X200	ТЕЛЕФОН
				X200 PRO	ТЕЛЕФОН
				X200T	ТЕЛЕФОН
			OPPO	FIND X8	ТЕЛЕФОН
				FIND X8 PRO	ТЕЛЕФОН
	QTI	SM8735	СЯОМИ	XIAOMI PAD 8	ПЛАНШЕТ
		SM8750	SAMSUNG	GALAXY S25 ULTRA	ТЕЛЕФОН
				ГАЛАКСИЯ S25	ТЕЛЕФОН
				GALAXY S25+	ТЕЛЕФОН
				GALAXY S25 EDGE	ТЕЛЕФОН
				GALAXY Z FOLD7	FOLDABLE
			ONEPLUS	ONEPLUS 13	ТЕЛЕФОН
				ONEPLUS 13S	ТЕЛЕФОН
				PAD 3	ПЛАНШЕТ
			OPPO	FIND N5	FOLDABLE
			СЯОМИ	XIAOMI 15	ТЕЛЕФОН
				XIAOMI 15 ULTRA	ТЕЛЕФОН
			СОНИ	XPERIA 1 VII	ТЕЛЕФОН
			VIVO	IQOO 13	ТЕЛЕФОН

Comprehensive testing across every specific model may not be required because several devices in the list use identical SoCs and exhibit comparable performance. Developers are eligible to self-certify for the guidelines once they have successfully verified requirements on at least one device from each listed SoCs:

Телефоны

Год	System on a Chip	Устройства
2026	Тензор G5	PIXEL 10 PRO XL
2025	Tensor G4	PIXEL 9 PRO XL
2026	MTK MT6993	X300, FIND X9
2025	MTK MT6991	XIAOMI 15T PRO, GALAXY TAB S11, VIVO X200, FIND X8
2026	QCOM SM8845/8850	ONEPLUS 15R, MOTOROLA SIGNATURE, GALAXY S26, ONEPLUS 15, XIAOMI 17
2025	QCOM SM8750	GALAXY S25, ONEPLUS 13, PAD 3, XIAOMI 15. XPERIA 1 VII, IQOO 13
2026	Exynos S5E9965	GALAXY S26

Планшет

Год	System on a Chip	Устройства
2025	MTK MT6991	GALAXY TAB S11
2025	QCOM SM8735	XIAOMI PAD 8
2025	QCOM SM8750	OPPO PAD 3

Контроллеры

For controllers, make sure to test your game with the following as it covers the common styles of controllers supported on the platform today:

• Беспроводной контроллер Sony DualSense
• XBox Wireless Controller
• Nintendo Switch Pro Controller (note: This is for the original Switch console)

We recommend using the testing guidance here for more details.

Примечания к изменениям

Сентябрь 2026 г.

• Производительность

  • Guidelines updated: LU-PF-GAA

  • Previous text:

    Games that do not support 60 FPS on other platforms.

  • New text:

    Games that do not support 60 FPS on other non-Android mobile platforms.

• Large screen optimization

  • Guidelines updated: LU-LS-GAA , LU-LS-GAB LU-LS-GAC , LU-LS-GAD

  • Previous text:

    • Handle system bars , display cutouts , and configuration changes —such as device rotation and window resizing—to prevent crashes and visual artifacts. Ensure all UI and gameplay elements remain visible and interactive, avoiding any obstructions that block player input, while correctly maintaining or restoring the game state.

    • Games in a landscape layout need to be full screen, without letterboxing or pillarboxing, at the aspect ratios for each reference device and also at the anchor aspect ratios of 4:3, 16:10, and 21:9.

    • Games in a portrait layout similarly need to support the complement aspect ratios. For example, for the anchor ratios the equivalent is 3:4, 10:16, and 9:21.

    • Games are able to letterbox or pillar box themselves under the following conditions:

      • On a device with an aspect ratio that is not found on a flagship device or outside one of the anchor aspect ratios defined previously.
      • If the only game layout orientation (portrait or landscape) is different from the device's physical orientation.

  • New text:

    • Use insets to prevent blocking game controls or UIs that overlap with system bars (status, navigation, gesture) or display cutouts (notches, punch holes).

    • Support configuration changes (device rotation, fold/unfold, multi-window split, freeform window resizing) without crashes, ANRs, visual artifacts, or touch mapping offsets, while preserving active game state and progress.

    • Games displayed in landscape must render full screen without letterboxing or pillarboxing on Reference Devices and anchor ratios of 4:3, 16:10, and 21:9. Landscape-only games are not required to support a portrait layout, but must cleanly letterbox or pillarbox themselves on portrait displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.

    • Games displayed in portrait must render full screen without letterboxing or pillarboxing on reference devices and anchor ratios of 3:4, 10:16, and 9:21.Portrait-only games are not required to support a landscape layout, but must cleanly letterbox or pillarbox themselves on landscape displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.

• Google Play Games on PC

  • Guidelines updated: LU-GPGC-GAA

  • Previous text:

    Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC .

    • Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution.
    • OR, Your game is part of the Native PC Early Access Program (EAP) .

  • New text:

    Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC .

    • Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution.
    • OR, Your game is published as a Native PC game on Google Play Games and integrates with the PC SDK ^* .

    ^* If you publish as a Native PC Game, your title won't need to support Sidekick, Cloud Save, Achievements, and Game Stats API for the PC version until those features become available in the Google Play Games on PC SDK.

• Precision input controls

  • New text:

• Form factor distribution

  • Guideline updated: LU-FF-GAA

  • Previous text:

    • September 2026 : Mobile , Foldables, and Tablets
    • March 1, 2027 : Googlebook
    • September 2027 : Android XR , Android TV , and Android Auto

  • New text:

    • September 2026 : Mobile , Foldables, and Tablets
    • September 2027 : Android XR , Android TV , Googlebook , and Android Auto

• Vulkan

  • Guideline updated: LU-VK-GAA
  • Previous text:
  • Vulkan must be set as the primary graphics API if you are using Unity version 2021 or newer , or Unreal Engine version 4.25 or newer . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as it is <10% of frames.
  • Instead of using Vulkan directly, games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path.

  • All other games can decide to either use Vulkan as the primary graphics API or opt-in to using ANGLE for Android 17+ devices. To opt in to use ANGLE modify the app's manifest file as follows:

    <application android:appCategory="game">
    <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" />
    </application>
    

  • New text:

  • If you are using Unity version 2023 or newer , or Unreal Engine version 4.25 or newer :

  • Vulkan must be set as the primary graphics API . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as its <10% of frames.

  • Games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path.

  • If you are using an older version of Unity or Unreal, or any other game engine, then you are required to either use Vulkan or enable ANGLE rendering to meet this guideline. To opt-in to use ANGLE, modify your app's manifest file as follow:

    <application android:appCategory="game">
    <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" />
    </application>
    

• Память

  • Guidelines updated: LU-MM-GAA

  • Previous text:

    To deliver a premium experience, Android 17 is introducing optimized memory handling and stricter platform requirements later this year–accompanied by new, actionable memory telemetry in the Play Console. Because meeting these standard memory limits will be required for Level Up, we strongly encourage [implementing these memory optimization strategies][bbb] early to ensure app stability and a great user experience. More detailed compliance criteria to maintain your program status will be shared in the coming months.

  • New text:

    To deliver a premium experience, Android 17 introduced optimized memory handling and stricter platform requirements, which is accompanied by new, actionable memory telemetry in the Play Console.

    Effective February 2027 , Play requires games to meet established bad-behavior thresholds for dynamic memory usage (anonymous RSS + swap), bitmap usage, and code optimization across all Android versions. Developers can now monitor these memory metrics and bad behavior thresholds within Android vitals .

    Once enforcement for these memory thresholds are in effect, games must comply with all memory thresholds to qualify for or maintain Level Up eligibility. You can find the memory thresholds and enforcement timeline here .

    Optimize your game : Follow the latest guidance for games to maximize memory savings across process states.

Июль 2026 г.

• Статистика игры
  • Guidelines updated: LU-GS-GAA
  • Exemption updated: LU-GS-EAC
  • Previous text:
    • Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All stats need to represent regularly occurring actions by players in the game.
    • At least 1 stat needs to be usable for competitive player engagement features.
    • Stats should not require a purchase (For example, buy gems).
    • Stats should not require watching advertisements.
    • Stats should not be generic use of the game (For example, open the game; use settings).
    • Stats should be available to all users (For example, not a team-specific action).
  • New text:
    • Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All repetitive stats need to represent regularly occurring actions by players in the game.
      • At least 1 stat needs to be usable for competitive player engagement features.
    • Exemption: Titles on Native PC Early Access Program (EAP), given our SDK doesn't support this feature yet. (Note: This only applies to the Native PC version of your title).

,

Google Play Games revamped Level Up is a program to recognize and reward great gaming experiences with program rate card benefits to drive business growth for your game. Participation in this program is voluntary and developers that choose not to participate will not have a change in benefits they are entitled through other programs. Developers can enroll through Play Console starting September 1, 2026. For more information, see Enroll in the Level Up program .

Our mission is to connect players with the best gaming experiences—ones that provide a consistent gamer experience , reach across all screens and deliver stable and smoother gameplay sessions .

Player expectations and developer needs are always evolving, and the program is designed to evolve with them. User experience guidelines and benefits may be updated over time. To help you maintain your program status, we will provide reasonable notice and detailed documentation before any program updates take effect, ensuring you have sufficient time to implement required changes.

This page describes the user experience guidelines. To know more about the Level Up program and benefits, visit the Google Play Games | Level Up program page .

User experience guidelines

To gain access to the Level Up program rate card benefits, your game needs to adhere to all the user experience guidelines outlined on this page. These guidelines may be updated from time to time as the program evolves.

The following sections outline the guidelines with three main themes:

• Provide a consistent gamer experience
  • Play Games Sidekick
  • Достижения
  • Статистика игры
  • Награды
  • Cloud save
• Expand your reach across all screens
  • Large screen optimization
  • Google Play Games on PC
  • Precision input controls
  • Form factor distribution
  • Доступность названия
• Deliver stable and smoother gameplay sessions
  • Стабильность
  • Производительность
  • Память
  • Vulkan
• Reference device list

Provide a consistent gamer experience

Our gaming platform introduces new mechanics and surfaces delivering an elevated, delightful, and consistent gaming experience for players. To deliver this, games should integrate the following user experience guidelines.

ИДЕНТИФИКАТОР	Руководство
LU-PA-GAA	Platform authentication : Integrate the Google Play Games Services v2 SDK and ensure it initializes at startup. This integration powers achievements, game stats, and cross-device sync, for players who have opted into these platform features. For more information, see Play Games Services .

Using Play Games Platform authentication does not require using Google's identity system, or that you even have an in-game identity system. If you would like to use an identity system, you are free to use any identity provider (such as Sign in with Google, third party providers, or a custom backend) to manage proprietary in-game accounts. Games with in-game accounts can use the Play Games Recall API to sync accounts between devices to make sign-in easier.

Исключения

ИДЕНТИФИКАТОР	Exemption
LU-PA-EAA	Games that primarily target players aged under 13 are not required to initialize Play Games Services or deploy other features in this section (Achievements, GSAPI, Sidekick, Rewards, or Cloud Save) to meet Level Up guidelines.

Play Games Sidekick

Play Games Sidekick is an overlay that helps players stay in their game by delivering relevant content, functionality, and offers directly to them. Players expect Sidekick to be available on games on the Play Games platform.

ИДЕНТИФИКАТОР	Руководство
LU-SK-GAA	Add Sidekick to your game. This can be done through enabling the feature in the Play Developer Console if your game is published in the App Bundle format. Alternatively, you can compile the Sidekick SDK directly into your game if you are using the legacy APK format for publishing, or you are using an incompatible DRM solution.

Исключения

While Sidekick benefits all players, it is not available for every audience. We have the following exemptions for this guideline:

ИДЕНТИФИКАТОР	Исключения
LU-SK-EAA	Games that primarily target players aged under 13. Because Sidekick is disabled on children's accounts, games that are primarily designed for children under 13 are exempt.
LU-SK-EAB	If a game has encountered a blocking issue with Sidekick, and they have reported it and had it accepted by Google, then they may be granted an exemption for an appropriate period of time to find a work around or for the issue to be addressed.

Дополнительные ресурсы

For more information, see Sidekick .

Достижения

Achievements are a core gaming experience to recognize and reward players for their accomplishment in their games.

ИДЕНТИФИКАТОР	Руководство
LU-AC-GAA	We require a minimum of 10 achievements spread across the lifetime of the game. Note that we recommend having 40+ achievements to provide robust, deep engagement with your players on the Google Play Games platform.
LU-AC-GAB	All achievements must have a unique name and description . These should make clear to players what they need to do to get the achievement.
LU-AC-GAC	To be eligible for Quests , a minimum of 4 achievements must be reasonably and reliably achievable within the first hour of gameplay by everyone who plays.

Исключения

While achievements are available for all players, they may not make sense for every audience. We have the following exemption for this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-AC-EAA	Games that primarily target players aged under 13.
LU-AC-EAB	Games are exempt from providing achievements if they lack sufficient clear events, progression, or player accomplishment within them. Note that progression mechanisms like lifetime high scores, levels, area unlocking or discovery, enemy or challenger defeats, story stages, XP, completion percentages, or item collection can be used to create achievements.

Дополнительные ресурсы

For information on how to integrate achievements into your game and best practices, see Achievements .

Статистика игры

Unlock deeper player engagement and boost your game's visibility across the Google Play Games platform with Game Stats. The Game Stats feature enables users to view their stats in their gamer profile and is used to power additional player engagement features across Play, such as Quests, Social Challenges, and more in the future.

ИДЕНТИФИКАТОР	Руководство
LU-GS-GAA	Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All repetitive stats need to represent regularly occurring actions by players in the game. At least 1 stat needs to be usable for competitive player engagement features.
LU-GS-GAB	If you have a primary progression mechanic, submit at least 1 additional player progression stat to power the Game Stats feature stored against the player's gamer profile. Progression level needs to be a metric that represents the player's progress in the game.

Player data for Game Stats should be submitted using Game Stats API through either client or server implementation. Each player progression or repetitive stat needs to be configured in Play provided tools. Raw data schema needs to be declared and mapped to a user facing Game Stats, including display string, unique icon and any aggregation rules.

ИДЕНТИФИКАТОР	Руководство
LU-GS-GAC	Each stat must follow the requirements described in Game Stats .

Most games should be able to provide appropriate signals. Examples are available to help you choose the correct data points that will enable the engagement mechanics.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-GS-EAA	Games that primarily target players aged under 13 Game Stats is not enabled for players under 13 years of age.
LU-GS-EAB	Games are exempt from providing player states only if they lack clear progression mechanisms. If your game includes features such as lifetime high scores, levels, XP, completion percentages, or primary item collection, it does not qualify for this exemption as these can be used as a progression mechanism.
LU-GS-EAC	Titles on Native PC Early Access Program (EAP) , given our SDK does not support this feature yet. (Note: This only applies to the Native PC version of your title).

Дополнительные ресурсы

For more information, see Game Stats .

Награды

Create Play Games Reward offers that Play can distribute to players for free as incentives and rewards including items already in the game or new items to drive increased engagement:

ИДЕНТИФИКАТОР	Руководство
LU-RE-GAA	All items need to be available to every player at least once using Play.
LU-RE-GAB	All items must be meaningful or desirable for players to ensure they effectively drive engagement.
LU-RE-GAC	September 30, 2026: At least 2 single-use Play Games Reward offers , such as specific characters, skins, or weapons. These Play Game rewards will be awarded to players after the successful completion of a Quest.
LU-RE-GAD	March 1, 2027 : At least 1 repeatable Play Games Reward offer , such as lives, temporary power-ups, daily reward items, in-game currency, or other consumables. These rewards will be awarded to players after successful completion of social challenges, with a maximum of 1 reward per week per player.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-RE-EAA	Games that primarily target players aged under 13. Reward items are used for features like quests and Social Challenges, which are generally unavailable to players under 13. If your game primarily targets this age group, you are exempt from providing reward items.
LU-RE-EAB	Paid games. Players expect to get the full game experience for paid games after their initial purchase. This applies to any game with a single purchase, whether upfront at install time or through a one-time in-game purchase. We won't reward additional in-game items for paid games.

Дополнительные ресурсы

For more information, see Play Games Rewards .

Cloud save

Players play on multiple devices and install their games on the same device multiple times. As a result, they always need to start their game from their last progress state. To achieve this, you must implement a cloud save solution in your game.

ИДЕНТИФИКАТОР	Руководство
LU-CS-GAA	A game must save the player's game state off-device in the cloud and retrieve it when they start the game.
LU-CS-GAB	A conflict resolution policy is required when a player has multiple in-game accounts or if there is a conflict between saved game data on their device and in the cloud. Usually, the player decides how to resolve these conflicts. Your conflict resolution policy should address the following scenarios: Multiple accounts per user: Handle instances where a single player interacts with the application using different accounts. State conflicts: Resolve discrepancies that arise between the local game state and the cloud-saved game state.

If you don't have an existing cloud save solution for your player progress, we recommend the Saved Games API as part of Play Games Services to provide this functionality. You are free to use any solution provider to meet this guideline.

We believe that every game should provide the ability for players to resume their progress across installs of the game.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-CS-EAA	Cloud save is not required for games that don't provide in-game accounts and only provide guest accounts or do not provide any saved game state across gaming sessions.
LU-CS-EAB	Games where the save files exceed the size limits of the Saved Games API (3 MB) and implementing an automated third-party cloud solution would be cost-prohibitive are exempt from the cloud save guidelines. However, we recommend developers provide an alternative solution, such as allowing players to manually download and upload their files.

Дополнительные ресурсы

For more information, see Cloud save .

Expand your reach across all screens

Players want to play their favourite titles seamlessly across all their devices, and we are expanding Android's reach to new screens and spaces. To help developers reap the benefits of growing audiences, developers need to publish optimized versions of their games across form factors.

All games must follow these guidelines to deliver cross device form factor game experience to join the Level Up program:

Large screen optimization

Players expect to play their games on any device form factor that the Google Play Games Platform supports. This includes large screen Android devices like tablets or foldable phones. Your game needs to provide resizability functionality to ensure players get the best experience on these form factors.

ИДЕНТИФИКАТОР	Руководство
LU-LS-GAA	Use insets to prevent blocking game controls or UIs that overlap with system bars (status, navigation, gesture) or display cutouts (notches, punch holes).
LU-LS-GAB	Support configuration changes (device rotation, fold/unfold, multi-window split, freeform window resizing) without crashes, ANRs, visual artifacts, or touch mapping offsets, while preserving active game state and progress.
LU-LS-GAC	Games displayed in landscape must render full screen without letterboxing or pillarboxing on Reference Devices and anchor ratios of 4:3, 16:10, and 21:9. Landscape-only games are not required to support a portrait layout, but must cleanly letterbox or pillarbox themselves on portrait displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.
LU-LS-GAD	Games displayed in portrait must render full screen without letterboxing or pillarboxing on reference devices and anchor ratios of 3:4, 10:16, and 9:21. Portrait-only games are not required to support a landscape layout, but must cleanly letterbox/pillarbox themselves on landscape displays. Out-of-anchor ratios may also be letterboxed/pillarboxed.

Дополнительные ресурсы

• Refer to the Form factor distribution guideline for any form factor specific exemptions.

• For more information on handling large screen resizability, see Support large screen resizability .

Google Play Games on PC

Google Play Games on PC brings the best of Google Play by enabling players to experience an immersive and seamless cross-platform gameplay.

ИДЕНТИФИКАТОР

Руководство

LU-PC-GAA

Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC . Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution. OR, Your game is published as a Native PC game on Google Play Games and integrates with the PC SDK * .

Исключения

There are some games where distribution on PCs is challenging. The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-PC-EAA	Form factor constraints would meaningfully degrade a quality experience . Titles that have critical gameplay technical requirements that are not available on the Google Play Games on PC form factor or where the Google Play Games on PC form factor will create a meaningfully degraded player experience, for example: Augmented reality and location-based games rely fundamentally on the physical geographic displacement of the device. Games utilizing local mobile hardware sensors (like breath input or sleep tracking) cannot be simulated and are critical to the core gameplay loop without workarounds. Games with mechanics requiring the user to physically rotate their entire body in 360-degree real-world space to locate digital assets.
LU-PC-EAB	Platform-specific title-level IP-licensing limitation. Some developers have licensed their mobile game's title-level IP from a third party licensor. These agreements may restrict the developer's license, prohibiting the publishing of the title on PCs without first acquiring additional licensed rights. Such licensed-IP games for which the license grant excludes publishing such games to PCs may be eligible for the exemption.
LU-PC-EAC	( Paid Games Only ) Mobile to PC price differential. Paid games distributed through the Play store prior to September 30, 2026 with a pre-existing PC-to-mobile price differential.

Дополнительные ресурсы

For more information on distributing to PC with Google Play, see Google Play Games on PC .

Precision input controls

Supporting multiple form factors means supporting the device's natural input, and in general allowing the user to play the way they feel best. This means that games must support controller and keyboard and mouse input for the best cross-screen gaming experiences.

ИДЕНТИФИКАТОР	Руководство
LU-IC-GAA	The game must be fully playable with a controller, keyboard, and mouse (K&M) across all devices the game supports through the Play Games platform where these modes of input are available. Fully playable means the game can be played entirely from the start, including all gameplay mechanics and settings menus, without the need to fall back to touch input.

Исключения

Not all mobile mechanics translate seamlessly to precision input controls. The following exemptions are driven by core gameplay mechanics and how we believe different modes of input fundamentally affect the player experience.

ИДЕНТИФИКАТОР	Критерии	Контроллеры Необходимый	К&М Необходимый
LU-IC-EAA	GPS / Location-Based Spatial Mapping : Augmented reality and location-based games rely fundamentally on the physical geographic displacement of the device.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAB	Ambient Sensors (Microphone/Sleep Tracking) : Titles utilizing local mobile hardware sensors (like breath input or sleep tracking) cannot be simulated and are critical to the core gameplay loop without workarounds.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAC	Kinetic Camera / AR Panoramas : Mechanics requiring the user to physically rotate their entire body in 360-degree real-world space to locate digital assets.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAD	Gyroscopic / Accelerometer Spatial Aiming: Games that rely on a gyro or accelerometer being present on the device to play the game, and would otherwise require a significant reworking of the user experience in order to support precision inputs.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAE	Intense Rapid Swiping and Multi-Touch Rhythm: Rhythm games (Music genre) demand simultaneous, synchronous actuation of multiple screen nodes, which a single mouse cursor cannot execute mathematically. Controllers lack the physical layout to map dynamic 6-to-8 lane rhythm charts intuitively.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAF	Gestural Drawing / Freehand Vectors : Drawing specific geometric shapes or freehand paths is effectively impossible to replicate cleanly using the strict radial constraints of a controller thumbstick.	❌ (необязательно)	✅ (необходимый)
LU-IC-EAG	Drag-and-Drop / Absolute Point-and-Click : Executing rapid drag-and-drop mechanics with a relative radial thumbstick is kinetically unviable and vastly slower than absolute touch.	❌ (необязательно)	✅ (необходимый)

Дополнительные ресурсы

For more information about supporting precision inputs within your game, see Enable natural input on all form factors . When supporting controllers, make sure to add this flag to your manifest so that users can find your game when searching for controller-supported games in the store.

Form factor distribution

The Google Play Games platform is available across many different Android device form factors and players expect to play their games across them all.

ИДЕНТИФИКАТОР	Руководство
LU-FF-GAA	Your game must be distributed across the following Android form factors with exemplary quality: September 30, 2026 : Mobile , Foldables, and Tablets September 30, 2027 : Android XR , Android TV , Googlebook , and Android Auto

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-FF-EAA	Form factor constraints would meaningfully degrade a quality experience . Titles that have critical gameplay technical requirements that are not available on the form factor or where the form factor will create a meaningfully degraded player experience.

Например:

Gameplay mechanic	Form Factors exempt from distribution
Augmented reality and location-based games rely fundamentally on the physical geographic displacement of the device	Google Play Games on PC, Tablets, Googlebook, Android TV
Games utilizing local mobile hardware sensors (like breath input or sleep tracking) cannot be simulated and are critical to the core gameplay loop without workarounds.	Google Play Games on PC, Tablets, Googlebook, Android TV, Android Auto
Games with mechanics requiring the user to physically rotate their entire body in 360-degree real-world space to locate digital assets.	Google Play Games on PC, Googlebook, Android TV, Android Auto

ИДЕНТИФИКАТОР	Exemption
LU-FF-EAB	Devices with technical specifications below the minimum Mobile hardware requirements. Games are exempt from distribution on devices with hardware (RAM, CPU, storage, or GPU) or Android versions that fall below your minimum mobile phone requirements.
LU-FF-EAC	Form factor availability. Games are exempt from distribution on devices that are not available in any of the regions where the game is offered—meaning there is no overlap in regional availability between the device and the game.

Доступность названия

Players enjoy the flexibility of choosing their preferred devices while maintaining seamless access to their entire library of gaming experiences.

ИДЕНТИФИКАТОР	Руководство
LU-TA-GAA	For titles to be eligible for the program rate card benefits those titles must be released on Android supported form factors at the same time they become available on any other comparable, non-Android form factors from September 30th 2026 and moving forward.

Currently required Android supported form factors include:

• Mobile and Large Screen (Tablet, Googlebooks, PC)
• Android XR (with titles running in a 2D window on the XR device)
• Android TV
• Android Auto

Titles that do not meet this title availability guideline will become eligible for the Level Up program rate card benefits following a 6-month waiting period , once all user experience guidelines are fully met.

Examples :

• If a title is applying to be in the Level Up program and such title is currently available on other comparable non-Android form factors, such title must be launched on all comparable Android form factors for at least 6 months prior to enrollment into Level Up otherwise they will not be eligible for the program benefits until 6 months after the launch of their title on the Android form factor. The 6 month waiting period does not apply if the title was launched on the non-Android form factor prior to September 30th, 2026.
• If a title currently enrolled in the program launches a comparable non-Android form factor and does not launch on the comparable Android form factor simultaneously, they will become ineligible for program benefits for 6 months.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-TA-EAA	Differences between device platforms. Not every game is technically or conceptually suited for every hardware configuration; therefore, the title will be exempt if the developer can demonstrate that a specific Android form factor's constraints would meaningfully degrade the user experience against the comparable non-Android platform or if there is no viable technical solution for that hardware.
LU-TA-EAB	Launch grace period. To account for unforeseen technical hurdles, store review delays, or "soft launches," we will implement the following: Standard grace period. Developers are granted a 15-day window to achieve "live" status on the Google Play Store. Extended grace period. In exceptional circumstances where a developer can demonstrate that the delay was caused by a Google-side technical issue or an unusually long app review process, the grace period may be extended to 30 days upon manual review.
LU-TA-EAC	EEA. This guideline does not apply in the EEA. However, when distributing to the EEA, Android users should be able to access all new experiences and capabilities within the Android title provided by the developer. Developers are therefore required to fully optimize their titles for Android.

Deliver stable and smoother gameplay sessions

To ensure games run beautifully across all form factors, we are introducing quality benchmarks that guarantee both performance and stability for players. All games must follow these user experience guidelines to provide a high quality experience to join the Level Up program.

Стабильность

Players expect their games to provide a stable experience on their device that is free of crashes and Android Not Responding (ANRs). Games need to meet the following quality thresholds. To reduce volatility, these thresholds will be enforced based on the trailing 28 days of data considering only devices within the approved set for which your app has at least 1,500 sessions in the last 28 days.

	LU-ST-GAA	LU-ST-GAB
Основные параметры Android	Test devices	4GB+ RAM Android Devices
Аварии	<1% average crash rate Check metrics in Play Console info	<2% average crash rate Check metrics in Play Console ) info
АНР	<2% average ANR rate Check metrics in Play Console info	<3% average ANR rate Check metrics in Play Console ) info

Исключения

There are no exemptions for this guideline.

Дополнительные ресурсы

For more information diagnosing and fixing vital issues, see Android vitals .

Производительность

A smooth and stable framerate is critical to delivering a high quality gaming experience on Android devices.

ИДЕНТИФИКАТОР	Руководство
LU-PR-GAA	On reference devices , active gameplay scenes must target and render at a minimum of 60 fps by default. This requirement specifically applies to real-time, active gameplay and excludes non-interactive or transitionary states such as loading/splash screens, content downloads, lobby interfaces, menus, and cinematic cutscenes: Average FPS ≥ 55 FPS Low 10% (P90) FPS ≥ 50 FPS Low 1% (P99) FPS ≥ 30 FPS

Исключения

Mobile games have to make many difficult decisions about what high quality means for their specific experience – such as whether to favor graphical fidelity or battery life during a play session. The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-PR-EAA	Games that do not support 60 FPS on other non-Android mobile platforms.
LU-PR-EAB	Games that use HWUI or Composer rather than rendering directly.
LU-PR-EAC	Games that only push new frames on player interaction , rather than on a continuously regular basis.
LU-PR-EAD	Games are not required to meet this on Tablet and Foldable devices due to their challenges in thermal design and computations to support high-resolution screens.

Дополнительные ресурсы

For additional details on calculating and measuring Level Up performance, see frame rate . You can also explore the slow sessions documentation for optimization strategies regarding frame smoothness.

Память

To deliver a premium experience, Android 17 introduced optimized memory handling and stricter platform requirements, which is accompanied by new, actionable memory telemetry in the Play Console.

Effective February 2027 , Play requires games to meet established bad-behavior thresholds for dynamic memory usage (anonymous RSS + swap), bitmap usage, and code optimization across all Android versions. Developers can now monitor these memory metrics and bad behavior thresholds within Android vitals .

ИДЕНТИФИКАТОР	Руководство
LU-MM-GAA	Once enforcement for these memory thresholds are in effect, games must comply with all memory thresholds to qualify for or maintain Level Up eligibility. You can find the memory thresholds and enforcement timeline here . Optimize your game : Follow the latest guidance for games to maximize memory savings across process states.

Исключения

There are no exemptions for this guideline.

Vulkan

Vulkan is Android's modern graphics API that offers significant improvements in performance and battery usage. It also offers new higher fidelity graphical techniques that will improve the gameplay experience on Android.

Older games might prefer to access Vulkan through ANGLE rather than converting their own code to Vulkan. ANGLE is Google's conformant OpenGL ES translation layer for Windows, Mac, Linux, iOS and Android. ANGLE uses Vulkan under the hood.

ИДЕНТИФИКАТОР

Руководство

LU-VK-GAA

On devices that have updated graphics drivers, where DEQP ≥ 20240301 : If you are using Unity version 2023 or newer , or Unreal Engine version 4.25 or newer : Vulkan must be set as the primary graphics API . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as it is <10% of frames. Games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path. If you are using an older version of Unity or Unreal, or any other game engine, then you are required to either use Vulkan or enable ANGLE rendering to meet this guideline. To opt-in to use ANGLE, modify your app's manifest file as follow: <application android:appCategory="game"> <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" /> </application>

Исключения

Our default stance is that all games should adopt Vulkan because it offers considerable performance and battery benefits. The following exception recognizes that some games might not have a choice on graphics API.

ИДЕНТИФИКАТОР	Exemption
LU-VK-EAA	Games that don't control their own rendering and render through HWUI/SKIA (similar to how apps render). These games have no control over their graphics pipeline, and will be moved to Vulkan automatically over the coming versions of Android.
LU-VK-EAB	If your game uses WebGPU as its rendering API. WebGPU is a new higher level language that uses Vulkan on newer devices and OpenGL ES on older devices. If for some reason WebGPU decides not to use Vulkan on a focus device, that is beyond the control of the developer. We're working on deploying the Vulkan backend on as many devices as possible as quickly as possible.
LU-VK-EAC	If a game has encountered a blocking issue with Vulkan, and they have reported it and had it accepted by the relevant code-maintainer (For example, a Game Engine, GPU-IP Vendor, or Google), then they may be granted an exemption for an appropriate period of time to find a work around or for the issue to be addressed.
LU-VK-EAD	A developer may be exempt from this requirement if they are able to reduce their CPU instruction count in a similar fashion to what Vulkan provides. Vulkan provides an approximate 30% reduction in CPU instruction count as compared to other solutions. If the developer can show a similar improvement with an alternative solution, then the use of Vulkan is not required.

Дополнительные ресурсы

For more information on upgrading your game's graphics APIs, see Vulkan .

Reference device list

The following devices are used to test our guidelines. Because Android hardware and features evolve, this list can be updated to ensure comprehensive coverage.

Список устройств

Год	System on a Chip продавец	System on a Chip модель	Производитель	Маркетинговое название	Форм-фактор
2026	GOOGLE	TENSOR G5	GOOGLE	PIXEL 10 PRO XL	ТЕЛЕФОН
				PIXEL 10 PRO FOLD	FOLDABLE
	MEDIATEK	MT6993	VIVO	X300	ТЕЛЕФОН
				X300 PRO	ТЕЛЕФОН
			OPPO	FIND X9 PRO	ТЕЛЕФОН
				FIND X9	ТЕЛЕФОН
	QTI	SM8845	ONEPLUS	ONEPLUS 15R	ТЕЛЕФОН
			ЛЕНОВО	MOTOROLA SIGNATURE	ТЕЛЕФОН
		SM8850	SAMSUNG	GALAXY S26 ULTRA	ТЕЛЕФОН
				GALAXY S26	ТЕЛЕФОН
				GALAXY S26+	ТЕЛЕФОН
			ONEPLUS	ONEPLUS 15	ТЕЛЕФОН
			OPPO	FIND N6	FOLDABLE
			СЯОМИ	СЯОМИ 17	ТЕЛЕФОН
				XIAOMI 17 ULTRA	ТЕЛЕФОН
				LEITZPHONE POWERED BY XIAOMI	ТЕЛЕФОН
				XIAOMI 17 PRO MAX	ТЕЛЕФОН
	SAMSUNG	S5E9965	SAMSUNG	GALAXY S26	ТЕЛЕФОН
				GALAXY S26+	ТЕЛЕФОН
2025	GOOGLE	TENSOR G4	GOOGLE	PIXEL 9 PRO XL	ТЕЛЕФОН
				PIXEL 9 PRO FOLD	FOLDABLE
	MEDIATEK	MT6991	СЯОМИ	XIAOMI 15T PRO	ТЕЛЕФОН
			SAMSUNG	GALAXY TAB S11	ПЛАНШЕТ
				GALAXY TAB S11 ULTRA	ПЛАНШЕТ
				GALAXY TAB S11 ULTRA 5G	ПЛАНШЕТ
				GALAXY TAB S11 5G	ПЛАНШЕТ
			VIVO	VIVO X200	ТЕЛЕФОН
				X200 PRO	ТЕЛЕФОН
				X200T	ТЕЛЕФОН
			OPPO	FIND X8	ТЕЛЕФОН
				FIND X8 PRO	ТЕЛЕФОН
	QTI	SM8735	СЯОМИ	XIAOMI PAD 8	ПЛАНШЕТ
		SM8750	SAMSUNG	GALAXY S25 ULTRA	ТЕЛЕФОН
				ГАЛАКСИЯ S25	ТЕЛЕФОН
				GALAXY S25+	ТЕЛЕФОН
				GALAXY S25 EDGE	ТЕЛЕФОН
				GALAXY Z FOLD7	FOLDABLE
			ONEPLUS	ONEPLUS 13	ТЕЛЕФОН
				ONEPLUS 13S	ТЕЛЕФОН
				PAD 3	ПЛАНШЕТ
			OPPO	FIND N5	FOLDABLE
			СЯОМИ	XIAOMI 15	ТЕЛЕФОН
				XIAOMI 15 ULTRA	ТЕЛЕФОН
			СОНИ	XPERIA 1 VII	ТЕЛЕФОН
			VIVO	IQOO 13	ТЕЛЕФОН

Comprehensive testing across every specific model may not be required because several devices in the list use identical SoCs and exhibit comparable performance. Developers are eligible to self-certify for the guidelines once they have successfully verified requirements on at least one device from each listed SoCs:

Телефоны

Год	System on a Chip	Устройства
2026	Тензор G5	PIXEL 10 PRO XL
2025	Tensor G4	PIXEL 9 PRO XL
2026	MTK MT6993	X300, FIND X9
2025	MTK MT6991	XIAOMI 15T PRO, GALAXY TAB S11, VIVO X200, FIND X8
2026	QCOM SM8845/8850	ONEPLUS 15R, MOTOROLA SIGNATURE, GALAXY S26, ONEPLUS 15, XIAOMI 17
2025	QCOM SM8750	GALAXY S25, ONEPLUS 13, PAD 3, XIAOMI 15. XPERIA 1 VII, IQOO 13
2026	Exynos S5E9965	GALAXY S26

Планшет

Год	System on a Chip	Устройства
2025	MTK MT6991	GALAXY TAB S11
2025	QCOM SM8735	XIAOMI PAD 8
2025	QCOM SM8750	OPPO PAD 3

Контроллеры

For controllers, make sure to test your game with the following as it covers the common styles of controllers supported on the platform today:

• Беспроводной контроллер Sony DualSense
• XBox Wireless Controller
• Nintendo Switch Pro Controller (note: This is for the original Switch console)

We recommend using the testing guidance here for more details.

Примечания к изменениям

Сентябрь 2026 г.

• Производительность

  • Guidelines updated: LU-PF-GAA

  • Previous text:

    Games that do not support 60 FPS on other platforms.

  • New text:

    Games that do not support 60 FPS on other non-Android mobile platforms.

• Large screen optimization

  • Guidelines updated: LU-LS-GAA , LU-LS-GAB LU-LS-GAC , LU-LS-GAD

  • Previous text:

    • Handle system bars , display cutouts , and configuration changes —such as device rotation and window resizing—to prevent crashes and visual artifacts. Ensure all UI and gameplay elements remain visible and interactive, avoiding any obstructions that block player input, while correctly maintaining or restoring the game state.

    • Games in a landscape layout need to be full screen, without letterboxing or pillarboxing, at the aspect ratios for each reference device and also at the anchor aspect ratios of 4:3, 16:10, and 21:9.

    • Games in a portrait layout similarly need to support the complement aspect ratios. For example, for the anchor ratios the equivalent is 3:4, 10:16, and 9:21.

    • Games are able to letterbox or pillar box themselves under the following conditions:

      • On a device with an aspect ratio that is not found on a flagship device or outside one of the anchor aspect ratios defined previously.
      • If the only game layout orientation (portrait or landscape) is different from the device's physical orientation.

  • New text:

    • Use insets to prevent blocking game controls or UIs that overlap with system bars (status, navigation, gesture) or display cutouts (notches, punch holes).

    • Support configuration changes (device rotation, fold/unfold, multi-window split, freeform window resizing) without crashes, ANRs, visual artifacts, or touch mapping offsets, while preserving active game state and progress.

    • Games displayed in landscape must render full screen without letterboxing or pillarboxing on Reference Devices and anchor ratios of 4:3, 16:10, and 21:9. Landscape-only games are not required to support a portrait layout, but must cleanly letterbox or pillarbox themselves on portrait displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.

    • Games displayed in portrait must render full screen without letterboxing or pillarboxing on reference devices and anchor ratios of 3:4, 10:16, and 9:21.Portrait-only games are not required to support a landscape layout, but must cleanly letterbox or pillarbox themselves on landscape displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.

• Google Play Games on PC

  • Guidelines updated: LU-GPGC-GAA

  • Previous text:

    Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC .

    • Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution.
    • OR, Your game is part of the Native PC Early Access Program (EAP) .

  • New text:

    Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC .

    • Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution.
    • OR, Your game is published as a Native PC game on Google Play Games and integrates with the PC SDK ^* .

    ^* If you publish as a Native PC Game, your title won't need to support Sidekick, Cloud Save, Achievements, and Game Stats API for the PC version until those features become available in the Google Play Games on PC SDK.

• Precision input controls

  • New text:

• Form factor distribution

  • Guideline updated: LU-FF-GAA

  • Previous text:

    • September 2026 : Mobile , Foldables, and Tablets
    • March 1, 2027 : Googlebook
    • September 2027 : Android XR , Android TV , and Android Auto

  • New text:

    • September 2026 : Mobile , Foldables, and Tablets
    • September 2027 : Android XR , Android TV , Googlebook , and Android Auto

• Vulkan

  • Guideline updated: LU-VK-GAA
  • Previous text:
  • Vulkan must be set as the primary graphics API if you are using Unity version 2021 or newer , or Unreal Engine version 4.25 or newer . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as it is <10% of frames.
  • Instead of using Vulkan directly, games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path.

  • All other games can decide to either use Vulkan as the primary graphics API or opt-in to using ANGLE for Android 17+ devices. To opt in to use ANGLE modify the app's manifest file as follows:

    <application android:appCategory="game">
    <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" />
    </application>
    

  • New text:

  • If you are using Unity version 2023 or newer , or Unreal Engine version 4.25 or newer :

  • Vulkan must be set as the primary graphics API . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as its <10% of frames.

  • Games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path.

  • If you are using an older version of Unity or Unreal, or any other game engine, then you are required to either use Vulkan or enable ANGLE rendering to meet this guideline. To opt-in to use ANGLE, modify your app's manifest file as follow:

    <application android:appCategory="game">
    <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" />
    </application>
    

• Память

  • Guidelines updated: LU-MM-GAA

  • Previous text:

    To deliver a premium experience, Android 17 is introducing optimized memory handling and stricter platform requirements later this year–accompanied by new, actionable memory telemetry in the Play Console. Because meeting these standard memory limits will be required for Level Up, we strongly encourage [implementing these memory optimization strategies][bbb] early to ensure app stability and a great user experience. More detailed compliance criteria to maintain your program status will be shared in the coming months.

  • New text:

    To deliver a premium experience, Android 17 introduced optimized memory handling and stricter platform requirements, which is accompanied by new, actionable memory telemetry in the Play Console.

    Effective February 2027 , Play requires games to meet established bad-behavior thresholds for dynamic memory usage (anonymous RSS + swap), bitmap usage, and code optimization across all Android versions. Developers can now monitor these memory metrics and bad behavior thresholds within Android vitals .

    Once enforcement for these memory thresholds are in effect, games must comply with all memory thresholds to qualify for or maintain Level Up eligibility. You can find the memory thresholds and enforcement timeline here .

    Optimize your game : Follow the latest guidance for games to maximize memory savings across process states.

Июль 2026 г.

• Статистика игры
  • Guidelines updated: LU-GS-GAA
  • Exemption updated: LU-GS-EAC
  • Previous text:
    • Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All stats need to represent regularly occurring actions by players in the game.
    • At least 1 stat needs to be usable for competitive player engagement features.
    • Stats should not require a purchase (For example, buy gems).
    • Stats should not require watching advertisements.
    • Stats should not be generic use of the game (For example, open the game; use settings).
    • Stats should be available to all users (For example, not a team-specific action).
  • New text:
    • Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All repetitive stats need to represent regularly occurring actions by players in the game.
      • At least 1 stat needs to be usable for competitive player engagement features.
    • Exemption: Titles on Native PC Early Access Program (EAP), given our SDK doesn't support this feature yet. (Note: This only applies to the Native PC version of your title).

,

Google Play Games revamped Level Up is a program to recognize and reward great gaming experiences with program rate card benefits to drive business growth for your game. Participation in this program is voluntary and developers that choose not to participate will not have a change in benefits they are entitled through other programs. Developers can enroll through Play Console starting September 1, 2026. For more information, see Enroll in the Level Up program .

Our mission is to connect players with the best gaming experiences—ones that provide a consistent gamer experience , reach across all screens and deliver stable and smoother gameplay sessions .

Player expectations and developer needs are always evolving, and the program is designed to evolve with them. User experience guidelines and benefits may be updated over time. To help you maintain your program status, we will provide reasonable notice and detailed documentation before any program updates take effect, ensuring you have sufficient time to implement required changes.

This page describes the user experience guidelines. To know more about the Level Up program and benefits, visit the Google Play Games | Level Up program page .

User experience guidelines

To gain access to the Level Up program rate card benefits, your game needs to adhere to all the user experience guidelines outlined on this page. These guidelines may be updated from time to time as the program evolves.

The following sections outline the guidelines with three main themes:

• Provide a consistent gamer experience
  • Play Games Sidekick
  • Достижения
  • Статистика игры
  • Награды
  • Cloud save
• Expand your reach across all screens
  • Large screen optimization
  • Google Play Games on PC
  • Precision input controls
  • Form factor distribution
  • Доступность названия
• Deliver stable and smoother gameplay sessions
  • Стабильность
  • Производительность
  • Память
  • Vulkan
• Reference device list

Provide a consistent gamer experience

Our gaming platform introduces new mechanics and surfaces delivering an elevated, delightful, and consistent gaming experience for players. To deliver this, games should integrate the following user experience guidelines.

ИДЕНТИФИКАТОР	Руководство
LU-PA-GAA	Platform authentication : Integrate the Google Play Games Services v2 SDK and ensure it initializes at startup. This integration powers achievements, game stats, and cross-device sync, for players who have opted into these platform features. For more information, see Play Games Services .

Using Play Games Platform authentication does not require using Google's identity system, or that you even have an in-game identity system. If you would like to use an identity system, you are free to use any identity provider (such as Sign in with Google, third party providers, or a custom backend) to manage proprietary in-game accounts. Games with in-game accounts can use the Play Games Recall API to sync accounts between devices to make sign-in easier.

Исключения

ИДЕНТИФИКАТОР	Exemption
LU-PA-EAA	Games that primarily target players aged under 13 are not required to initialize Play Games Services or deploy other features in this section (Achievements, GSAPI, Sidekick, Rewards, or Cloud Save) to meet Level Up guidelines.

Play Games Sidekick

Play Games Sidekick is an overlay that helps players stay in their game by delivering relevant content, functionality, and offers directly to them. Players expect Sidekick to be available on games on the Play Games platform.

ИДЕНТИФИКАТОР	Руководство
LU-SK-GAA	Add Sidekick to your game. This can be done through enabling the feature in the Play Developer Console if your game is published in the App Bundle format. Alternatively, you can compile the Sidekick SDK directly into your game if you are using the legacy APK format for publishing, or you are using an incompatible DRM solution.

Исключения

While Sidekick benefits all players, it is not available for every audience. We have the following exemptions for this guideline:

ИДЕНТИФИКАТОР	Исключения
LU-SK-EAA	Games that primarily target players aged under 13. Because Sidekick is disabled on children's accounts, games that are primarily designed for children under 13 are exempt.
LU-SK-EAB	If a game has encountered a blocking issue with Sidekick, and they have reported it and had it accepted by Google, then they may be granted an exemption for an appropriate period of time to find a work around or for the issue to be addressed.

Дополнительные ресурсы

For more information, see Sidekick .

Достижения

Achievements are a core gaming experience to recognize and reward players for their accomplishment in their games.

ИДЕНТИФИКАТОР	Руководство
LU-AC-GAA	We require a minimum of 10 achievements spread across the lifetime of the game. Note that we recommend having 40+ achievements to provide robust, deep engagement with your players on the Google Play Games platform.
LU-AC-GAB	All achievements must have a unique name and description . These should make clear to players what they need to do to get the achievement.
LU-AC-GAC	To be eligible for Quests , a minimum of 4 achievements must be reasonably and reliably achievable within the first hour of gameplay by everyone who plays.

Исключения

While achievements are available for all players, they may not make sense for every audience. We have the following exemption for this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-AC-EAA	Games that primarily target players aged under 13.
LU-AC-EAB	Games are exempt from providing achievements if they lack sufficient clear events, progression, or player accomplishment within them. Note that progression mechanisms like lifetime high scores, levels, area unlocking or discovery, enemy or challenger defeats, story stages, XP, completion percentages, or item collection can be used to create achievements.

Дополнительные ресурсы

For information on how to integrate achievements into your game and best practices, see Achievements .

Статистика игры

Unlock deeper player engagement and boost your game's visibility across the Google Play Games platform with Game Stats. The Game Stats feature enables users to view their stats in their gamer profile and is used to power additional player engagement features across Play, such as Quests, Social Challenges, and more in the future.

ИДЕНТИФИКАТОР	Руководство
LU-GS-GAA	Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All repetitive stats need to represent regularly occurring actions by players in the game. At least 1 stat needs to be usable for competitive player engagement features.
LU-GS-GAB	If you have a primary progression mechanic, submit at least 1 additional player progression stat to power the Game Stats feature stored against the player's gamer profile. Progression level needs to be a metric that represents the player's progress in the game.

Player data for Game Stats should be submitted using Game Stats API through either client or server implementation. Each player progression or repetitive stat needs to be configured in Play provided tools. Raw data schema needs to be declared and mapped to a user facing Game Stats, including display string, unique icon and any aggregation rules.

ИДЕНТИФИКАТОР	Руководство
LU-GS-GAC	Each stat must follow the requirements described in Game Stats .

Most games should be able to provide appropriate signals. Examples are available to help you choose the correct data points that will enable the engagement mechanics.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-GS-EAA	Games that primarily target players aged under 13 Game Stats is not enabled for players under 13 years of age.
LU-GS-EAB	Games are exempt from providing player states only if they lack clear progression mechanisms. If your game includes features such as lifetime high scores, levels, XP, completion percentages, or primary item collection, it does not qualify for this exemption as these can be used as a progression mechanism.
LU-GS-EAC	Titles on Native PC Early Access Program (EAP) , given our SDK does not support this feature yet. (Note: This only applies to the Native PC version of your title).

Дополнительные ресурсы

For more information, see Game Stats .

Награды

Create Play Games Reward offers that Play can distribute to players for free as incentives and rewards including items already in the game or new items to drive increased engagement:

ИДЕНТИФИКАТОР	Руководство
LU-RE-GAA	All items need to be available to every player at least once using Play.
LU-RE-GAB	All items must be meaningful or desirable for players to ensure they effectively drive engagement.
LU-RE-GAC	September 30, 2026: At least 2 single-use Play Games Reward offers , such as specific characters, skins, or weapons. These Play Game rewards will be awarded to players after the successful completion of a Quest.
LU-RE-GAD	March 1, 2027 : At least 1 repeatable Play Games Reward offer , such as lives, temporary power-ups, daily reward items, in-game currency, or other consumables. These rewards will be awarded to players after successful completion of social challenges, with a maximum of 1 reward per week per player.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-RE-EAA	Games that primarily target players aged under 13. Reward items are used for features like quests and Social Challenges, which are generally unavailable to players under 13. If your game primarily targets this age group, you are exempt from providing reward items.
LU-RE-EAB	Paid games. Players expect to get the full game experience for paid games after their initial purchase. This applies to any game with a single purchase, whether upfront at install time or through a one-time in-game purchase. We won't reward additional in-game items for paid games.

Дополнительные ресурсы

For more information, see Play Games Rewards .

Cloud save

Players play on multiple devices and install their games on the same device multiple times. As a result, they always need to start their game from their last progress state. To achieve this, you must implement a cloud save solution in your game.

ИДЕНТИФИКАТОР	Руководство
LU-CS-GAA	A game must save the player's game state off-device in the cloud and retrieve it when they start the game.
LU-CS-GAB	A conflict resolution policy is required when a player has multiple in-game accounts or if there is a conflict between saved game data on their device and in the cloud. Usually, the player decides how to resolve these conflicts. Your conflict resolution policy should address the following scenarios: Multiple accounts per user: Handle instances where a single player interacts with the application using different accounts. State conflicts: Resolve discrepancies that arise between the local game state and the cloud-saved game state.

If you don't have an existing cloud save solution for your player progress, we recommend the Saved Games API as part of Play Games Services to provide this functionality. You are free to use any solution provider to meet this guideline.

We believe that every game should provide the ability for players to resume their progress across installs of the game.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-CS-EAA	Cloud save is not required for games that don't provide in-game accounts and only provide guest accounts or do not provide any saved game state across gaming sessions.
LU-CS-EAB	Games where the save files exceed the size limits of the Saved Games API (3 MB) and implementing an automated third-party cloud solution would be cost-prohibitive are exempt from the cloud save guidelines. However, we recommend developers provide an alternative solution, such as allowing players to manually download and upload their files.

Дополнительные ресурсы

For more information, see Cloud save .

Expand your reach across all screens

Players want to play their favourite titles seamlessly across all their devices, and we are expanding Android's reach to new screens and spaces. To help developers reap the benefits of growing audiences, developers need to publish optimized versions of their games across form factors.

All games must follow these guidelines to deliver cross device form factor game experience to join the Level Up program:

Large screen optimization

Players expect to play their games on any device form factor that the Google Play Games Platform supports. This includes large screen Android devices like tablets or foldable phones. Your game needs to provide resizability functionality to ensure players get the best experience on these form factors.

ИДЕНТИФИКАТОР	Руководство
LU-LS-GAA	Use insets to prevent blocking game controls or UIs that overlap with system bars (status, navigation, gesture) or display cutouts (notches, punch holes).
LU-LS-GAB	Support configuration changes (device rotation, fold/unfold, multi-window split, freeform window resizing) without crashes, ANRs, visual artifacts, or touch mapping offsets, while preserving active game state and progress.
LU-LS-GAC	Games displayed in landscape must render full screen without letterboxing or pillarboxing on Reference Devices and anchor ratios of 4:3, 16:10, and 21:9. Landscape-only games are not required to support a portrait layout, but must cleanly letterbox or pillarbox themselves on portrait displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.
LU-LS-GAD	Games displayed in portrait must render full screen without letterboxing or pillarboxing on reference devices and anchor ratios of 3:4, 10:16, and 9:21. Portrait-only games are not required to support a landscape layout, but must cleanly letterbox/pillarbox themselves on landscape displays. Out-of-anchor ratios may also be letterboxed/pillarboxed.

Дополнительные ресурсы

• Refer to the Form factor distribution guideline for any form factor specific exemptions.

• For more information on handling large screen resizability, see Support large screen resizability .

Google Play Games on PC

Google Play Games on PC brings the best of Google Play by enabling players to experience an immersive and seamless cross-platform gameplay.

ИДЕНТИФИКАТОР

Руководство

LU-PC-GAA

Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC . Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution. OR, Your game is published as a Native PC game on Google Play Games and integrates with the PC SDK * .

Исключения

There are some games where distribution on PCs is challenging. The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-PC-EAA	Form factor constraints would meaningfully degrade a quality experience . Titles that have critical gameplay technical requirements that are not available on the Google Play Games on PC form factor or where the Google Play Games on PC form factor will create a meaningfully degraded player experience, for example: Augmented reality and location-based games rely fundamentally on the physical geographic displacement of the device. Games utilizing local mobile hardware sensors (like breath input or sleep tracking) cannot be simulated and are critical to the core gameplay loop without workarounds. Games with mechanics requiring the user to physically rotate their entire body in 360-degree real-world space to locate digital assets.
LU-PC-EAB	Platform-specific title-level IP-licensing limitation. Some developers have licensed their mobile game's title-level IP from a third party licensor. These agreements may restrict the developer's license, prohibiting the publishing of the title on PCs without first acquiring additional licensed rights. Such licensed-IP games for which the license grant excludes publishing such games to PCs may be eligible for the exemption.
LU-PC-EAC	( Paid Games Only ) Mobile to PC price differential. Paid games distributed through the Play store prior to September 30, 2026 with a pre-existing PC-to-mobile price differential.

Дополнительные ресурсы

For more information on distributing to PC with Google Play, see Google Play Games on PC .

Precision input controls

Supporting multiple form factors means supporting the device's natural input, and in general allowing the user to play the way they feel best. This means that games must support controller and keyboard and mouse input for the best cross-screen gaming experiences.

ИДЕНТИФИКАТОР	Руководство
LU-IC-GAA	The game must be fully playable with a controller, keyboard, and mouse (K&M) across all devices the game supports through the Play Games platform where these modes of input are available. Fully playable means the game can be played entirely from the start, including all gameplay mechanics and settings menus, without the need to fall back to touch input.

Исключения

Not all mobile mechanics translate seamlessly to precision input controls. The following exemptions are driven by core gameplay mechanics and how we believe different modes of input fundamentally affect the player experience.

ИДЕНТИФИКАТОР	Критерии	Контроллеры Необходимый	К&М Необходимый
LU-IC-EAA	GPS / Location-Based Spatial Mapping : Augmented reality and location-based games rely fundamentally on the physical geographic displacement of the device.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAB	Ambient Sensors (Microphone/Sleep Tracking) : Titles utilizing local mobile hardware sensors (like breath input or sleep tracking) cannot be simulated and are critical to the core gameplay loop without workarounds.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAC	Kinetic Camera / AR Panoramas : Mechanics requiring the user to physically rotate their entire body in 360-degree real-world space to locate digital assets.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAD	Gyroscopic / Accelerometer Spatial Aiming: Games that rely on a gyro or accelerometer being present on the device to play the game, and would otherwise require a significant reworking of the user experience in order to support precision inputs.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAE	Intense Rapid Swiping and Multi-Touch Rhythm: Rhythm games (Music genre) demand simultaneous, synchronous actuation of multiple screen nodes, which a single mouse cursor cannot execute mathematically. Controllers lack the physical layout to map dynamic 6-to-8 lane rhythm charts intuitively.	❌ (необязательно)	❌ (необязательно)
LU-IC-EAF	Gestural Drawing / Freehand Vectors : Drawing specific geometric shapes or freehand paths is effectively impossible to replicate cleanly using the strict radial constraints of a controller thumbstick.	❌ (необязательно)	✅ (необходимый)
LU-IC-EAG	Drag-and-Drop / Absolute Point-and-Click : Executing rapid drag-and-drop mechanics with a relative radial thumbstick is kinetically unviable and vastly slower than absolute touch.	❌ (необязательно)	✅ (необходимый)

Дополнительные ресурсы

For more information about supporting precision inputs within your game, see Enable natural input on all form factors . When supporting controllers, make sure to add this flag to your manifest so that users can find your game when searching for controller-supported games in the store.

Form factor distribution

The Google Play Games platform is available across many different Android device form factors and players expect to play their games across them all.

ИДЕНТИФИКАТОР	Руководство
LU-FF-GAA	Your game must be distributed across the following Android form factors with exemplary quality: September 30, 2026 : Mobile , Foldables, and Tablets September 30, 2027 : Android XR , Android TV , Googlebook , and Android Auto

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-FF-EAA	Form factor constraints would meaningfully degrade a quality experience . Titles that have critical gameplay technical requirements that are not available on the form factor or where the form factor will create a meaningfully degraded player experience.

Например:

Gameplay mechanic	Form Factors exempt from distribution
Augmented reality and location-based games rely fundamentally on the physical geographic displacement of the device	Google Play Games on PC, Tablets, Googlebook, Android TV
Games utilizing local mobile hardware sensors (like breath input or sleep tracking) cannot be simulated and are critical to the core gameplay loop without workarounds.	Google Play Games on PC, Tablets, Googlebook, Android TV, Android Auto
Games with mechanics requiring the user to physically rotate their entire body in 360-degree real-world space to locate digital assets.	Google Play Games on PC, Googlebook, Android TV, Android Auto

ИДЕНТИФИКАТОР	Exemption
LU-FF-EAB	Devices with technical specifications below the minimum Mobile hardware requirements. Games are exempt from distribution on devices with hardware (RAM, CPU, storage, or GPU) or Android versions that fall below your minimum mobile phone requirements.
LU-FF-EAC	Form factor availability. Games are exempt from distribution on devices that are not available in any of the regions where the game is offered—meaning there is no overlap in regional availability between the device and the game.

Доступность названия

Players enjoy the flexibility of choosing their preferred devices while maintaining seamless access to their entire library of gaming experiences.

ИДЕНТИФИКАТОР	Руководство
LU-TA-GAA	For titles to be eligible for the program rate card benefits those titles must be released on Android supported form factors at the same time they become available on any other comparable, non-Android form factors from September 30th 2026 and moving forward.

Currently required Android supported form factors include:

• Mobile and Large Screen (Tablet, Googlebooks, PC)
• Android XR (with titles running in a 2D window on the XR device)
• Android TV
• Android Auto

Titles that do not meet this title availability guideline will become eligible for the Level Up program rate card benefits following a 6-month waiting period , once all user experience guidelines are fully met.

Examples :

• If a title is applying to be in the Level Up program and such title is currently available on other comparable non-Android form factors, such title must be launched on all comparable Android form factors for at least 6 months prior to enrollment into Level Up otherwise they will not be eligible for the program benefits until 6 months after the launch of their title on the Android form factor. The 6 month waiting period does not apply if the title was launched on the non-Android form factor prior to September 30th, 2026.
• If a title currently enrolled in the program launches a comparable non-Android form factor and does not launch on the comparable Android form factor simultaneously, they will become ineligible for program benefits for 6 months.

Исключения

The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-TA-EAA	Differences between device platforms. Not every game is technically or conceptually suited for every hardware configuration; therefore, the title will be exempt if the developer can demonstrate that a specific Android form factor's constraints would meaningfully degrade the user experience against the comparable non-Android platform or if there is no viable technical solution for that hardware.
LU-TA-EAB	Launch grace period. To account for unforeseen technical hurdles, store review delays, or "soft launches," we will implement the following: Standard grace period. Developers are granted a 15-day window to achieve "live" status on the Google Play Store. Extended grace period. In exceptional circumstances where a developer can demonstrate that the delay was caused by a Google-side technical issue or an unusually long app review process, the grace period may be extended to 30 days upon manual review.
LU-TA-EAC	EEA. This guideline does not apply in the EEA. However, when distributing to the EEA, Android users should be able to access all new experiences and capabilities within the Android title provided by the developer. Developers are therefore required to fully optimize their titles for Android.

Deliver stable and smoother gameplay sessions

To ensure games run beautifully across all form factors, we are introducing quality benchmarks that guarantee both performance and stability for players. All games must follow these user experience guidelines to provide a high quality experience to join the Level Up program.

Стабильность

Players expect their games to provide a stable experience on their device that is free of crashes and Android Not Responding (ANRs). Games need to meet the following quality thresholds. To reduce volatility, these thresholds will be enforced based on the trailing 28 days of data considering only devices within the approved set for which your app has at least 1,500 sessions in the last 28 days.

	LU-ST-GAA	LU-ST-GAB
Основные параметры Android	Test devices	4GB+ RAM Android Devices
Аварии	<1% average crash rate Check metrics in Play Console info	<2% average crash rate Check metrics in Play Console ) info
АНР	<2% average ANR rate Check metrics in Play Console info	<3% average ANR rate Check metrics in Play Console ) info

Исключения

There are no exemptions for this guideline.

Дополнительные ресурсы

For more information diagnosing and fixing vital issues, see Android vitals .

Производительность

A smooth and stable framerate is critical to delivering a high quality gaming experience on Android devices.

ИДЕНТИФИКАТОР	Руководство
LU-PR-GAA	On reference devices , active gameplay scenes must target and render at a minimum of 60 fps by default. This requirement specifically applies to real-time, active gameplay and excludes non-interactive or transitionary states such as loading/splash screens, content downloads, lobby interfaces, menus, and cinematic cutscenes: Average FPS ≥ 55 FPS Low 10% (P90) FPS ≥ 50 FPS Low 1% (P99) FPS ≥ 30 FPS

Исключения

Mobile games have to make many difficult decisions about what high quality means for their specific experience – such as whether to favor graphical fidelity or battery life during a play session. The following exemptions apply to this guideline:

ИДЕНТИФИКАТОР	Exemption
LU-PR-EAA	Games that do not support 60 FPS on other non-Android mobile platforms.
LU-PR-EAB	Games that use HWUI or Composer rather than rendering directly.
LU-PR-EAC	Games that only push new frames on player interaction , rather than on a continuously regular basis.
LU-PR-EAD	Games are not required to meet this on Tablet and Foldable devices due to their challenges in thermal design and computations to support high-resolution screens.

Дополнительные ресурсы

For additional details on calculating and measuring Level Up performance, see frame rate . You can also explore the slow sessions documentation for optimization strategies regarding frame smoothness.

Память

To deliver a premium experience, Android 17 introduced optimized memory handling and stricter platform requirements, which is accompanied by new, actionable memory telemetry in the Play Console.

Effective February 2027 , Play requires games to meet established bad-behavior thresholds for dynamic memory usage (anonymous RSS + swap), bitmap usage, and code optimization across all Android versions. Developers can now monitor these memory metrics and bad behavior thresholds within Android vitals .

ИДЕНТИФИКАТОР	Руководство
LU-MM-GAA	Once enforcement for these memory thresholds are in effect, games must comply with all memory thresholds to qualify for or maintain Level Up eligibility. You can find the memory thresholds and enforcement timeline here . Optimize your game : Follow the latest guidance for games to maximize memory savings across process states.

Исключения

There are no exemptions for this guideline.

Vulkan

Vulkan is Android's modern graphics API that offers significant improvements in performance and battery usage. It also offers new higher fidelity graphical techniques that will improve the gameplay experience on Android.

Older games might prefer to access Vulkan through ANGLE rather than converting their own code to Vulkan. ANGLE is Google's conformant OpenGL ES translation layer for Windows, Mac, Linux, iOS and Android. ANGLE uses Vulkan under the hood.

ИДЕНТИФИКАТОР

Руководство

LU-VK-GAA

On devices that have updated graphics drivers, where DEQP ≥ 20240301 : If you are using Unity version 2023 or newer , or Unreal Engine version 4.25 or newer : Vulkan must be set as the primary graphics API . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as it is <10% of frames. Games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path. If you are using an older version of Unity or Unreal, or any other game engine, then you are required to either use Vulkan or enable ANGLE rendering to meet this guideline. To opt-in to use ANGLE, modify your app's manifest file as follow: <application android:appCategory="game"> <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" /> </application>

Исключения

Our default stance is that all games should adopt Vulkan because it offers considerable performance and battery benefits. The following exception recognizes that some games might not have a choice on graphics API.

ИДЕНТИФИКАТОР	Exemption
LU-VK-EAA	Games that don't control their own rendering and render through HWUI/SKIA (similar to how apps render). These games have no control over their graphics pipeline, and will be moved to Vulkan automatically over the coming versions of Android.
LU-VK-EAB	If your game uses WebGPU as its rendering API. WebGPU is a new higher level language that uses Vulkan on newer devices and OpenGL ES on older devices. If for some reason WebGPU decides not to use Vulkan on a focus device, that is beyond the control of the developer. We're working on deploying the Vulkan backend on as many devices as possible as quickly as possible.
LU-VK-EAC	If a game has encountered a blocking issue with Vulkan, and they have reported it and had it accepted by the relevant code-maintainer (For example, a Game Engine, GPU-IP Vendor, or Google), then they may be granted an exemption for an appropriate period of time to find a work around or for the issue to be addressed.
LU-VK-EAD	A developer may be exempt from this requirement if they are able to reduce their CPU instruction count in a similar fashion to what Vulkan provides. Vulkan provides an approximate 30% reduction in CPU instruction count as compared to other solutions. If the developer can show a similar improvement with an alternative solution, then the use of Vulkan is not required.

Дополнительные ресурсы

For more information on upgrading your game's graphics APIs, see Vulkan .

Reference device list

The following devices are used to test our guidelines. Because Android hardware and features evolve, this list can be updated to ensure comprehensive coverage.

Список устройств

Год	System on a Chip продавец	System on a Chip модель	Производитель	Маркетинговое название	Форм-фактор
2026	GOOGLE	TENSOR G5	GOOGLE	PIXEL 10 PRO XL	ТЕЛЕФОН
				PIXEL 10 PRO FOLD	FOLDABLE
	MEDIATEK	MT6993	VIVO	X300	ТЕЛЕФОН
				X300 PRO	ТЕЛЕФОН
			OPPO	FIND X9 PRO	ТЕЛЕФОН
				FIND X9	ТЕЛЕФОН
	QTI	SM8845	ONEPLUS	ONEPLUS 15R	ТЕЛЕФОН
			ЛЕНОВО	MOTOROLA SIGNATURE	ТЕЛЕФОН
		SM8850	SAMSUNG	GALAXY S26 ULTRA	ТЕЛЕФОН
				GALAXY S26	ТЕЛЕФОН
				GALAXY S26+	ТЕЛЕФОН
			ONEPLUS	ONEPLUS 15	ТЕЛЕФОН
			OPPO	FIND N6	FOLDABLE
			СЯОМИ	СЯОМИ 17	ТЕЛЕФОН
				XIAOMI 17 ULTRA	ТЕЛЕФОН
				LEITZPHONE POWERED BY XIAOMI	ТЕЛЕФОН
				XIAOMI 17 PRO MAX	ТЕЛЕФОН
	SAMSUNG	S5E9965	SAMSUNG	GALAXY S26	ТЕЛЕФОН
				GALAXY S26+	ТЕЛЕФОН
2025	GOOGLE	TENSOR G4	GOOGLE	PIXEL 9 PRO XL	ТЕЛЕФОН
				PIXEL 9 PRO FOLD	FOLDABLE
	MEDIATEK	MT6991	СЯОМИ	XIAOMI 15T PRO	ТЕЛЕФОН
			SAMSUNG	GALAXY TAB S11	ПЛАНШЕТ
				GALAXY TAB S11 ULTRA	ПЛАНШЕТ
				GALAXY TAB S11 ULTRA 5G	ПЛАНШЕТ
				GALAXY TAB S11 5G	ПЛАНШЕТ
			VIVO	VIVO X200	ТЕЛЕФОН
				X200 PRO	ТЕЛЕФОН
				X200T	ТЕЛЕФОН
			OPPO	FIND X8	ТЕЛЕФОН
				FIND X8 PRO	ТЕЛЕФОН
	QTI	SM8735	СЯОМИ	XIAOMI PAD 8	ПЛАНШЕТ
		SM8750	SAMSUNG	GALAXY S25 ULTRA	ТЕЛЕФОН
				ГАЛАКСИЯ S25	ТЕЛЕФОН
				GALAXY S25+	ТЕЛЕФОН
				GALAXY S25 EDGE	ТЕЛЕФОН
				GALAXY Z FOLD7	FOLDABLE
			ONEPLUS	ONEPLUS 13	ТЕЛЕФОН
				ONEPLUS 13S	ТЕЛЕФОН
				PAD 3	ПЛАНШЕТ
			OPPO	FIND N5	FOLDABLE
			СЯОМИ	XIAOMI 15	ТЕЛЕФОН
				XIAOMI 15 ULTRA	ТЕЛЕФОН
			СОНИ	XPERIA 1 VII	ТЕЛЕФОН
			VIVO	IQOO 13	ТЕЛЕФОН

Comprehensive testing across every specific model may not be required because several devices in the list use identical SoCs and exhibit comparable performance. Developers are eligible to self-certify for the guidelines once they have successfully verified requirements on at least one device from each listed SoCs:

Телефоны

Год	System on a Chip	Устройства
2026	Тензор G5	PIXEL 10 PRO XL
2025	Tensor G4	PIXEL 9 PRO XL
2026	MTK MT6993	X300, FIND X9
2025	MTK MT6991	XIAOMI 15T PRO, GALAXY TAB S11, VIVO X200, FIND X8
2026	QCOM SM8845/8850	ONEPLUS 15R, MOTOROLA SIGNATURE, GALAXY S26, ONEPLUS 15, XIAOMI 17
2025	QCOM SM8750	GALAXY S25, ONEPLUS 13, PAD 3, XIAOMI 15. XPERIA 1 VII, IQOO 13
2026	Exynos S5E9965	GALAXY S26

Планшет

Год	System on a Chip	Устройства
2025	MTK MT6991	GALAXY TAB S11
2025	QCOM SM8735	XIAOMI PAD 8
2025	QCOM SM8750	OPPO PAD 3

Контроллеры

For controllers, make sure to test your game with the following as it covers the common styles of controllers supported on the platform today:

• Беспроводной контроллер Sony DualSense
• XBox Wireless Controller
• Nintendo Switch Pro Controller (note: This is for the original Switch console)

We recommend using the testing guidance here for more details.

Примечания к изменениям

Сентябрь 2026 г.

• Производительность

  • Guidelines updated: LU-PF-GAA

  • Previous text:

    Games that do not support 60 FPS on other platforms.

  • New text:

    Games that do not support 60 FPS on other non-Android mobile platforms.

• Large screen optimization

  • Guidelines updated: LU-LS-GAA , LU-LS-GAB LU-LS-GAC , LU-LS-GAD

  • Previous text:

    • Handle system bars , display cutouts , and configuration changes —such as device rotation and window resizing—to prevent crashes and visual artifacts. Ensure all UI and gameplay elements remain visible and interactive, avoiding any obstructions that block player input, while correctly maintaining or restoring the game state.

    • Games in a landscape layout need to be full screen, without letterboxing or pillarboxing, at the aspect ratios for each reference device and also at the anchor aspect ratios of 4:3, 16:10, and 21:9.

    • Games in a portrait layout similarly need to support the complement aspect ratios. For example, for the anchor ratios the equivalent is 3:4, 10:16, and 9:21.

    • Games are able to letterbox or pillar box themselves under the following conditions:

      • On a device with an aspect ratio that is not found on a flagship device or outside one of the anchor aspect ratios defined previously.
      • If the only game layout orientation (portrait or landscape) is different from the device's physical orientation.

  • New text:

    • Use insets to prevent blocking game controls or UIs that overlap with system bars (status, navigation, gesture) or display cutouts (notches, punch holes).

    • Support configuration changes (device rotation, fold/unfold, multi-window split, freeform window resizing) without crashes, ANRs, visual artifacts, or touch mapping offsets, while preserving active game state and progress.

    • Games displayed in landscape must render full screen without letterboxing or pillarboxing on Reference Devices and anchor ratios of 4:3, 16:10, and 21:9. Landscape-only games are not required to support a portrait layout, but must cleanly letterbox or pillarbox themselves on portrait displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.

    • Games displayed in portrait must render full screen without letterboxing or pillarboxing on reference devices and anchor ratios of 3:4, 10:16, and 9:21.Portrait-only games are not required to support a landscape layout, but must cleanly letterbox or pillarbox themselves on landscape displays. Out-of-anchor ratios may also be letterboxed or pillarboxed.

• Google Play Games on PC

  • Guidelines updated: LU-GPGC-GAA

  • Previous text:

    Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC .

    • Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution.
    • OR, Your game is part of the Native PC Early Access Program (EAP) .

  • New text:

    Your game must be distributed on Google Play Games on PC . There are two ways to meet this distribution requirement: Your mobile game meets the playability requirements when played on the Android emulator Google Play Games for PC .

    • Ensure all unsupported Android features and permissions are not marked as required to ensure proper distribution.
    • OR, Your game is published as a Native PC game on Google Play Games and integrates with the PC SDK ^* .

    ^* If you publish as a Native PC Game, your title won't need to support Sidekick, Cloud Save, Achievements, and Game Stats API for the PC version until those features become available in the Google Play Games on PC SDK.

• Precision input controls

  • New text:

• Form factor distribution

  • Guideline updated: LU-FF-GAA

  • Previous text:

    • September 2026 : Mobile , Foldables, and Tablets
    • March 1, 2027 : Googlebook
    • September 2027 : Android XR , Android TV , and Android Auto

  • New text:

    • September 2026 : Mobile , Foldables, and Tablets
    • September 2027 : Android XR , Android TV , Googlebook , and Android Auto

• Vulkan

  • Guideline updated: LU-VK-GAA
  • Previous text:
  • Vulkan must be set as the primary graphics API if you are using Unity version 2021 or newer , or Unreal Engine version 4.25 or newer . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as it is <10% of frames.
  • Instead of using Vulkan directly, games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path.

  • All other games can decide to either use Vulkan as the primary graphics API or opt-in to using ANGLE for Android 17+ devices. To opt in to use ANGLE modify the app's manifest file as follows:

    <application android:appCategory="game">
    <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" />
    </application>
    

  • New text:

  • If you are using Unity version 2023 or newer , or Unreal Engine version 4.25 or newer :

  • Vulkan must be set as the primary graphics API . Minor OpenGL ES usage (For example, for Adverts, webviews, etc) is acceptable as long as its <10% of frames.

  • Games using Unity's Built-in Render Pipeline may opt-in to using ANGLE for Android 17+ devices. These games have until September 30, 2027 to set Vulkan as the primary graphics API. Transitioning to Unity's Universal Render Pipeline is highly recommended to achieve this but is not the only permissible path.

  • If you are using an older version of Unity or Unreal, or any other game engine, then you are required to either use Vulkan or enable ANGLE rendering to meet this guideline. To opt-in to use ANGLE, modify your app's manifest file as follow:

    <application android:appCategory="game">
    <meta-data android:name="com.android.graphics.driver.prefer_angle" android:value="true" />
    </application>
    

• Память

  • Guidelines updated: LU-MM-GAA

  • Previous text:

    To deliver a premium experience, Android 17 is introducing optimized memory handling and stricter platform requirements later this year–accompanied by new, actionable memory telemetry in the Play Console. Because meeting these standard memory limits will be required for Level Up, we strongly encourage [implementing these memory optimization strategies][bbb] early to ensure app stability and a great user experience. More detailed compliance criteria to maintain your program status will be shared in the coming months.

  • New text:

    To deliver a premium experience, Android 17 introduced optimized memory handling and stricter platform requirements, which is accompanied by new, actionable memory telemetry in the Play Console.

    Effective February 2027 , Play requires games to meet established bad-behavior thresholds for dynamic memory usage (anonymous RSS + swap), bitmap usage, and code optimization across all Android versions. Developers can now monitor these memory metrics and bad behavior thresholds within Android vitals .

    Once enforcement for these memory thresholds are in effect, games must comply with all memory thresholds to qualify for or maintain Level Up eligibility. You can find the memory thresholds and enforcement timeline here .

    Optimize your game : Follow the latest guidance for games to maximize memory savings across process states.

Июль 2026 г.

• Статистика игры
  • Guidelines updated: LU-GS-GAA
  • Exemption updated: LU-GS-EAC
  • Previous text:
    • Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All stats need to represent regularly occurring actions by players in the game.
    • At least 1 stat needs to be usable for competitive player engagement features.
    • Stats should not require a purchase (For example, buy gems).
    • Stats should not require watching advertisements.
    • Stats should not be generic use of the game (For example, open the game; use settings).
    • Stats should be available to all users (For example, not a team-specific action).
  • New text:
    • Submit at least 5 repetitive stats to power the Game Stats feature stored against the player's gamer profile. All repetitive stats need to represent regularly occurring actions by players in the game.
      • At least 1 stat needs to be usable for competitive player engagement features.
    • Exemption: Titles on Native PC Early Access Program (EAP), given our SDK doesn't support this feature yet. (Note: This only applies to the Native PC version of your title).