> For the complete documentation index, see [llms.txt](https://docs.ecwid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ecwid.com/launch-apps/steps-to-go-live-with-a-public-app.md). # Steps to go live with a public app Thank you for your decision to build an app for Ecwid! Follow the steps listed below to convert your app idea into a working solution available to more than 100M users around the world. ### Submit your app idea Send a [Request form](https://forms.monday.com/forms/4307bb490509448eee3ccc4a54695711?r=use1) telling us about the app you want to create: its usefulness to our merchants, preferred billing type, supported regions and platforms, etc. ### Learn more about application types Public apps can have different business logic or none at all. Depending on what backend and/or website admin you have, we offer two main approaches to handling your users, known as **application types.** Two types are **Native** and **External** apps. Choose a suitable type for your app to make a secure and reliable application for our mutual users: [Native and external apps](/launch-apps/native-and-external-apps.md) ### Learn more about monetizing With an app in our App Market, you gain access to thousands of potential paid users. There are many ways to monetize your work: monthly price, pay-per-use payments, one-time premium purchases, and more. Ecwid provides tools to set up and handle flexible billing: [Monetize public apps](/launch-apps/monetize-public-apps.md) ### Start working on a dev version With an approved [Request form](https://forms.monday.com/forms/4307bb490509448eee3ccc4a54695711?r=use1), you get a free test store on a Premium plan and a dev app. From here, you can access all platform features and freely use the store as a playground. [Email us](mailto:ec.apps@lightspeedhq.com) if your workflow requires an additional staging app or several stores for tests. ### Complete app publishing process When your app is ready to be published, start the **app validation** process to ensure it meets all requirements. At its end, the app gets published and becomes available in the Ecwid App Market. To get through the validation process more easily, follow the [Guide to App Validation](/launch-apps/steps-to-go-live-with-a-public-app/guide-to-app-validation.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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.ecwid.com/launch-apps/steps-to-go-live-with-a-public-app.md?ask=&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.