> For the complete documentation index, see [llms.txt](https://help.adalo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.adalo.com/design/designing-your-app/using-the-layout-tab.md).

# Using the Layout Tab

The Layout tab holds all of the features you need to build truly responsive web and native apps that look great on any screen size.

*Skill Level: Intermediate*

## Before You Begin

* Make sure you have a good understanding of the [definition and terms](/design/designing-your-app/definitions-and-terms.md), as well as the [screen size switcher](/design/designing-your-app/using-the-screen-size-switcher.md).
* Make sure you have [created a responsive app](/design/designing-your-app/creating-an-app.md).

## Basics

The layout tab is where you can adjust how your components are laid out on different screen sizes. It encompasses quite a few areas that each have their own unique features and limitations.

In the pages that follow, you'll learn more about each feature of the layout tab and how to use it to build the best responsive apps possible.&#x20;

**You can access the Layout tab by clicking on a component or group and then selecting the Layout option.**

<figure><img src="https://3467607506-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LhGHkPsv15svPIU5I7C%2Fuploads%2F5kYtMNXuhQPLweWdkcQY%2FScreen%20Shot%202023-03-02%20at%202.03.52%20PM.png?alt=media&amp;token=55d5ea62-24fd-48d4-b237-8bf097ad9b0c" alt=""><figcaption></figcaption></figure>

## Pages in this Section

{% content-ref url="/pages/prT3rSwrn6zeKgEIxB2H" %}
[Screen Size Visibility](/design/designing-your-app/using-the-layout-tab/screen-size-visibility.md)
{% endcontent-ref %}

{% content-ref url="/pages/m0hXP9z6emVYL7Wy0oQ1" %}
[Sticky While Scrolling](/design/designing-your-app/using-the-layout-tab/sticky-while-scrolling.md)
{% endcontent-ref %}

{% content-ref url="/pages/t0G8xbGyAxiPmgE3lMpB" %}
[Shared Layout Settings](/design/designing-your-app/using-the-layout-tab/shared-layout-settings.md)
{% endcontent-ref %}

{% content-ref url="/pages/SneTXJCtNsIcnH7QPIZ2" %}
[Custom Layout Settings](/design/designing-your-app/using-the-layout-tab/custom-layout-settings.md)
{% endcontent-ref %}

## Learn More

* The layout tab is not available in apps built in the Legacy Adalo builder.

## Help

If you need additional help with this article, you can always ask in our[ community forum](https://forum.adalo.com/) or [hire an Expert](https://adalo.com/experts) to help! Be sure to paste the link to this article in your post as well!

Do you have a tutorial or help doc request? [Let us know!](https://ideas.adalo.com/tutorial-requests)


---

# 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://help.adalo.com/design/designing-your-app/using-the-layout-tab.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.
