> 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/app-updater/playmaker/use-cases.md).

# Use Cases

Quick-start guides for checking app updates and prompting updates using PlayMaker custom actions.

## Available Use Cases

### 1. [Request Update Info And Prompt](/features/app-updater/playmaker/use-cases/use-case-1-request-update-info-and-prompt.md)

* **What it does:** End-to-end flow: check update status and (optionally) prompt the user to update
* **Actions:** 3 (`AppUpdaterRequestUpdateInfo`, `AppUpdaterGetRequestUpdateInfoSuccessResult`, `AppUpdaterPromptUpdate`)

### 2. [Silent Policy Check](/features/app-updater/playmaker/use-cases/use-case-2-silent-policy-check.md)

* **What it does:** Check for updates periodically without blocking UI
* **Actions:** 2 (`AppUpdaterRequestUpdateInfo`, `AppUpdaterGetRequestUpdateInfoSuccessResult`)

### 3. [Prompt Update (Manual Trigger)](/features/app-updater/playmaker/use-cases/use-case-3-prompt-update.md)

* **What it does:** Trigger a store update prompt from a settings/help screen
* **Actions:** 1 (`AppUpdaterPromptUpdate`)

## Quick Action Reference

| Action                                      | Purpose                                 |
| ------------------------------------------- | --------------------------------------- |
| AppUpdaterRequestUpdateInfo                 | Request update status (cached)          |
| AppUpdaterGetRequestUpdateInfoSuccessResult | Read cached update status after success |
| AppUpdaterGetRequestUpdateInfoError         | Read cached error after request failure |
| AppUpdaterPromptUpdate                      | Show native update prompt / flow        |
| AppUpdaterGetPromptUpdateProgress           | Read cached progress (Android only)     |
| AppUpdaterGetPromptUpdateError              | Read cached error after prompt failure  |

## Output Variables

| Variable     | Type                          | Description                                                |
| ------------ | ----------------------------- | ---------------------------------------------------------- |
| updateStatus | Enum (AppUpdaterUpdateStatus) | `Available` / `NotAvailable` / `InProgress` / `Downloaded` |
| progress     | Float (0..1)                  | PromptUpdate progress (Android only)                       |

## Best Practices

* Check once per day maximum
* Show forced updates immediately
* Allow users to dismiss optional updates
* Track last check time in PlayerPrefs
* Don't interrupt critical user flows
* Test update flows with TestFlight/internal testing

## Platform Support

* **iOS**: App Store version checking
* **Android**: Google Play Store version checking
* Both platforms require network connection

## Related Documentation

* [**README.md**](/features/app-updater/playmaker.md)


---

# 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/app-updater/playmaker/use-cases.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.