A typical Android mobile or tablet device has the following buttons:

Each button has its own functionality based on the Android standard. It is always a good practice to use these buttons for the exact same functionality in the game.

For example, pressing the Back button should take the user to the previous screen or previous state of the game. The most common use of the Back button for in-game play is to pause the game cycle. Similarly, the Volume up/down button should have a direct effect on the game sound in line with the native functionality.

It is always a good practice to implement basic Android functionalities and use Android-specific features for an Android game. We just spoke about using the device buttons for Android devices.

From the features point of view, the Android standard features support killing the game application from the game itself. Unlike iOS, an Android game can be quit.

It is a common practice for users to not always quit the gameplay in a conventional way. Rather, Home buttons are used to quickly get out of the game. In that case, the game goes to the background and keeps on running unless the user resumes it or the OS kills the process. The longer it can stay in the background, the quicker the game can be resumed.

Mainly, using low memory and low process overhead can increase the time the game persists in the background. A few times there might be several interrupts. In this case, it is a best practice to resume to the same state for a better user experience.

Although Android is an open source platform, Google has some guidelines for Android applications; these are also applicable to games. It is obvious that the Google Play Store is the biggest platform to reach a global audience in the current market scenario. So, it is always a wise decision to follow their guidelines to get featured.

There are several millions of applications available on the Google Play Store. Without getting featured, it is very difficult to attract users to a particular game or application.