> 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/choose-a-version.md).

# Choose a version

Compare release channels and choose the right Lawnchair build.

Lawnchair is available through several release channels. Each channel balances stability and new features differently.

Choose the one that fits how you use your device.

<table><thead><tr><th width="154">Release channel</th><th width="193">Intended users</th><th>Stability</th><th>Characteristics</th></tr></thead><tbody><tr><td><a href="https://lawnchair.app/downloads">GitHub</a></td><td>Most users</td><td>Generally stable, suitable for daily use</td><td>A balance of new features and reliability. Released periodically after testing.</td></tr><tr><td><a href="https://github.com/LawnchairLauncher/lawnchair#development-builds">Nightly</a></td><td>Testers, enthusiasts, users needing a specific fix</td><td>Potentially unstable. May contain bugs.</td><td>Built automatically with the latest code changes. Has a built-in updater. Installs as a separate app from the Beta version.</td></tr><tr><td><a href="https://play.google.com/store/apps/details?id=app.lawnchair.play">Play Store</a></td><td>Users who prefer automatic updates via Google Play</td><td>Same with Official Beta</td><td>Releases for the Play Store often follow Official Beta releases but can be delayed by 1-2 weeks due to platform review processes. Uses a different package name from GitHub versions.</td></tr></tbody></table>

### Summary

* Start with **GitHub** or **Play Store** for the most stable experience.
* Use **Nightly** if you want the latest fixes and accept occasional breakage.


---

# 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/choose-a-version.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.