Open-source project
tanujnotes/Olauncher avatar
tanujnotes/Olauncher

The feature list lives in the app, not the repository

Minimal AF Launcher for Android. Reduce your screen time. Daily wallpapers.

3,983 stars550 forksKotlinGPL-3.0

At a glance

What is it?
Olauncher is a minimal ad-free Android launcher distributed through four channels under a GPL licence. Its repository contains no feature list at all: the documentation is an About page inside the app's own settings and a newsletter, and a few features are admitted to be hidden.
Who is it for?
Olauncher suits someone who wants the shortest path from unlocking a phone to an app and does not want their home screen to run advertising, and who is willing to accept that the documentation lives inside the app. Four things to know before you install it.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 10 days ago.
What is it written in?
Mainly Kotlin, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • tanujnotes/Olauncher3,983 ★ · +141
Star history
Repository2026-09-242026-11-15
tanujnotes/Olauncher3.8k4k

141 Stars in the last 52 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

You cannot evaluate this app from its repository

The README is about a hundred words long and contains no list of what the launcher does. There is no feature section, no configuration documentation, no screenshots and no description of any setting. Instead it says that to maintain the simplicity of the launcher, a few niche features are available but hidden, and it directs you to the About page inside Olauncher's own settings for a complete list of features and frequently asked questions. The second destination is a newsletter post. So the entire functional documentation of the application lives in two places, neither of which is in version control: inside the installed app, and on a subscription site. That is a deliberate choice for a project whose author wants the repository to look like the product looks, and it has consequences. You cannot check what the app does before installing it. You cannot diff the feature set between releases. You cannot search the documentation. And if you are evaluating whether the launcher does something you need, the only reliable method is to install it and read its settings screen. For an application whose entire pitch is minimalism, that is defensible. For anyone making a procurement decision, it is a real obstacle.

The stated goal is less screen time, and one of the two features is a wallpaper that changes daily

The repository description carries the pitch in two clauses. The first is minimal, ad-free, and for Android. The second is to reduce your screen time. Then there is a third clause that the README never mentions: daily wallpapers. That is worth pausing on, because a launcher is the one piece of software whose entire job is to be the first thing you look at every time you pick up the phone. Reducing screen time and changing what the home screen looks like daily pull in opposite directions, and the description puts them in the same breath without ranking them. Nothing in the README explains what the wallpapers are, where they come from, whether there is a setting to turn them off, or whether they need a network round trip to fetch. So the most distinctive-sounding feature in the project's public description is also the one with the least documentation anywhere in the repository. If wallpapers matter to you, that is the first thing to check in the app's settings. If they do not, the honest reading of the description is that the app's case for reducing screen time rests on the absence of icons and ads rather than on anything measured.

Four channels and a GPL licence make the ad-free claim structural rather than a promise

The app is distributed four ways, and the list is the argument. There is a Play Store listing, a F-Droid entry, an entry in a German Android package repository, and direct APK downloads from the repository's releases. The licence is the GNU GPL version three. Together those four facts make the ad-free claim structural rather than a matter of trust. An app published on F-Droid has to build from source, and a package on a community repository is assembled by that repository rather than by the developer, so a paid advertisement or a tracking library introduced in a closed build would not survive the process. The direct APK route is the one weak link, since it is the same artefact the author produces, so it is worth checking that the one you download corresponds to what the other three channels are serving. The contact section offers three social platforms and no email address, and although the repository has workflow definitions, no bug-reporting route is documented. For a project this small that is a reasonable choice, but it does mean the only way to report a problem is a social media account.

The paid tier is a separate application rather than an unlock inside this one

This is the detail that answers the pricing question without a price list. There is no in-app purchase in Olauncher, no subscription and no feature gate. Instead the author publishes a second application, a Pro version, and describes it as the same launcher with extra features: widgets, weather and folders. So the monetisation model is a separate listing rather than anything inside the free app. That has a specific consequence worth naming. Someone who installs both has two launchers on the phone, which is workable but not seamless, and the free app gains nothing from the paid one's existence, because the codebases are separate distributions rather than one app with two tiers. It also means the free app carries no mechanism that could change behaviour after installation on the basis of a purchase, which for an app whose pitch is ad-free predictability is coherent. What is not documented anywhere is whether the two share code, whether the Pro version tracks the free version's releases, or what else differs between them beyond the three named features.

