Authorization
Item 1.2 of the Game Requirements
You can launch and use the game without registration or logging in to third-party services. You can only log in with your Yandex ID, which can be requested via the Yandex Games SDK.
-
Authorization happens only after a deliberate action by the user — pressing a special button inside the game. The authorization prompt states what benefits it provides.
-
Guest login or the ability to play without authorization is implemented. The player's progress is saved in this case.
Adding Authorization
1.2. You don't have to be registered or logged in to third-party services to launch and use the SDK. You can log in with your Yandex ID.
Why it matters: Without mandatory registration or authorization, a user can start playing faster, and the game will begin generating revenue sooner. Moreover, such games have a lower entry threshold, meaning they can attract more users.
If you have added authorization to your game, follow these rules:
-
A user can play without registering or logging in.
-
Authorization can only be through Yandex ID.
-
The message that offers authorization explains the benefits it provides to the user.
-
The game does not offer authorization:
- through third-party services;
- if the user is already logged into an account.
Examples
|
Correct |
Incorrect |
|
Basic functions are available without authorization. |
Entry or play is only possible after authorization. |
|
If there is an offer to authorize in the game, it leads to Yandex ID. |
There is an offer to authorize through third-party services in the game. |
|
It is possible to decline authorization and continue playing. |
There is no option to decline authorization, or the offer is aggressively and frequently shown in the game. |
|
After logging into an account, the game no longer shows the authorization offer. |
After logging into an account, the game continues to show the authorization offer. |
Authorization Offer
1.2.1. You'll only be authorized after you perform a voluntary action.
Authorization should be predictable to not disturb the user or cause dissatisfaction. In addition, the user should have information about the benefits they will receive from authorizing.
To make authorization comfortable for the user, follow these rules:
- Transition to the authorization page occurs only if the user has deliberately chosen this action (for example, by clicking a button labeled "Authorize").
- The offer to authorize is displayed with an explanation of the advantages the user will have, for example:
- Saving progress in the cloud.
- Notifications about new products and promotions.
- In-app purchases — items and upgrades purchased will be available in any browser, not just the current one.
- The user can decline authorization and continue playing.
Examples
|
Correct |
Incorrect |
|
Transition to authorization occurs upon pressing an element, which outwardly appears to lead to the authorization page. |
The authorization page opens upon pressing buttons that are not related to authorization, for example, Leaderboard or Rate the Game. |
|
The authorization window includes information about the benefits of logging into the account. |
The authorization offer window lacks information about the benefits of authorization. |
|
There is an option to decline authorization and continue playing. |
There is no option to decline authorization. |