> For the complete documentation index, see [llms.txt](https://docs.arcticons.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcticons.com/contribute/building-the-app-yourself.md).

# Building the app yourself

## Building the app

**Prerequisites**: Android Studio and python3  installed on your device.

1. Place the created icons in the `/newicons` folder and add the new Component Info codes in the `appfilter.xml`, you can gather it with [icon request](https://github.com/Kaiserdragon2/IconRequest/releases/) (see [Updating existing apps](/contribute/updating-existing-apps.md)).
2. Change the `versionCode` and `versionName` in the `/app/build.gradle` file.
3. Open the repo in Android Studio. It will take a while to sync/load everything for the first time.
4. Choose the build flavor that you want 
5. In the top bar on the right side, you will see a dropdown menu next to a green play button.

   <figure><img src="https://1579052187-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2RrVVBRQ3dxPE4yo9gYS%2Fuploads%2FTPT4ojL3VkD7BfkeEqix%2FScherm%C2%ADafbeelding%202025-04-07%20om%2014.43.43.png?alt=media&amp;token=91458af2-9ffe-4e3d-9212-f347700d2b05" alt="" width="297"><figcaption></figcaption></figure>
6. It's important to check for possible errors in your icons or appfilter entries, click on the dropdown menu and click on **RunChecks**. The Build tab at the bottom will show possible entries or icons to fix.
7. In the left sidebar, you will find the build variants button, choose the variant that you want<br>

   <figure><img src="https://1579052187-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F2RrVVBRQ3dxPE4yo9gYS%2Fuploads%2FoXmYuniC4xBCgMml8TL0%2FScherm%C2%ADafbeelding%202025-04-07%20om%2011.35.51.png?alt=media&amp;token=f7b77a78-c04a-4c41-aaaf-85aac45d3231" alt="" width="341"><figcaption><p>Build Variants tab in Android studio</p></figcaption></figure>
8. Click on the dropdown menu and click on **Prepare New Release**, and then the green play button. Wait for the process to finish.
9. Plug your phone and allow USB debugging in your phone's developer settings.
   1. `Settings > About phone > Build number`
10. Click on the dropdown menu and click on **App**, then the green play button to run the app on your phone!
    1. You can also generate an APK file in Android studio:
       * `Toolbar > Build > Make project (the hammer icon)`
         * For a [normal APK](https://developer.android.com/studio/run/): `Toolbar > Build > Build bundle(s)/APK(s) > Build APK(s)`
         * For a [signed APK](https://developer.android.com/studio/publish/app-signing): `Toolbar > Build > Build bundle(s)/APK(s) > Generate signed bundle/APK`

### Choosing your build flavors

The app is built as a debug version (`com.donnnno.arcticons.debug`) by default.

To choose another variant: `Build Variants`(on the left sidebar) `> *Active Build Variant* > select from the menu.`


---

# 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.arcticons.com/contribute/building-the-app-yourself.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.