> 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/community/about/readme.md). # Roadmap and future features This page provides an overview of Lawnchair's development status, future goals, and release philosophy. ## Vision Lawnchair's goal is to be: * A close match to the core Pixel Launcher experience. * Provide deep and meaningful customization. * A rock-solid, reliable foundation. ### Development status Lawnchair is an open-source project driven entirely by volunteers. Contributors work on the project in their free time, alongside jobs, school, and other personal commitments. Development activity can vary, with periods of rapid progress followed by quieter times. Lawnchair is still actively developed. You can see the latest changes in the commit history on our [GitHub repository](https://github.com/LawnchairLauncher/lawnchair) or by installing Nightly builds. ### Release policy (ETAs) We do not provide estimated release dates for new versions. Given the volunteer nature of the project, deadlines are often not feasible and create unnecessary pressure. A new version is released when it is ready. ### Future goals and roadmap Our development is community-driven and depends on contributor availability, so specific timelines are not set. However, some of our high-level goals for future versions include: * Port all Lawnchair Legacy features. * Add highly requested community features. * Simplify the Lawnchair user experience. For more detailed planning, you can review our project's roadmap and open issues on GitHub. --- # 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/community/about/readme.md?ask=&goal= ``` `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.