> For the complete documentation index, see [llms.txt](https://knowledge-base.letsgetdigital.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge-base.letsgetdigital.com/in-person-event/application.md). # Branded App This article describes everything you need to know about publishing your Branded App. There are a few important steps that need to take place in order to publish your Branded App to the Google Playstore and App Store. {% hint style="danger" %} It is important to start this process as soon as possible as some steps require contact with Apple. {% endhint %} Please follow the steps listed below and the related article:


Step 1: Create Apple Developer Account	apple-developer-og.png	Create an Apple Developers Account
Step 2: Grant Access to Apple Developer Account	Screenshot 2022-11-03 150732.png
Step 3: Design of Branded App	Screenshot 2022-11-03 133158.png	App design
Step 4: App is reviewed	asc-og.png
Step 5: Branded App is published	Untitled design (17).png

--- # 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://knowledge-base.letsgetdigital.com/in-person-event/application.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.