Lawnchair 16: a Launcher3 fork with Pixel features and heavy theming

The problem Lawnchair solves for Android users

Stock Launcher3 is deliberately plain. It gives you a home screen, an app drawer and a search bar, and it stops there. Pixel Launcher adds features on top of it, but it ships on Pixel devices and is not built to be forked. Lawnchair sits between those two points: it takes Launcher3 as its starting point, ports Pixel Launcher features, and then exposes customization that neither of the other two offers.

The README lists what that means in practice. Material 3 Expressive theming follows your wallpaper and system colors. There is At a Glance widget support with integration for Smartspacer. There is global search for apps, contacts and web results from the home screen. Icon packs, fonts and color settings are user-configurable. QuickSwitch adds Android Recents integration on Android 15 and 16, and the README states it requires root.

The audience is narrower than "all Android users". This is for people who treat the home screen as a surface they want to configure, who already know what an icon pack is, and who are comfortable with the fact that the project ships beta and nightly builds rather than a stable release channel. The README does not present a supported-device list, so hardware compatibility is something you discover by installing.

How Lawnchair relates to Launcher3 and the 16-dev branch

Lawnchair is not a rewrite. The repository layout makes the inheritance visible: alongside the usual Gradle and manifest files there are directories named quickstep, src, res, shared, compatLib, hidden-api and platform_frameworks_libs_systemui. Quickstep is the Launcher3 component that handles the recents and gesture-navigation surface on modern Android, and its presence here is the clearest sign that Lawnchair is a downstream of the AOSP launcher rather than an independent implementation.

Versioning follows the Android release the branch is based on. The README is explicit: this branch houses the codebase of Lawnchair 16, which is currently in development and based on Launcher3 from Android 16, and for Lawnchair 9 to 15 you should look at the branches with the 9- to 15- prefixes. The default branch is 16-dev. So the branch name is not a marketing label, it is a statement about which Launcher3 source tree the code sits on top of.

That structure has a cost. When Android changes Launcher3, Lawnchair has to absorb the change before it can add anything of its own. The release history reflects the pattern: v15.0.0-beta2.1 in February 2026, v15.0.0-beta3.0 in April 2026, and a nightly on 2026-09-20. There is no stable 15 or 16 release in that list, only betas and nightlies. The last push to the repository was on 2026-09-20.

Installing Lawnchair and getting to the settings

The README points at four distribution channels: Google Play, IzzyOnDroid, Obtainium and the GitHub releases page. It also draws a line between them. Lawnchair on the Play Store will install as a different app compared to other sources, and features may be restricted there to comply with Google Play publishing rules. If you install from GitHub or IzzyOnDroid and want to confirm you have an official build, the project publishes a verification page.

The README gives no installation commands, so there is nothing to copy here. The documented route is to pick a source from the download section, install from it, and then use the verification page to check that the build is official. The README does not spell out the per-device menu path for setting Lawnchair as the default home app.

Lawnchair's own settings are reached from the home screen rather than from the system settings app. The README does not describe the gesture, and the documentation site at docs.lawnchair.app is the place the project itself points to for setup detail. The features the README does name are the ones you will find there: icon pack selection, font selection, color settings, and the At a Glance widget with Smartspacer integration.

For development builds, the README is direct about what you are taking on. Development builds offer the latest features and bug fixes at a cost of performance and additional issues, and it says to make backups before installing. The Obtainium link in the README configures the app with the package name app.lawnchair.nightly, so nightly and stable installs can coexist as separate apps.

Where Lawnchair is the wrong choice

The most concrete limitation is the release channel. The recent releases are a nightly from 2026-09-20 and two 15 betas from 2026. Anyone who needs a launcher they can install once and leave alone for a year is being asked to run beta software, and the README itself warns that development builds come with a cost in performance and additional issues.

The second limitation is root. QuickSwitch, the feature that integrates Lawnchair with Android Recents on Android 15 and 16, is listed in the README as requiring root. On a stock, unrooted phone that feature is simply unavailable, and the README does not offer a non-root fallback.

The third is the licence. The repository's licence field reads NOASSERTION, and the top-level files include LICENSE.txt rather than a recognised identifier. If your reason for choosing an open-source launcher is that you can read and rely on its terms, you will have to open that file yourself. Nothing in the README summarises it.

Finally, there is the question of scope. Lawnchair is a home app. It does not replace your system settings, your notification shade, or your lock screen, and the README makes no claim that it does. If your complaint with your phone is about any of those surfaces, this project is not aimed at it.

Lawnchair against the stock Pixel Launcher and Nova-style launchers

The obvious alternative is the Pixel Launcher itself. Both descend from the same AOSP lineage, so the difference is not in the fundamental model but in what gets exposed. Pixel Launcher ships At a Glance and the search bar as fixed elements and does not offer icon pack or font selection. Lawnchair ports those Pixel features and then adds the customization layer on top, which is the whole reason the project exists. The trade-off is that you are running a fork maintained by a community rather than a component shipped with your device.

A second alternative is a launcher built independently of Launcher3, of the kind that has historically offered deep grid and gesture configuration. The difference in approach is architectural: those launchers implement their own home screen and app drawer from scratch, which gives them freedom to design unusual interactions but also means they have to reimplement system integration such as recents and gesture navigation themselves. Lawnchair inherits that integration from Launcher3 and Quickstep, which is why QuickSwitch exists as a separate, root-requiring feature rather than as something the launcher does on its own.

Neither approach is strictly better. If you want a launcher that behaves exactly like the one Google ships, with a few more switches, the Launcher3 fork is the shorter path. If you want a home screen that does not resemble the Android default at all, a from-scratch launcher is the more direct route, and Lawnchair's Launcher3 inheritance will work against you.

Maintenance, upgrades and what the licence field does not tell you

The repository is not archived and the last push was on 2026-09-20, so the codebase is being worked on. That is a statement about the branch, not a promise about your install. The upgrade path the README describes is channel-based: Play Store users get whatever Google Play allows, which the README says may be a restricted feature set; IzzyOnDroid, Obtainium and GitHub users get release APKs; and anyone who wants every change uses the nightly builds, which the README points at through nightly.link and Obtainium.

The upgrade cost is not documented. The README says to make backups before installing development builds, but it does not describe what happens to your home screen layout, icon pack selection or widget configuration when you move between builds. That is a gap, not a hidden feature: the README simply does not cover migration. Anyone planning to move from a 15 beta to a 16 build is doing so without a published compatibility statement.

On licensing, the repository reports NOASSERTION and carries a LICENSE.txt at the top level. That combination means the automated licence detection could not classify the terms, so the only reliable source is the file itself. This is not a legal opinion, and it is not a reason to avoid the project, but it does mean you should not assume Apache-2.0 or GPL-3.0 from the fact that the project is described as free and open-source. Read LICENSE.txt before you build anything on top of the code.

Editorial conclusion

Adopt Lawnchair if you want a Pixel-style home screen with icon pack, font and color controls on top of Launcher3, and you are willing to run a beta or nightly build and keep backups. Do not adopt it if you need an app with a published rollback path, a documented support window, or a licence you can read at a glance: the repository carries NOASSERTION and the README does not document rollback. Before installing, open the verify page at docs.lawnchair.app/getting-started/install-and-setup/verify and confirm the build you downloaded is an official one, since the Play Store build installs as a different app from the GitHub and IzzyOnDroid builds.

Frequently asked questions

Official sources

1. Issues
2. LawnchairLauncher/lawnchair on GitHub
3. Project website
4. README
5. Releases