> 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/developers/introduction/readme.md).

# Before you start

Contributing code to Lawnchair will take patience. This page helps you decide if it is a good fit and shows other ways to help.

{% hint style="warning" %}
Lawnchair is not a good first open-source codebase for most contributors. If you are new to Android internals or open source, start with a smaller task or one of the alternatives below.
{% endhint %}

### Who this is for

This guide fits you best if:

* You know Kotlin and the basics of Android development.
* You are comfortable reading Java, XML Views, and Compose.
* You can work through tricky debugging and slower review cycles.

### Why contributing is hard

* Lawnchair is built on Google's [Launcher3](https://cs.android.com/android/platform/superproject/main/+/main:packages/apps/Launcher3/), which means working with platform-level behavior instead of a typical app-only stack.
* The codebase mixes legacy Java and XML Views with newer Kotlin and Compose code.
* Parts of the UI are still being migrated, so patterns can change from one area to another.
* The team is small and volunteer-run, so mentoring and reviews can take time.
* Launcher work often involves Android system behavior like gesture navigation, process management, permissions, and OEM customizations.

A good first contribution is small and contained. Aim for a focused bug fix or a narrow UI change.

### Other ways to help

If you can't contribute code directly, you can still help us via the following:

1. Contribute to Lawnicons using the links in the **Lawnicons** section of the sidebar.
2. [Support project maintenance](/community/get-involved/donate-to-the-project.md) via Open Collective.
3. Answer questions in the [community channels](/community/get-involved/community-channels.md).
4. Help [translate Lawnchair](/community/get-involved/translate-lawnchair.md).

If you still want to contribute code, continue to [Get started](/developers/introduction/get-started.md) for setup steps and a practical path to your first contribution.


---

# 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.lawnchair.app/developers/introduction/readme.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.