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

# Custom plan features

### What is a custom app solution? How does it differ from other solutions?

A custom app solution enables you to build a fully personalized mobile app without the need for a website. If you are aiming to create an app from the ground up, this solution is ideal for you.&#x20;

This makes the custom app solution the most flexible one, with the ability to create dynamic posts and pages. You can easily add, update, and manage content like blog posts and articles that can be organised through categories, tags and attributes. Additionally, you can add various types of pages, all tailored to your specific requirements.

#### Key features

* Add multimedia elements:  Integrate images, videos, galleries, and buttons to enrich the user experience.
* Embed multimedia: Incorporate YouTube videos, code snippets, Facebook videos, Vimeo videos, and much more.
* Include dynamic content: Maintain an engaging app experience for your app users by keeping your content relevant.

{% hint style="success" %}
Progressive Web Apps (PWAs) are included as part of the Custom app product and support all the multimedia and dynamic content features listed above.
{% endhint %}

Unlike other plans that require you to have a website to convert into a mobile app, this plan lets you build a fully native app from scratch.

This plan also includes features such as advanced design tools, advanced bottom bar and menu, app simulators, push notifications, ad monetization, chat integration, analytics and the ability to publish on both the Google Play Store and Apple App Store, just like other solutions.&#x20;


---

# 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/custom-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.
