# Rejection from the app stores

Bravo cannot guarantee your app will be accepted by the app stores if they detect anything that goes against their guidelines.

We recommend that you look over the app guidelines **before** submitting your app (or after you have been rejected):

🤖 [Google Play Guidelines](https://play.google.com/about/developer-content-policy/)\
🍏 [App Store Review Guidelines](https://developer.apple.com/app-store/review/guidelines/)

## App Store Guidelines highlights

* [Minimum Functionality](https://developer.apple.com/app-store/review/guidelines/#minimum-functionality): while there is no clear specification as to what is minimum functionality, try adding more native functions (things you cannot do on a website, functionalities that can only be used on mobiles) into your app to make it more "app-like" if you get rejected for this reason.
* In case your app is rejected due to "Guideline 5.1.1 - Legal - Privacy - Data Collection and Storage", ensure that you provide account-specific functionality when you require user login before using the app.
* Apple does not allow selling digital goods with out using its in-app purchase platform.
* You cannot change the functionality of the app after it has been reviewed. This will also be a cause for rejection.
* In case Apple asks to enable "Sign in with Apple", you will need to add it to your design, generate a new build and submit again to the Apple store.

That's it! 🚀


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.bravostudio.app/app-publication/publishing-your-app/publication-rejection-from-the-app-stores.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.