Fossify Launcher is a privacy-first home screen for Android

The positioning is a launcher with nothing bolted on

Fossify Launcher is described as your gateway to a fast, personalised and privacy-first home screen experience, and the second line sets the terms of the deal: no ads, no bloat, just a smooth, efficient launcher designed to fit your unique style and preferences. That is an unusual claim for an Android home screen, because the launcher category is one of the few where data collection is the business model, and the usual pattern is a free tier with ads and a paid tier without. The Fossify position is that the free tier is the whole product and the business model lives elsewhere, in the wider catalogue of Fossify applications. The repository is the launcher for that catalogue, and the topics recorded for it are android, foss, kotlin, launcher and open-source, with the primary language Kotlin and the licence GPL-3.0.

Five claims, and they are the whole feature list

The readme is organised as a set of labelled claims, and each is a promise about behaviour rather than a list of settings. Lightning-fast navigation says the launcher is optimised to be responsive and fluid, giving instant access to your favourite apps without lag. Full customization covers dynamic themes, custom colours and layouts, with easy-to-use tools to create a setup that matches your style. Complete widget support covers fully resizable widgets, with clocks, calendars and other tools blending into the home screen design. No unwanted clutter is about hiding or uninstalling apps in a few taps to keep the screen organised. And privacy and security is the one that carries the most weight, with the claim that there is no internet access and no intrusive permissions, so your data stays with you, with no tracking and no ads. Open-source assurance is the last, and it points at the code on GitHub as the reason to trust the rest.

Three channels, and the privacy argument depends on which one

The download badges at the top of the readme show three ways to install the application. Google Play carries the package under the identifier org.fossify.home, F-Droid lists the same package, and IzzyOnDroid has it as well. Having all three is normal for an open source Android project, but the interesting part is that the repository's own source is available, so the builds on those channels can in principle be reviewed against it. Given that the privacy claim is the core of the pitch, that distinction is the substance rather than a footnote. A launcher that asks for no internet permission is only meaningful if the binary you install is the one whose source you can read, and the F-Droid build is the one where that chain is shortest. The other links in the readme point at the wider Fossify catalogue on the website, the GitHub organisation, a Reddit community and a Telegram channel.

What the repository shows about how it is built

The top level of the repository is a standard modern Android project, and it tells you more about the engineering than the readme does. There is an app/ directory for the application module, build.gradle.kts and settings.gradle.kts for the Gradle build in Kotlin DSL, a gradle/ directory, gradle.properties, and the gradlew and gradlew.bat wrapper scripts. The lint configuration is split into two files, with a lint.xml and a detekt.yml, which means the project runs both the Android lint pass and detekt, the Kotlin static analyser, so the code is checked for style and correctness rather than merely compiled. The fastlane/ directory holds the release metadata and the store screenshots, and the readme's phone screenshots live under fastlane/metadata/android/en-US/images/phoneScreenshots/, which means the images you see in the readme are the same assets shipped to the stores. The graphics/ directory holds the artwork, and there is a keystore.properties_sample file, which is the template for the release signing key that a maintainer fills in but which stays out of the repository. There is a CODEOWNERS file, a CONTRIBUTING.md, a CHANGELOG.md, an .editorconfig, a .fossify/ directory for project-specific configuration and a Gemfile with a lock file, which is the Ruby side of the fastlane tooling.

A family of applications rather than a single project

The links at the bottom of the readme point to more Fossify apps, to the open-source code under the FossifyOrg organisation, to a Reddit community and to a Telegram group, and that shape tells you how the project is organised. Fossify is a group of simple, privacy-respecting replacements for individual Android system applications, each with its own repository and its own release cadence, sharing a design language and a common approach to permissions. The launcher is the most visible of them and the one every user sees first, which is why its own readme is mostly marketing while its value to the organisation is that it is the thing people install first. The GitHub organisation badge in the readme is the open-source assurance claim in practice: the point of the Fossify name is that the code for every application in the family is on GitHub, and the link is given so that a reader can check it rather than take the word for it.

Where this is the wrong choice

Three limits are worth naming. The first is that the readme is a marketing page rather than a technical document, so it tells you what the launcher claims to do and not how any of it is configured, and there is no user manual linked, no documentation directory and no build instructions. A contributor has to read the code, and a user has to discover the settings. The second is that nothing in the project describes a layout backup or sync, which for many people is the feature that makes a launcher worth adopting, since re-arranging your home screen by hand after a device change is the most common complaint about the category. The third is the release gap between the tree and the store. The current release is 1.10.0 from 2026-02-17 while the last push was on 2026-10-19, so the working tree has moved considerably past what a user can install from the stores, and the changelog rather than the readme is where the current state of the project is described. None of that makes the launcher a bad choice for what it does, which is to be a fast, ad-free home screen that asks for no internet access, but it does mean you should expect to read the code rather than the documentation.

Editorial conclusion

Fossify Launcher suits someone who wants a home screen without advertising or an internet permission, and it suits anyone who prefers an F-Droid build, since the project ships the application through all three channels. It is the wrong tool if you want a launcher that syncs your layout to a server or restores it onto a new phone, because nothing in the project describes such a feature. It is also the wrong choice if you need to move your existing launcher settings across, since the repository documents no import path. Before installing, decide which channel you want and why, because the privacy claim is the reason to pick one build over another, and check the changelog entry for the version you install rather than the marketing page. The last push was on 2026-10-19 and the current release is 1.10.0 from 2026-02-17.

Frequently asked questions

Official sources

1. FossifyOrg/Launcher on GitHub
2. License: GPL-3.0
3. Project website
4. README
5. Releases