> For the complete documentation index, see [llms.txt](https://www.center.daxium-air.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.center.daxium-air.com/news/2025/colored-map-pins-android.md).

# Colored map pins now available on Android

After web and iOS, Daxium-Air Android v2.4.5 brings colored map pins to field users.

**Published on May 6, 2025**

Good news for Daxium-Air Android users. After the web and iOS apps, your map pins finally come in color on **Daxium-Air Android v2.4.5** — more visual and more efficient for field users.

![](https://1160383192-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FotkY8NZEogvR3XMRPSkn%2Fuploads%2Fgit-blob-d50a2c7a1a7e8bc66fb8b5d100e1b759d9b74418%2F22a93a_886c805d3ff241e393b9b1512246baaf~mv2.png?alt=media)

## How does it work?

If your forms use a [workflow](https://www.center.daxium-air.com/user-documentation/build/building-the-platform/building-forms/workflow-and-assignation) or a functional status with a list containing colors, then the map pins automatically take on the color associated with each status. A single glance is now enough to see where things stand.

{% hint style="info" %}
Remember to update your app to benefit from this feature.
{% 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://www.center.daxium-air.com/news/2025/colored-map-pins-android.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.
