> For the complete documentation index, see [llms.txt](https://docs.decentraland.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.decentraland.org/creator/build-for-mobile/mobile-client/overview.md).

# Overview

Decentraland is now available on mobile. Players can explore your scenes from iOS and Android devices, in addition to the desktop client and the web. As a creator, you can adapt your scenes so they look great and play well on touch-based devices.

![Decentraland mobile app — Genesis City](/files/GBaapSlhcAKZRIU3raEP)

{% embed url="<https://www.youtube.com/watch?v=FBr2gye3qh8>" %}

## Get the mobile app

* [Download for iOS (App Store)](https://apps.apple.com/app/decentraland/id6478403840?utm_source=docs\&utm_medium=internal\&utm_content=ios)
* [Download for Android (Google Play)](https://play.google.com/store/apps/details?id=org.decentraland.godotexplorer\&pcampaignid=web_share\&utm_source=docs\&utm_medium=internal\&utm_content=android)

## Building for Mobile

### Reference

* [Sample Scenes](/creator/build-for-mobile/mobile-client/sample-scenes.md) — open-source scenes built by the Decentraland team and optimized for mobile play.
* [Missing Features](/creator/build-for-mobile/mobile-client/missing-features.md) — features available on the desktop client that are not yet supported in the mobile app.
* [Hardware Requirements](/creator/build-for-mobile/mobile-client/hardware-requirements.md) — minimum and recommended hardware specs for running Decentraland on mobile.

### Develop

* [Detect the platform from code](/creator/build-for-mobile/develop/detect-platform.md) — use `isMobile()` to branch your scene's logic and UI per platform.
* [Preview your scene on mobile](/creator/build-for-mobile/develop/preview-on-mobile.md) — preview directly on a phone via the Creator Hub or the CLI.
* [Mobile safe area](/creator/build-for-mobile/develop/safe-area.md) — the device's hardware margins (notch, home indicator) and the regions the client's own controls occupy; pick the area your UI is placed in with `screenInset`.
* [UI best practices for mobile](/creator/build-for-mobile/develop/ui-best-practices.md) — DOs and DON'Ts, sizing recommendations, and current limitations.
* [Input on mobile](/creator/build-for-mobile/develop/input-on-mobile.md) — touch-friendly input mappings and which `InputAction`s to avoid.
* [Optimize Performance](/creator/build-for-mobile/develop/optimize-performance.md) — mobile scene limits, how to preview them in Creator Hub, and performance targets.

### Publish

* [Get featured on mobile Discover](/creator/build-for-mobile/publish/get-featured.md) — submission requirements for the mobile Discover section.
* [iOS curation](/creator/build-for-mobile/publish/ios-curation.md) — how iOS content curation works and how to submit your scene or world for review.

## Quick checklist

Before publishing a scene that should work well on mobile, make sure that:

* [ ] You have previewed the scene on a real device — see [Preview your scene on mobile](/creator/build-for-mobile/develop/preview-on-mobile.md).
* [ ] All critical UI elements stay inside the [mobile safe area](/creator/build-for-mobile/develop/safe-area.md).
* [ ] Your UI is sized large enough for touch — follow the [UI best practices](/creator/build-for-mobile/develop/ui-best-practices.md).
* [ ] Key actions are not bound to `IA_ACTION_3`–`IA_ACTION_6` (the `1`/`2`/`3`/`4` keys), which are not easily reachable on mobile — see [Input on mobile](/creator/build-for-mobile/develop/input-on-mobile.md).
* [ ] Your scene's [Performance](/creator/build-for-mobile/develop/optimize-performance.md) is above 90% on the High Graphics Profile on a mid-range phone — see [Hardware Requirements](/creator/build-for-mobile/mobile-client/hardware-requirements.md) for reference devices.


---

# 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.decentraland.org/creator/build-for-mobile/mobile-client/overview.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.