> For the complete documentation index, see [llms.txt](https://docs.appfarm.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appfarm.io/appcademy/appfarm-fundamentals/user-interface-fundamentals/responsive-design.md).

# Responsive Design

Responsive Design, or Responsive Layout, allows you to create 1 App targeting different devices. In other words, the same App may have a different look-and-feel on a mobile device and a PC. The UI Designer in Appfarm allows you to enable Responsive Design, allowing you to define different settings on UI components for the different devices.

### Guide and Example

You may find a Guide on how to set up a Responsive App in our documentation:

[Responsive Layout (Guide)](/how-to/user-interface/responsive-layout.md)

The above guide is a walkthrough of a Responsive App found in our Showroom: 

<https://showroom.appfarm.app/drag-and-drop-kanban>

### **Other Documentation**

Other relevant articles in our documentation:

[Responsive Design](/reference/apps/ui/layout-designer.md#responsive-strategy)


---

# 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.appfarm.io/appcademy/appfarm-fundamentals/user-interface-fundamentals/responsive-design.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.