The release history is frequent and the version numbers have three components

Three recent releases are visible. The newest is 6.9.17, dated 2026-09-17, which is also the last commit on the default branch, so the tip of the tree is a tagged release rather than work in progress. Before it comes 6.9.1 from three days earlier, and before that 6.7.19 from two months before that. So the cadence is bursty rather than steady: two releases inside seventy-two hours, then a gap of about two months. The numbering itself is the interesting part, because it has three components and the third one is not a small integer. Going from 6.9.1 to 6.9.17 is sixteen patch releases in three days, which tells you the third component is being used as an incrementing build counter rather than as a patch level in the usual sense, where a sixteenth patch would imply sixteen separate fixes of the kind users notice. It also means you cannot infer anything about risk from a version difference here, because a jump of sixteen is as likely to be routine work as a bug fix. The last commit is recent, so the project is being worked on, but the release-to-release changes are not visible from the numbers and are not documented anywhere in the repository.

The project is one Gradle module, a release directory, and no build documentation

The tree is short enough to read in one line, and it is worth reading as a description of what building this involves. There is a settings file, a build file, a properties file, a Gradle wrapper with its Windows counterpart, the wrapper directory, a single application module, a fastlane directory, a licence file, a readme, and workflow definitions. So this is one module, not a multi-module project, and the whole application is in that module. The build is the older Groovy dialect rather than the Kotlin one, which tells you something about when the build was last modernised. The fastlane directory is the interesting entry, because that is where automated store submission lives, and it explains how a one-person project keeps four distribution channels current without doing it by hand every release. What is absent is as informative as what is present. There is no contributing guide, no code of conduct, no changelog, no documentation directory, and no build instructions. Nothing tells you how to compile it, what the minimum Android SDK is, or which Kotlin and Gradle versions it expects. For an application whose source is public, that is the most surprising omission in the repository.

Editorial conclusion

Olauncher suits someone who wants the shortest path from unlocking a phone to an app and does not want their home screen to run advertising, and who is willing to accept that the documentation lives inside the app. Four things to know before you install it. Read the description carefully, because the wallpaper feature it advertises is the one thing the repository says nothing about. Expect to configure it from its own settings screen rather than from documentation, since the feature list is not in the repository and cannot be diffed between releases. Decide which channel to trust, with the two community repositories being the ones that build the package themselves and the direct APK being the one artefact the author alone produces. And if you want widgets, weather or folders, that is the separate Pro application rather than something unlocked inside this one.

Frequently asked questions

What is Olauncher?

It is a minimal Android launcher, where the project's own abbreviation stands for ad-free. Its repository description frames its purpose as reducing screen time and also lists daily wallpapers, though the readme does not describe the wallpapers. It is written in Kotlin, released under the GNU GPL version three, and is distributed through four separate channels.

how to install olauncher

There are four documented routes: a Play Store listing, an F-Droid entry, a listing in the IzzyOnDroid repository, and the latest APK from the repository's releases page. Installing from either of the two community repositories rather than the store is the stronger choice for verifying that what you run matches the source, since those repositories build the package themselves.

Is Olauncher free?

The launcher is distributed for free through all four channels and contains no in-app purchase, subscription or feature gate. Monetisation is a separate Pro Launcher application, described as the same launcher with extra features such as widgets, weather and folders. No price for that second application appears in the repository.

Where can I find Olauncher's feature list and documentation?

Not in the repository. The readme says the complete list of features and the frequently asked questions are on the About page inside Olauncher's own settings, and it also links a post on the author's newsletter site. The readme itself contains no feature list, no screenshots and no configuration documentation.

Does Olauncher have hidden features?

The readme says so, without naming any of them. It states that to maintain the simplicity of the launcher, a few niche features are available but hidden. So the shipped application does more than its documentation says, and the repository gives no way to find out which features those are short of installing the app.

Official sources

  1. License: GPL-3.0
  2. Project website
  3. README
  4. Releases
  5. tanujnotes/Olauncher on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/tanujnotes-olauncher.svg)](https://hysenlabs.com/projects/tanujnotes-olauncher)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/tanujnotes-olauncher.svg)](https://hysenlabs.com/projects/tanujnotes-olauncher)

Was this useful?