AndroidEasterEggs: A Single APK for Every Android Version's Hidden Toy
Android Easter Egg Collections. The goal is to enable most devices to experience different versions of the Easter eggs with minimal modifications to the Easter egg\'s code.
At a glance
- What is it?
- This Kotlin project repackages the official Android Easter eggs into one app, aiming for broad device compatibility with minimal code changes. The trade-offs involve update signing conflicts and the alpha channel's unfinished features.
- Who is it for?
- Adopt AndroidEasterEggs if you want a single app to explore Android's hidden Easter eggs on devices that don't have them, and you accept the risk of alpha bugs and the Play Store update conflict. Avoid it if you need a production-grade app with stable features or if you rely on Play Store auto-updates.
- Can I use it commercially?
- Yes. Apache-2.0 is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
- Is it still maintained?
- Yes. The repository last received commits 1 day 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 September 14, 2026, and from our analysis. They are not legal advice.
DEEP OPEN-SOURCE ANALYSIS
What Problem It Solves
Android's Easter eggs are hidden animations and games tucked inside the OS, accessible only by tapping the Android version number repeatedly in Settings. They vary by Android version, and many devices, especially those with custom ROMs or older versions, never see them. This project collects the complete code for all Android Easter eggs into a single app, so users can experience different versions without digging through system settings. The stated goal is to enable most devices to run these Easter eggs with minimal modifications to the original code. It targets enthusiasts, tinkerers, and anyone curious about Android's hidden features who wants a convenient way to access them.
How It Works: Repackaging AOSP Code
The project takes the Easter egg code from AOSP, the Android Open Source Project, and repackages it into a standalone Android app. The README credits AOSP as a source, and the package name com.dede.android_eggs suggests a custom application ID. The core mechanism is likely to embed each Easter egg's activity or view into a single APK, with a launcher that lets you pick which version to view. The emphasis on minimal modifications means the original code is preserved as much as possible, which helps maintain behavior but might limit integration. The app is written in Kotlin, so the wrapper and UI are modern, but the Easter egg logic itself is probably Java or Kotlin from AOSP. The repository structure isn't detailed in the README, so the exact data flow is not fully visible, but the approach is clear: collect, package, and present.
Getting It Running: Install Sources and Signing Caveat
You can get the app from several sources: the GitHub releases page, F-Droid, IzzyOnDroid, and the Google Play Store. There is also a Pgyer link for the alpha version. The README warns about a significant caveat with the Play Store version: it uses Play App Signing, which means updates from other sources will fail. To switch sources, you must uninstall the Play Store version and install the other version, and vice versa. This is a real friction point for users who want to try the alpha or sideload updates. For F-Droid and IzzyOnDroid, the app is likely signed with a different key, so the same conflict applies. The release tags are v5.4.0, v5.3.0, and v5.2.0, so the project is actively versioned. To install, download the APK from your chosen source and allow installation from unknown sources if not using Play Store.
The Alpha Channel: Bugs and Unfinished Features
The README explicitly states that Pgyer hosts the Alpha version, which contains unfinished features that are not final and may be removed, reworked, or replaced without notice. Alpha versions may contain bugs. This is a genuine limitation: if you install the alpha, you are signing up for instability. The project's main branch is the stable channel, but the alpha is a separate track. For a project that aims to provide a polished experience, this split means you have to choose between stability and the latest changes. The release history shows a rapid cadence, with v5.4.0 on August 4, 2026, and v5.3.0 on July 15, 2026, so the stable channel is also moving fast. This could be good for getting new Easter eggs quickly, but it also means more frequent updates and potential regressions.
Limitations and Wrong Use Cases
The most obvious limitation is the update conflict caused by Play App Signing. If you install from Play Store, you cannot update from GitHub or F-Droid without uninstalling first, which loses app data. This makes the app inconvenient for users who like to switch sources. Another limitation is that the project only covers Easter eggs, not other hidden features or system tweaks. If you want a general Android customization tool, this is the wrong tool. Also, the README does not specify which Android versions are supported or whether all Easter eggs are included. The description says 'all Android Easter eggs,' but without a version list, you cannot be sure your device's specific Easter egg is present. The alpha channel's unfinished features could break the app entirely, so it is not suitable for users who need a reliable daily driver.
Alternative: The Official AOSP Easter Egg
The natural alternative is the Easter egg that ships with your Android device. Every Android version includes one, accessible by tapping the build number in Settings. The difference is that the official Easter egg is integrated into the OS, requires no installation, and is always up to date with your system. It is also the source code that this project repackages. However, the official Easter egg is limited to your current Android version; you cannot access past versions without this app or a custom ROM. Another alternative is to flash a custom ROM that includes multiple Easter eggs, but that is a much heavier modification. AndroidEasterEggs offers convenience and breadth, but the official method is simpler and conflict-free. If you only care about your device's current Easter egg, the official method is sufficient.
Maintenance and License Implications
The project is actively maintained, with the latest release v5.4.0 on August 4, 2026, and a consistent release pattern every two to three weeks. This suggests a healthy development cycle, but it also means you will need to update frequently to get fixes and new Easter eggs. The license is Apache-2.0, which is permissive and allows you to use, modify, and distribute the code, including commercially, as long as you include the license notice. However, the Easter egg code from AOSP is also under the Apache License, so there is no conflict. The README thanks AOSP and translation contributors, and there is a contribution guide for reporting issues or translating via Crowdin. For users, the maintenance cost is low: just install updates. For developers, the project's structure is not detailed in the README, so contributing might require reading the source code. The license is a plus for anyone wanting to fork or extend the project.
Editorial conclusion
Adopt AndroidEasterEggs if you want a single app to explore Android's hidden Easter eggs on devices that don't have them, and you accept the risk of alpha bugs and the Play Store update conflict. Avoid it if you need a production-grade app with stable features or if you rely on Play Store auto-updates. Before installing, verify whether your device's Android version is supported, and check the release notes for known issues. The project is actively maintained, with v5.4.0 released in August 2026, so the code is likely fresh, but the alpha channel is explicitly unfinished.
Community notes