> For the complete documentation index, see [llms.txt](https://docs.arcade.software/kb/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arcade.software/kb/build/interactive-demo/share/mobile.md).

# Mobile

### When does Arcade switch to mobile view?

Arcade switches to **mobile view** when the container displaying the Arcade is less than **600 pixels wide**. This typically includes:

* Mobile devices
* Embeds inside narrow containers (e.g., chat widgets, side panels)

### What changes in mobile view?

In mobile view:

* **Hotspots remain interactive**, but the **hotspot text is moved to subtitles** below the screen to prevent overlap.
* The layout is optimized for vertical scrolling and small screens, making it easier to follow steps on phones or tablets.
* Fonts, button sizes, and spacing adapt for mobile UX best practices.

### Does Arcade support a full screen view for mobile?

Given mobile providers definitions of Arcade's software (it not being a video), we are unable to create assets that take up an entire mobile screen.


---

# 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.arcade.software/kb/build/interactive-demo/share/mobile.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.