> For the complete documentation index, see [llms.txt](https://docs.lawnchair.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.lawnchair.app/getting-started/install-and-setup.md).

# Setup Lawnchair

Install Lawnchair and set it as your default home app.

Lawnchair only takes a few minutes to set up.

Install the build you chose, then set Lawnchair as your default launcher.

{% stepper %}
{% step %}

#### Install the app

Download and install the build you chose in [Choosing a version](/getting-started/choose-a-version.md).
{% endstep %}

{% step %}

#### Set Lawnchair as default home app

After installation, tell Android to use Lawnchair as your default launcher.

1. Long-press the home screen, then tap **Home settings**.
2. In **Home settings**, tap the card that says "To access shortcuts and additional features, set Lawnchair as your default launcher".
3. In the screen that appears, choose **Lawnchair** from the list.
   {% endstep %}
   {% endstepper %}

### Need help?

If installation fails, see [Installation issues](/troubleshooting/installation-issues.md).

<details>

<summary><strong>Advanced</strong>: Verify your installation</summary>

Security-conscious users can verify the cryptographic integrity of our packages by [reviewing our verification guide](/getting-started/install-and-setup/verify.md).

</details>


---

# 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.lawnchair.app/getting-started/install-and-setup.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.