> For the complete documentation index, see [llms.txt](https://docs.appmachine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmachine.com/share-your-app/publishing-your-app.md).

# Publishing your app

Congratulations! You've finished your app and you're ready to send it into the world. AppMachine offers three avenues for publishing the app that you've built on our platform; it can be published as a web app, an iOS app, or an Android app.&#x20;

To start the publishing process, please make sure that you've paid the subscription that offers the publishing platforms you'd like to use. You can find the specific information to publish your app on the three following platforms in the articles linked to the pages below:

[Web App Publishing](/share-your-app/web-app-publishing.md)

[Apple Publishing](/share-your-app/apple-app-store.md)

[Android Publishing](/share-your-app/google-play.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://docs.appmachine.com/share-your-app/publishing-your-app.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.
