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

# Technical Requirements

An overview of the minimum technical requirements for using the MapsIndoors SDKs and software on the available platforms.

### Android SDK

Minimum SDK version: 21\
SDK target version: 35 (This is a play store requirement)\
JDK source: 11

### iOS SDK

{% hint style="info" %}
From version 4.18.0 MapsIndoors requires a minimum iOS version of 16 and Xcode 26 as [Apple require apps to be built with Xcode 26](https://developer.apple.com/news/upcoming-requirements/?id=02032026a) to be distributed via the App Store from April 28, 2026.
{% endhint %}

Minimum iOS 16\
Minimum Xcode 26

### Flutter

Flutter 3\
Dart 2 (Dart 3 compatible)

### React Native

React Native version: 0.72 or greater (Possible to use lower versions, but functionality is only guaranteed and developed towards 0.72 or greater)

### Web SDK

Browser version that supports ECMAScript 6, e.g.

* Chrome 119+
* Edge 119+
* Firefox 115+
* Opera 111+
* Safari 15+
* Mobile Safari with iOS 15+
* Opera Mobile 72+

Mapbox recommends the latest releases of Chrome/Firefox:\
<https://docs.mapbox.com/help/troubleshooting/mapbox-browser-support/>

### Web Components

React 18

Node: Minimum version 18

### CMS

Browser version that supports ECMAScript 6, e.g.

* Chrome 119+
* Edge 119+
* Firefox 115+
* Opera 111+
* Safari 15+

### Web App

Browser version that supports ECMAScript 6, e.g.

* Chrome 119+
* Edge 119+
* Firefox 115+
* Opera 111+
* Safari 15+


---

# 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.mapsindoors.com/other/technical-requirements.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.