In order to ensure that players have a high quality experience on Google Play Games on PC, you have to pass two sets of tests before your game can be published. You must pass these test in order:
Milestone 1: Functional Testing where we verify that the build meets baseline requirements.
Milestone 2: Quality Testing where our playtesting team verifies that the game can be played.
Use this checklist to verify that you've completed all the necessary steps before submitting a build to ensure a quick approval process.
Milestone 1 Requirements
The goal of this milestone is to verify that the build works, the core technical requirements are met, and the game is ready to be played on a PC with a keyboard and mouse. Feedback typically takes 2-3 business days.
Here's the requirements for this milestone:
- Platform Requirements
- PC Compatibility
- Display and Visual Assets
- Use high resolution assets and textures on PC
- Support PC-specific aspect ratios
- Scale UI elements appropriately for a larger screen
- Render at 60Hz
- Audio playback is smooth and in sync
- Google Play Games Services sign in and game sync for the PC
Milestone 2 Requirements
The goal of this milestone is to ensure playability of your game on a PC, taking into account common points of user friction and negative feedback. Your build must pass Milestone 1 before proceeding to Milestone 2. Builds submitted for Milestone 2 testing should be considered ready to launch.
Feedback on a build typically takes 2-3 business days, and will include feedback as follows:
- Mandatory: Feedback must be addressed before the game can move to
production. Examples include (this is not a complete list):
- Game updates do not work and the game cannot be played
- Crashes, visual artifacts, or other obvious bugs during gameplay
- Keyboard or mouse controls are incomplete and result in obviously negative or unplayable user experience
- Significant performance issues
- Recommendation: We will not launch the game until you review this feedback
and confirm that you want to launch. While this feedback is non-blocking, you
may want to address these issues before moving the game to production. Generally
speaking, recommendations anticipate common causes of negative user sentiment.
Examples include (this is not a complete list):
- Keyboard or mouse controls are incomplete and result in noticeable user friction, but where the game is still playable
- Mobile controls still appear on-screen, but the game is still playable
- Suggestion: Non-blocking concerns, which will not delay your game's launch. This generally captures all other impressions which might affect user sentiment.
Here's the requirements for this milestone:
- Playtesting feedback
- Address all blocking issues
- Acknowledge all strong recommendations
- Cross-Platform Play
- The production version of your mobile build must use Google Play Games Services V2.