> For the complete documentation index, see [llms.txt](https://docs.getseam.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getseam.xyz/miniapp-creation/supporting-mobile.md). # Supporting Mobile All miniapps on Seam run on all devices, both phones and on web on desktop computers. Therefore, as a miniapp developer, you'll need to make sure that you're happy with how your miniapp works on both large devices and small devices. By default, the miniapp testing harness that you've been using so far as been the desktop composer -- but there is an easy way to change the dimensions to make sure your miniapp works for phones, too. ### Testing on Mobile The best way to test for mobile screen sizes is by using the dev tools built into your web browser. For example, in Chrome, you'll want to use [Device Mode](https://developer.chrome.com/docs/devtools/device-mode). {% embed url="" %} Using Chrome devtools, you can try all the different device types {% endembed %} ### Requirements Make sure you like your miniapp at the following widths: * Mobile Small: 320px * Mobile Medium: 375px * Mobile Large: 425px --- # 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.getseam.xyz/miniapp-creation/supporting-mobile.md?ask=&goal= ``` `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.