> For the complete documentation index, see [llms.txt](https://docs.appmachine.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmachine.com/share-your-app/publishing-your-app/technical-setup-quick-start-guide.md).

# Technical Setup Quick Start Guide

## **Technical Setup Apple App Store in AppMachine**

You can already take these steps if your app isn't completely finished yet.

1. Make sure you have an **App Store Connect account**. [Read more...](/share-your-app/apple-app-store/ios-developer-account.md)\ <br>

   <figure><img src="https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/80115512322/original/akF8MYjvqmIwfctn5JNuuDhrdcWLvQkgOA.png?1655891098" alt=""><figcaption></figcaption></figure>
2. In the AppMachine Publish screen you can choose Apple App Store > **Setup App Store Connect Api Key**. [Read more...](/share-your-app/apple-app-store/app-store-connect-api-keys.md)
3. In the same wizard, AppMachine will create an **App Bundle Identifier** for you. [Read more...](/share-your-app/apple-app-store/link-your-app.md)
4. Next, AppMachine will ask you to create an **App Record** in App Store Connect. Use the Bundle Identifier which AppMachine created for you in the previous step. [Read more...](/share-your-app/apple-app-store/new-app-record-in-app-store-connect.md)
5. Carefully fill in the **App Privacy** Information in App Store Connect and make sure your answers correctly reflect your App. [Read more...](/share-your-app/apple-app-store/app-privacy-details.md)

### **Technical Setup Google Play Store in AppMachine:** <a href="#setup-google-play-store-in-appmachine" id="setup-google-play-store-in-appmachine"></a>

You can already take these steps if your app isn't completely finished yet.

1. In the AppMachine Publish screen you can choose Google Play Store > Setup Play store\
   \
   This wizard will guide you how to set up **Firebase** keys, required for publishing, analytics, user authentication, data storage and more. [Read more..](/share-your-app/google-play/setup-your-android-app.md)<br>

   <figure><img src="https://s3-eu-central-1.amazonaws.com/euc-cdn.freshdesk.com/data/helpdesk/attachments/production/80110276631/original/VJ_cnkFWOsCkNn4ZtxXwTbDZLXwU5Aeaog.png?1654441662" alt=""><figcaption></figcaption></figure>
2. Create a **Google developer account**, this costs $25 per year. It will take Google a few days to review your account, so don't this wait with this step till the end. [Read more..](/share-your-app/google-play/create-a-google-developer-account.md)
3. If your app shows a map, for example in an events block, Contact block or if you have added a Map to a screen yourself  you need to create **Google Maps** Api keys.  [Read more..](/share-your-app/google-play/how-to-request-a-google-maps-api-key.md)
4. If you want to track your customer's activities in your app, you need to enable this at\
   Manage > Settings > Firebase analytics. Don't forget to enable Google analytics when you create [your Firebase keys.](/share-your-app/google-play/setup-your-android-app.md)
5. If your have **user registration via Facebook enabled** you will need to create your own **Facebook keys.** \
   While logging in, your customers will see the name of your Facebook app. [Read more..](/app-details/user-management/create-facebook-app-id-secret.md)
6. If you have a **Twitter block,** you will need to add Twitter API keys to retrieve data for your Twitter block. [Read more..](/app-details/twitter-api-keys.md)
7. Google Play > Edit Store info to see if the **Default language** is set correct


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.appmachine.com/share-your-app/publishing-your-app/technical-setup-quick-start-guide.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.