> For the complete documentation index, see [llms.txt](https://docs.bravostudio.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bravostudio.app/app-publication/publication-app-rating-alert.md).

# App rating alert

Ask your users to rate your app! The rating alert will allow you to collect feedback and ratings to be displayed in your app store listing.

![](https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fdocs%2F-MfmszQtVly6h8qOHICS%2F-MfmtA05jsxCfotoeZDE%2FFrame_168.png?generation=1627572711822714\&alt=media)

## 🤔 How does it work?

1. Publish your app.
2. If your app is already published, you need to upload a new build.
3. The rating alert will appear the 3rd time a user opens your app. This feature is automatically integrated into all published apps, no extra configuration needed!

![Rating alert in iOS (using Bravo Vision as an example)](https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fdocs%2F-MfmszQtVly6h8qOHICS%2F-MfmtA07h0CmCByzYruc%2Fios-rating.png?generation=1627572711833287\&alt=media)

![Rating alert in Android (using Bravo Vision as an example)](https://1444025092-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2Fdocs%2F-MfmszQtVly6h8qOHICS%2F-MfmtA06MwnQgAWiLf0E%2FFrame_170.png?generation=1627572711836797\&alt=media)

That's it! 🥳


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.bravostudio.app/app-publication/publication-app-rating-alert.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.