> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/identity-verification/ux-and-design/responsive-design.md).
# Responsive Design
1Kosmos is built to work across the full range of screen sizes your customers use — from large desktop monitors to phones. The interface reflows automatically so content stays readable.
***
### Supported screen sizes
1Kosmos adapts across three broad layout ranges:
| Layout | Typical devices | Width range |
| ------- | ----------------- | ----------- |
| Desktop | Laptops, monitors | ≥ 1024px |
| Tablet | iPads, tablets | 768–1023px |
| Mobile | Phones | < 768px |
### What changes across screen sizes
As the screen narrows, the layout adapts rather than simply shrinking:
* **Layout & content** — Multi-column layouts reflow into a single column so nothing requires horizontal scrolling.
* **Touch targets** — On touch devices, interactive controls are sized for fingers rather than a cursor, meeting accessibility minimums [(see Accessibility)](/identity-verification/ux-and-design/accessibility.md).
* **Images & logos** — Your brand assets scale to fit; this is why we recommend an SVG logo [(see Brand Customization).](/identity-verification/ux-and-design/branding-customization.md)
### Best practices
* Preview your branding on both desktop and mobile before publishing — a logo that looks right in the header can crowd a narrow screen.
* Keep custom copy concise so it reads well on small screens.
* Test interactions on a real touch device, not just a resized browser window.
---
# 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.1kosmos.com/identity-verification/ux-and-design/responsive-design.md?ask=&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.
