> 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/free-plan-features.md).

# Free plan features

### What you can do with the Free plan?

With the Free plan, users enjoy a variety of capabilities:

* Full App Creation: Build a fully functional mobile app from start to finish.
* Utilize All Features: Access all features, products, and utilities provided by AppMySite.

#### Advantages

* 1 x Android app: Create one Android app build for free.
* In-app browser: Integrate a built-in browser within your app.
* Customizable design: Customize the design of your app to match your brand.
* Real device testing: Test your app on real devices to ensure optimal performance.
* Push notifications: Send push notifications to engage with your app users.
* Monetization features: Explore monetization options within your app.
* Team collaboration: Collaborate with your team members during the app-building process.

#### Limitations

* No Apple App Store publishing: With the free plan, you will still be unable to publish your iOS app to the Apple App Store.
* Lack of Premium Features: Premium features like chat support and rich notifications are not included in the Free plan. 
* AppMySite branding: All apps created with the free plan include AppMySite's branding.


---

# 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/free-plan-features.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.