Lawnicons: community-maintained monochrome icon pack for Android launchers

Themed icons for brand apps that launchers cannot theme natively

Android launchers that support themed icons face a gap: apps whose developers have not added a monochrome icon layer to their APK appear in their original colorful form rather than the launcher's unified theme. Lawnicons fills that gap by providing community-maintained monochrome outlined SVG icons for brand apps, which compatible launchers apply in place of the original.

The project started as an addon for Lawnchair 12 Alpha 5 and above. It has since grown into a standalone icon pack compatible with most third-party launchers, applied through each launcher's own settings. The svgs/ directory at the repository root holds all submitted icon assets, giving contributors a clear place to add new ones.

The pack is described as community-driven and free, with contributors from around the world. The maintainer processes new icon pull requests around Saturday each week, and the number of covered apps grows with each merged contribution.

Four install sources, and why the Play Store app ID differs from others

Lawnicons is available from four sources: Google Play, IzzyOnDroid, Obtainium and GitHub. Each points to the same icon pack, with one exception documented in the README: Lawnicons on the Play Store will install as a different app from other sources.

A different app in this context means a different package ID. Installing from Google Play and from GitHub results in two separate entries in Android's app list rather than one. Switching sources requires uninstalling the current version first. The README does not explain why the Play Store build uses a separate ID, but the consequence is clear: launcher theming settings configured with the Google Play version will not carry over to a direct APK install.

For users who want recently merged icons, a develop-branch APK is available through nightly.link (which generates direct download links from GitHub Actions artifacts) and through Obtainium. Those builds are debug-signed rather than production-signed.

Applying Lawnicons in Lawnchair and enabling it in other launchers

In Lawnchair, Lawnicons is activated through a specific navigation path: Home Settings → General → Icon Style. This is the path documented in the README for Lawnchair users, and no command-line step is involved.

For other launchers, the README says to apply it in your launcher's settings, without naming specific launchers or their navigation paths. Each launcher exposes its icon pack support differently, so the method is whatever that launcher's settings require. Lawnicons does not ship a configuration wizard, and the README does not document per-launcher steps beyond the Lawnchair path.

Users of launchers other than Lawnchair need to locate the icon pack setting independently. That is not a limitation of Lawnicons itself but a consequence of the icon pack API being launcher-specific in its settings location.

Contributing icons: SVG submission, the 5-per-PR cap, and a weekly review window

Adding an icon to Lawnicons requires knowledge of the design guidelines, vector graphics editing and basic GitHub workflow. The README caps new icon contributions at 5 per pull request. The maintainer reviews icon contributions around Saturday, giving the process a predictable weekly cadence.

The repository provides tooling for contributors. An icontool.py script and an icontool binary are at the root, alongside lint_icons.py and an svg-processor/ directory. CONTRIBUTING.md at the root holds guidelines, and the developer wiki covers the workflow in more depth than the README itself.

An icon request dashboard at lawnicons-requests.vercel.app lists what the community has asked for. Contributors can use it to find icons that users want rather than adding ones arbitrarily. For users who want an icon but cannot contribute it themselves, the dashboard is where to file or track a request.

Open Collective priority queue: supporters get faster fulfillment

Lawnicons has a funding model that directly affects how quickly icon requests are processed. The README states that requests from supporters get fulfilled much faster than standard requests. Supporting the project happens through Open Collective, and a dedicated supporter request issue template exists for submitting prioritized requests.

This priority difference is explicit in the documentation: 'Requests from Lawnicons supporters get fulfilled much faster than if you just wait.' Donations go to Lawnicons specifically within Open Collective, separate from the broader Lawnchair project funding. Funded contributions are viewable through a pull request label on GitHub.

For anyone who needs a specific icon covered soon rather than eventually, this is the documented mechanism. For developers maintaining an app who want Lawnicons to include their icon, supporting the project moves that request up the queue ahead of standard community requests.

What the SVG processor, lint tool, and fastlane directory do for quality and publishing

The repository structure gives a clear picture of how icon submissions are handled beyond the manual review. An svg-processor/ directory handles SVG normalization, lint_icons.py checks submitted icons for compliance with the design guidelines, and generate_previous_release.py prepares comparison data between builds. These tools run as part of the contribution workflow.

A fastlane/ directory at the root manages store metadata and screenshots for automated publishing. The combination of svg-processor and lint_icons.py means that a contributor's SVG goes through automated checks before the Saturday review, catching format errors before they reach the maintainer.

Localization of the app's interface text runs through Crowdin, with a crowdin.yml configuration at the root. The app/ directory holds the Android application code in Kotlin, while the svgs/ directory holds the icon assets themselves. These two concerns are cleanly separated in the repository layout.

Gradle build system, spotless formatting, and the Kotlin app component

The build system is Gradle, with build.gradle.kts, settings.gradle.kts and gradle.properties at the root alongside the Gradle wrapper; Kotlin is the primary language for the application component. No build command is documented in the README, so building from source requires reading build.gradle.kts directly to find the relevant tasks.

The repository also includes spotless.xml.prefs for code formatting and a .editorconfig at the root, both enforcing consistent style across contributions without requiring the maintainer to manually flag formatting issues during the Saturday review.

v2.18.0 was tagged on 2026-06-17, with the last push to the repository on 2026-10-05. Source code, icons and tooling are all under Apache-2.0; the LICENSE file at the root is the authoritative text.

Editorial conclusion

Lawnicons is the right choice when your launcher supports third-party icon packs and you want consistent monochrome icons for apps that have not shipped their own. It works with most third-party launchers, though Lawnchair users get a dedicated path under Home Settings → General → Icon Style. Skip it if your launcher does not support the icon pack API, or if you need color icons. Before downloading, decide which source fits your update preferences: the Play Store version installs under a different app ID than GitHub or IzzyOnDroid, so switching between them requires an uninstall first.

Frequently asked questions

Official sources

1. Issues
2. LawnchairLauncher/lawnicons on GitHub
3. License: Apache-2.0
4. README
5. Releases