> For the complete documentation index, see [llms.txt](https://assetstore.essentialkit.voxelbusters.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://assetstore.essentialkit.voxelbusters.com/features/utilities/playmaker/use-cases/use-case-1-app-store-review.md).

# Prompt for App Store Review

## Goal

Open the app store page for your app to encourage users to leave ratings and reviews.

## Actions Required

| Action                           | Purpose                                 |
| -------------------------------- | --------------------------------------- |
| UtilitiesOpenAppStorePageDefault | Opens app store using configured app ID |

## Variables Needed

None required (uses Essential Kit Settings)

## Implementation Steps

### 1. State: OpenAppStore

**Action:** UtilitiesOpenAppStorePageDefault

**Note:** The app will suspend and the App Store will open. Users can return via multitasking.

## Configuration Required

In Essential Kit Settings, configure:

* **iOS**: Set App Store ID (numeric, e.g., "1234567890")
* **Android**: Set Package Name (e.g., "com.yourcompany.yourapp")

## Common Issues

* **App Store doesn't open**: Verify app IDs are correctly configured in Essential Kit Settings
* **Wrong app opens**: Check that platform-specific app IDs match your published app
* **Action fails in Editor**: App Store links only work on device (iOS/Android)

## Flow Diagram

```
OpenAppStore
    └─ App Store opens, app suspends
```

## Best Practices

* Prompt after positive experiences (level completion, achievement unlocked)
* Don't show too frequently (once per version, or after significant milestones)
* Use a friendly message before opening: "Enjoying the game? Rate us!"


---

# 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 dynamically by asking a question.

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

```
GET https://assetstore.essentialkit.voxelbusters.com/features/utilities/playmaker/use-cases/use-case-1-app-store-review.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.