> For the complete documentation index, see [llms.txt](https://help.twinr.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.twinr.dev/native-integrations/overview-1/app-review.md).

# App Review

Ask happy users to rate your app in the store.

App Review prompts your customers to rate your app, using the rating box Apple and Google provide. The rating goes straight to your store listing without the customer leaving your app.

{% hint style="info" %}
App Review is a **Premium** feature.
{% endhint %}

Ratings matter more than most merchants expect. They are one of the inputs both stores use to rank search results, and they are the first thing someone comparing two apps looks at.

## Turn it on

Open **Native Features → App Review** and switch it on.

<figure><img src="https://3731994945-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MlBy5z08zL1UoCwNqmg%2Fuploads%2Fgit-blob-52464f84416daaa776a66ff9591e9f81b6e3377a%2Fnf-in-app-review.png?alt=media" alt="The App Review screen with its enable toggle and schedule field"><figcaption></figcaption></figure>

**App Review Schedule** decides when the prompt appears, counted in app opens since the customer installed. Enter the numbers separated by commas — `10, 60, 100` prompts on their 10th, 60th and 100th open.

Click **Save as draft**.

## The 30-day rule

{% hint style="warning" %}
Apple and Google both cap review prompts at **once per month, per customer**. Twinr honours that, so schedule entries falling inside a 30-day window are skipped.

A schedule of `1, 5, 10, 15, 35, 50` on a customer who opens the app daily prompts on day 1 and day 35. Everything in between is silently dropped.
{% endhint %}

Leave at least 30 opens between entries for daily users, and more if customers open your app less often.

## Choosing your moments

Ask when someone has just had a good experience — after an order, a completed booking, a finished course. Asking during checkout or after an error gets you one-star ratings.

Avoid the first few opens. Someone who has used your app twice has nothing to say yet.

## Asking at a specific moment

The schedule counts app opens, which is blunt. To ask at a moment that actually means something, call the bridge function from your own site:

```javascript
await twinr_request_app_review()
```

Call it when an order completes, a course finishes, or a booking is confirmed. The 30-day cap still applies, so a customer who has been asked recently will not see it again.

You can also wire this to a navigation bar button — see [Custom Button](https://help.twinr.dev/navigation-bar-buttons/custom-button.md).

## Check it

In Twinr Preview you can see the prompt appear, but any rating you give goes to the Twinr Preview listing, not yours. Real behaviour on your own schedule can only be seen once your app is live.

## Common Questions

<details>

<summary>What are Apple's and Google's rules?</summary>

[Google's in-app review quotas](https://developer.android.com/guide/playcore/in-app-review#quotas) and [Apple's ratings and reviews guidance](https://developer.apple.com/design/human-interface-guidelines/patterns/ratings-and-reviews/).

</details>
