> For the complete documentation index, see [llms.txt](https://docs-en.shoppy.is/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs-en.shoppy.is/launch-your-mobile-app/google-play-store-creations.md).
# Google Play Store Creations
If you don't have a Google account, you can click [here](https://accounts.google.com/signup/v2/webcreateaccount?flowName=GlifWebSignIn\&flowEntry=SignUp) to create one.
To set up your developer account on Google Play, follow the next 3 simple steps.
#### 1. Register on Google Play
Click [here](https://play.google.com/console/signup) to create an account on Google Play.
{% hint style="danger" %}
**Attention**
When registering on Google Play, please ensure you select an '**Organization**' **account type**. This choice is crucial for accessing specific features and managing your app more effectively.
{% endhint %}
#### 2. Complete the form and accept the terms of service.
Enter your information and agree to the terms of service. Finally, click on the blue "Create Account and Pay" button and enter your payment information.
#### 3. Invite Shoppy to your account
* Go to [Google Play Console](https://developer.android.com/distribute/console)
* Click "Users and Permissions"
* Click on the "+" symbol
* Invite as an **administrator**
* Click "Invite"
* We will contact you as soon as we receive your invitation
---
# 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-en.shoppy.is/launch-your-mobile-app/google-play-store-creations.md?ask=&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.
