> 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/develop.md).

# Develop

- [Detect the platform](https://docs.decentraland.org/creator/build-for-mobile/develop/detect-platform.md): Detect whether your scene is running on mobile, desktop, or web.
- [Preview on Mobile](https://docs.decentraland.org/creator/build-for-mobile/develop/preview-on-mobile.md): Preview your scene on a real mobile device from the Creator Hub or the CLI.
- [Mobile Safe Area](https://docs.decentraland.org/creator/build-for-mobile/develop/safe-area.md): Where scene UI can safely live on mobile — clear of the device's hardware margins and of the client's own controls.
- [UI Best Practices](https://docs.decentraland.org/creator/build-for-mobile/develop/ui-best-practices.md): DOs and DON'Ts for designing scene UIs that work well on mobile.
- [Input on Mobile](https://docs.decentraland.org/creator/build-for-mobile/develop/input-on-mobile.md): How input actions map to touch on the Decentraland mobile client.
- [Performance](https://docs.decentraland.org/creator/build-for-mobile/develop/optimize-performance.md): Mobile scene limits and performance targets for Decentraland scenes, and how to preview and measure them from the Creator Hub.


---

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