> For the complete documentation index, see [llms.txt](https://shiro.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://shiro.gitbook.io/docs/the-shiro-platform/shiro-on-different-devices.md).

# Shiro on Different Devices

### Cross-Platform Compatibility

Shiro is designed to be accessible across a wide range of devices, including desktops, laptops, and mobile devices. This cross-platform approach ensures that players can enjoy the game regardless of their preferred hardware.

### Optimizations for Various Platforms

For each platform, Shiro is optimized to maintain a consistent gaming experience. On mobile devices, particular attention is given to touch interface responsiveness and battery efficiency. For desktops and laptops, the focus is on leveraging higher processing power to deliver richer graphics and smoother gameplay.


---

# 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://shiro.gitbook.io/docs/the-shiro-platform/shiro-on-different-devices.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.