> 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/getting-started/initial-requirements.md).

# Initial requirements

### What do you need to get started with AppMySite?

AppMySite is a no-code app development platform that enables you to create an app in minutes. Powered with integrations and features, AppMySite is the ideal solution to build an app for your business. 

To get started, you may or may not need a website depending on the app want to create- 

* With the Custom app solution, you don’t need anything. This solution is designed to help you build an app without a website. 
* With the WordPress solution, you need a WordPress website to get started. 
* With the WooCommerce solution, you need a WordPress website which has a WooCommerce plugin.
* With the Web to app solution, you need a website. There are no specific CMS requirements as this solution works with any CMS platform or web technology. 

{% hint style="warning" %}
In addition to these initial requirements, you must create developer accounts for Google Play and the Apple App Stores. This is mandatory to submit your app to the app stores.
{% endhint %}


---

# 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/getting-started/initial-requirements.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.