> For the complete documentation index, see [llms.txt](https://docs.appstoremanager.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appstoremanager.net/documents/readme/overview.md).

# Overview

**App Store Manager** is a service layer on top of Apple App Store Connect and Google Play Console. It simplifies store listing maintenance by providing bulk operations that the stores themselves don't offer.

```mermaid
flowchart LR
    ASM[App Store Manager] --> Import[Bulk Import]
    ASM --> Translate[Translate]
    ASM --> Validate[Validate]
    ASM --> Upload[Batch Upload]

    Upload --> iOS[App Store Connect]
    Upload --> Android[Google Play Console]

    style ASM fill:#FF9800,color:#fff
    style Import fill:#9C27B0,color:#fff
    style Translate fill:#9C27B0,color:#fff
    style Validate fill:#9C27B0,color:#fff
    style Upload fill:#9C27B0,color:#fff
    style iOS fill:#007AFF,color:#fff
    style Android fill:#34A853,color:#fff
```

***

## What You Can Do

### Bulk Import Content

Import all your store listing content at once:

| Content Type     | Examples                                                 |
| ---------------- | -------------------------------------------------------- |
| **Descriptions** | Title, subtitle, keywords, short & long descriptions     |
| **Assets**       | Screenshots, app preview videos, icons, feature graphics |

Import methods:

* **From file** — Excel or JSON templates
* **From store** — Pull existing content from your live listings
* **Drag & drop** — Drop folders of screenshots directly into the manager

### Batch Upload

Upload everything to the stores in one operation — all languages, all assets, one click.

{% hint style="success" %}
What takes hours in the store consoles takes minutes with App Store Manager.
{% endhint %}

***

## Quick Start

1. **Create an app** — Link your App Store or Play Console app
2. **Create a store listing** — Container for your metadata and assets
3. **Add content** — Import, drag & drop, or type directly
4. **Upload** — Push everything to the stores

{% hint style="info" %}
Translation and validation features are available but optional. You can import ready-to-go content and upload immediately.
{% endhint %}

***

## Next Steps

* [Use cases](/documents/readme/use-cases.md) — Common workflows and scenarios
* [Detailed walkthrough](/documents/readme/how-to-work-with-the-app-store-manager.md) — Step-by-step guide
* [App Store Connect access](/documents/access/app-store-connect-access.md)
* [Google Play Console access](/documents/access/google-play-console-access.md)

Need help? [Contact us](https://www.iwantanelephant.com/contact/)


---

# 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://docs.appstoremanager.net/documents/readme/overview.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.
