1.0.1

General

RuStore In-app Review SDK prompts the user to rate your app and leave feedback on RuStore without exiting the app.

Rating and feedback user scenarios may be run at any time throughout the user’s path in your app. The user can rate your app from 1 to 5 and leave feedback. Feedback is optional.

Implementation example

Check out the application example to learn how to properly integrate the Feedback SDK.

User scenario example

Prerequisites

For rating and feedback SDK to operate correctly, the following conditions need to be met:

• Android 7.0 or later..
• The current version of RuStore is installed on the user's device.
• The user is authorized in RuStore.
• The app must be published in RuStore.

When to ask for feedback

Use the tips below to decide when to ask the user to rate and leave feedback: (See below

• Start the process once the user has been using your app for long enough.

• Avoid starting it too often as this will impair your app’s user experience and limit the use or SDK ratings.

• Avoid using calls to action like “Rate App” button as the user could have already reached the process starting limit.

• Your app should not ask the user any questions before the start or while the process is running, including their opinion (“Do you like the app?”) or predictive questions (“Would you give this app 5 stars?”).

Design recommendations

Use the tips below to decide how to integrate the process:

• Display the process as is, without any intervention or modification of existing design, including size, opacity, shape and other properties.

• Add nothing on top or on sides of the process.

• The process should open on top of all layers. Don’t close the process after starting. The process will close by itself after an express action by the user.

Connecting to project

1. Copy the plugin and the sample app projects from the official RuStore repository into the GitFlic directory.
2. Open the Android project from the extension_libraries folder in your IDE.
3. Build the project via gradle assemble command. If the build is successful, files will be created in the review_example/extension_rustore_review/lib/android and review_example/extension_rustore_core/lib/android folders:
   • RuStoreDefoldReview.jar;
   • RuStoreDefoldCore.jar.
4. Copy the folders review_example/extension_rustore_review and review_example/extension_rustore_core to the root of your project.

Working with user ratings

Getting started with user ratings

Before calling library methods, you must initialise the library. Use the init() method for initialisation.

Вызов метода init

function init(self)
    rustorereview.init()
end

Preparing to launch app evaluation

Call request_review_flow in advance before calling launch_review_flow, to prepare necessary information to display. ReviewInfo has a lifetime — about five minutes.

You must subscribe to events once before using this method:

• on_request_review_flow_success;
• on_request_review_flow_failure.

Подписка на события

function init(self)
    rustorecore.connect("rustore_request_review_flow_success", _request_review_flow_success)
    rustorecore.connect("rustore_request_review_flow_failure", _request_review_flow_failure)

    -- Initialisation of rustorereview
end

function _request_review_flow_success(self, channel, value)

end

function _request_review_flow_failure(self, channel, value)
    local data = json.decode(value)
end

Вызов метода request_review_flow

rustorereview.request_review_flow()

The rustore_request_review_flow_failure callback returns a JSON string with error information. The error structure is described in Error Handling.

info

List of possible errors

Launching app evaluation

To run the feedback form in your app, call the launch_review_flow() method using the previously obtained ReviewInfo.

You must subscribe to events once before using this method:

• on_request_review_flow_success;
• on_request_review_flow_failure.

Подписка на события

function init(self)
    rustorecore.connect("rustore_launch_review_flow_success", _launch_review_flow_success)
    rustorecore.connect("rustore_launch_review_flow_failure", _launch_review_flow_failure)

    -- Initialisation of rustorereview
end

func _launch_review_flow_success(self, channel, value)

end

func _launch_review_flow_failure(self, channel, value)
    local data = json.decode(value)
end

Вызов метода launch_review_flow

rustorereview.launch_review_flow()

Await notification that the user has completed the form in rustore_launch_review_flow_success or rustore_launch_review_flow_failure to proceed with the application.

The rustore_launch_review_flow_failurecallback returns a JSON string with error information. The error structure is described in Error Handling.

After completing the feedback form, regardless of the outcome (success or failure), it is not recommended to display any additional forms related to assessment and feedback. If called frequently, launch_review_flow() will not display the feedback window to the user, as the allowed display is regulated by RuStore.

info

List of possible errors

Errors processing

The errors that occur can be retrieved in the events *_failure.

Error structure

Обработка json ошибки

function _on_failure(self, channel, value)
    local data = json.decode(value)
	
	local message = data.detailMessage
end

• detailMessage – error description.

Possible errors

• RuStoreNotInstalledException — RuStore not installed on user's device;
• RuStoreOutdatedException — RuStore, installed on the user's device, does not support payment processing functions.;
• RuStoreUserUnauthorizedException — user not authorized on RuStore;
• RuStoreRequestLimitReached — not enough time has passed since the process was last shown.;
• RuStoreReviewExists — this user has already rated your app.;
• RuStoreInvalidReviewInfo — problems with ReviewInfo;
• RuStoreException — basic RuStore error, from which all other errors are inherited..