# Send app to stores

## Publish Your App to the Stores

Your native app can be sent right through to the Apple and Google Play stores ready for release. To do this you need to already have developer accounts on both platforms.

We can help you with this if you wish as it helps if you have been through the process at least once. Once you have an account you can generate a unique identification key for your app - like a passport or ID card number. This is put into the automated pipeline build and each app which is built is signed by your identity.

This means it appears in your store account, with your branding and is **100%** yours.

If in subsequent years you want to replace the app with one you build in-house, or through another dev team, you will simply sign that app with the same identity and it will over-write the Reptile one.

All apps released on Reptile will be on a maintenance plan, which means that we will keep the app up-to-date with software changes required by the stores. We will typically update and re-publish your app once or twice a year to include the latest changes.

All you have to do is to keep paying your annual store membership ($79 for Apple currently) and have someone in your company assigned to accept the occasional Ts and Cs they send through which only the app owner can do. We will keep an eye on this and let you know if we see a renewal you need to action.

<figure><img src="/files/pOvnHxjE34qmexyBrI4c" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://learn.reptile.app/help-guides/send-app-to-stores.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.