The In-App Review API (Application Programming Interface) is a new featured application for Android users to review and rate an application while using it. The main thing is the users don’t need to leave the app and rate or review in the play store which can be displayed later after. This is a user-friendly application that does not have the risk of leaving the application to review in the play store and not coming back. This helps you get the exact review of how the users are feeling using the application. You can check and see this page for readymade swiggy android application source code.
The android version you are using should be 0.5 or higher and the app with which you are integrating should be 1.8.0 or higher than that. And I’m your device, the play store should be installed.
Quotas of In-App Review API
The review option of In-App Review appears in a gap of time. Like monthly. So users can experience a good time-bound widget displaying on their Android phone. But while using the launch review method, the dialog may not always display. Once the user is done with the quota of that time, the dialog box won’t appear again. In that case, if you request the review, think about the time it needs. Because the request will directly take the user to the play store and you’ll leave the currently used application. To request a review, you can click on the call to action option which can be a button. But you need not do that because as the user quota is over, it’s unnecessary to have a broken experience of using one application and jumping to another. The API controls the review option and does not reveal whether a user has made any reviews and ratings or not and whether the widget has appeared or not.
Guidelines of the In-App Review API
Without tampering with the card and its designs it can be modified by its size, shape, properties or opacity. But you can not include any overlay on or around the card. This card should be set at the topmost layer. But when a card is surfaced on the layer do not try to remove it. The play store’s mechanism or user action leads the card to be removed automatically.
Best time to ask for a review
When a user has earned enough experience using an application or game, you can ask only then for the review to fill by the user. Do not avail options of reviews to choose from or do not guide users. This can lead them to limit their reviews and you can not get a clear opinion about the application you are seeking reviews for. Also, do not ask for supporting opinions while they are rating. Like, why did you choose this rating?
Integration in-app review API
Firstly you have to add a library in the app’s Gradle as this is a play core API. You can also add a fallback dialog to check the errors. Then the review manager interface is created. Then call the request review flow to return the review info successfully. Then to start the review flow, it needs to launch the review flow via using review info. If the request review fails, you can also generate a request review app dialog which directly takes you to the play store. To start the in-app review flow show rate app method is needed. If the request review flow comes in error, it needs to show the rate app fallback dialog method. This method takes the users directly to the play store using three options.
Testing the In-App Review
For internal app sharing and internal testing, you should have the approval of the app sharing and internal testing. You can use the in-app review flow and release the app to use an internal test track.
Primary rules for In-App Review API
The basic fundamental rule of in-app review API is not to ask users twice to rate or review the in-app flow. How many times the user is getting the in-app review dialog, is called a quota. The quota is determined by the Google play store. And the restriction is the quota must be limited because the user should not get disturbed. While using an app loads of review requests are coming, which can ruin the users’ experience of using the app. Also, you can not make the user leave and review and rate the app from the play store. Remember you should maintain the comfort and convenience of the users, otherwise, they will not properly utilize In-App Review API.
Learn to identify the happy mobile moments which are important for In-App review
Happy mobile hours mean a good amount of time spent on an app. This is a very crucial time to target a user using an application. But spending time is not enough to send review dialogs. Whether the user is happily engaged or got stuck in a bad situation needs to be identified. By using Apxor, it can easily track the movement of the user. After a few rounds of scrolling, the in-app review API can be sent to the user asking for reviews and ratings to make sure that the user is actively using the app. You can check and see this page for swiggy android application source code.
About The Author:-
Hermit Chawla is an MD at AIS Technolabs which is a Web/App design and Development Company, that helps global businesses to grow through Global Clients. He loves to share his thoughts on Web & App Development, Clone App Development, and Game Development.