> For the complete documentation index, see [llms.txt](https://docs.uibakery.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uibakery.io/concepts/mobile-layout.md).

# Mobile layout

In UI Bakery, you can switch between a **desktop** and **mobile** layout for your applications:

* **Desktop**: 100% of the available page space
* **Mobile**: 400 px

The desktop layout is applied by default. To switch to the *mobile* layout, you need to change the adaptive control in the header to the mobile option.

{% hint style="info" %}
Please note that altering the layout of an application changes the layout of all its pages.
{% endhint %}

{% @arcade/embed flowId="TCd7UlGrS6z6YoYxzTI5" url="<https://app.arcade.software/share/TCd7UlGrS6z6YoYxzTI5>" %}

## Configuring component visibility for different layouts

Components can be configured to be visible only on a specific layout. For example, you may not want to include a large table on mobile view.&#x20;

In such cases, you need to select the component, navigate to the **Responsive** setting, and select the layout you want the component to be visible on.

{% @arcade/embed flowId="UrpJELE15n2U5t9BTjU9" url="<https://app.arcade.software/share/UrpJELE15n2U5t9BTjU9>" %}

{% hint style="warning" %}
If you make changes to components on the **desktop** layout, they will not be applied on **mobile**, and vice versa.\
Also, keep in mind that components added to a certain layout do not have the same position on the other layout - they are displayed at the bottom of the page.
{% endhint %}


---

# 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.uibakery.io/concepts/mobile-layout.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.