> For the complete documentation index, see [llms.txt](https://docs.appmysite.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmysite.com/pricing/developer-accounts-cost.md).

# Developer accounts cost

### Do your plans include the cost of creating developer accounts on the Google Play Store and the Apple App Store?

No, the cost of creating developer accounts on the app stores is not included in your AppMySite subscription. However, there are no hidden charges or extra taxes within our plans, everything offered is clearly outlined on our [**pricing page**](https://www.appmysite.com/in/custom-app-pricing/).

If you choose to publish your app, you’ll need to create developer accounts directly with Google and Apple. These accounts will be owned and managed by you, and their fees are charged separately by the respective platforms.

* Google Play Store: One-time fee of $25
* Apple App Store: Annual fee of $99

Since these fees are set by Google and Apple, they may change at any time. For the most accurate and up-to-date information, we recommend visiting their official websites:

For the latest and most accurate information, visit the official websites:

* [Google Play Store Developer Account](https://play.google.com/apps/publish/signup/)
* [Apple App Store Developer Account](https://developer.apple.com/programs/)


---

# 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.appmysite.com/pricing/developer-accounts-cost.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.