FlappyBird keeps the APK under 100 KB and gives the rights to DotGEARS
Less than 100 Kilobytes. Works for Android 5.0 and above
At a glance
- What is it?
- A Flappy Bird clone written in C and packaged for Android with OpenGL ES 2 and the native activity API. Its first attempt used C++ with ImGui and produced a one megabyte APK that crashed, and the repository ships no license file at all.
- Who is it for?
- Read it as a build size study rather than a game to ship: the interesting part is a C library on the native activity API that stays under 100 KB, and the price of that choice is that you assemble the toolchain yourself from a six-variable .env file, with no gradle wrapper promise and no signed release to download.
- Can I use it commercially?
- Not without permission. GitHub finds no licence file in the repository, and without a licence all rights are reserved by default: you may read the code but not reuse it. Check the README, or ask the authors, before using it.
- Is it still maintained?
- Activity is slowing. The repository last received commits 6 months ago.
- What is it written in?
- Mainly C, 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.
Star history
- VadimBoev/FlappyBird2,444 ★ · -1
| Repository | 2026-09-30 | 2026-11-15 |
|---|---|---|
| VadimBoev/FlappyBird | 2.4k | 2.4k |
-1 Stars in the last 46 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The first attempt was C++ with ImGui and it failed three ways
The history section starts in 2021 with rawdrawandroid, then Raylib, then a first attempt at a game in C++ using ImGui. That attempt is described as failing on three counts: the APK was around 1 MB, the game crashed, and the package contained only the armeabi-v7a library, with a note that Google's 2022 requirements demand arm64-v8a as well. Those three dates do not sit together neatly, because a 2021 attempt cannot have been broken by a rule published in 2022. What replaced it is a C implementation on OpenGL ES 2 with shaders and Android Native Activity, packaged under 100 KB. The September 2024 entry explains the switch as seeing Flappy Bird written in C# in the Raylib Discord channel and deciding to beat its APK size.
The rights line names DotGEARS and the tree has no license file
The top-level entries are .env.example, .gitattributes, .gitignore, BUILDING.md, FlappyBird.sln, the FlappyBird directory, README.md, README_RU.md and flappy.gif. There is no LICENSE file among them, and the licence recorded for the project is unknown rather than a standard identifier. The copyright section is one sentence: no copyright is claimed, and the rights to the game and the resources belong to DotGEARS. So the artwork and audio carry someone else's ownership while the code carries no grant at all, which leaves a fork or a reuse without a stated permission to point at. The inspiration list names rawdrawandroid, Flapper, Raylib and ImGui as the projects the work grew out of.
The .env template asks for the SDK path twice and signs with one variable
Six variables sit in .env.example: ANDROID_SDK_ROOT, ANDROID_NDK_ROOT, ANDROID_HOME, KEYSTORE_PASSWORD, PACKAGE_NAME and BUILD_TOOLS_VERSION, which is pinned to 30.0.3. Three of the six are paths, and two of those three, ANDROID_SDK_ROOT and ANDROID_HOME, name the same SDK directory under two different names, so a build script has to pick one. Signing gets a single variable: KEYSTORE_PASSWORD, with no keystore file path and no key alias, while the documented output name is FlappyBird-signed.apk, which means the default build target is already a signed one. A build tool version from 2020 is what the template asks for, next to a project that says it runs on Android 5.0 and above.
The Makefile sits one directory below the .env you have to write
The Unix instructions put the two steps in different directories. Step two says to set the environment variables in a .env file in the project root, and .env.example is indeed at the top level next to FlappyBird.sln and BUILDING.md. Step three then moves down before building:
cd FlappyBird
makeSo the configuration is written one level above the makefile that reads it, and the project has to be named twice to reach it, once as the repository and once as the directory inside it. The signed package is written to FlappyBird/app/build/outputs/apk/FlappyBird-signed.apk, which repeats the directory name because that is where the app module sits inside the nested project. The Windows path is two steps with no directory change at all: create .env from .env.example, then run build.bat, with no path given for that script.
Sound is MP3 through OpenSLES and PNGs go through upng
The implementation notes are short. It began with compiling a Hello World in C and packaging the library into an APK, which is the smallest thing that can prove the toolchain works. Audio was compressed to MP3 and played back through OpenSLES, the platform audio API rather than a library of its own. PNG decoding was handed to upng, a single-file decoder, instead of a full image library. All of that was combined with OpenGL ES 2, shaders and the Android Native Activity, which is why the game is a C library in an APK rather than an app with a managed runtime. The cost of that route is visible in the build section: a nested Gradle layout, a local makefile and an environment file the developer fills in by hand.
Three tags in three days and no changelog
The release history is three entries: v1.9 published 2026-05-15, v1.9.1 on 2026-05-16 and v1.9.2 on 2026-05-17. The numbering skips 1.9.0, and the last push to the default branch carries the same timestamp as v1.9.2, down to the second, which is what a release cut from a fresh commit looks like. None of the three carries any description text. There is no changelog file at the top level and nothing in the README about what changed between them, so what the three tags contain can only be compared by reading the diffs yourself. The version record and the documentation are two separate things here, and only one of them is in the repository.
The minimum Android version appears only in the one-line summary
The summary line above the README says the game works for Android 5.0 and above, and the rest of the file never repeats it. There is no requirements section, no mention of a minimum SDK, a target SDK or a compile SDK, and .env.example does not carry one either. What the file does state is the toolchain story, the size goal and the build steps, plus a pointer to BUILDING.md for detail and to a Telegram dev blog that runs in English and Russian. A Russian version of the README sits next to the English one as README_RU.md, linked from the first line, and flappy.gif at the root is the only visual the repository itself carries. The file closes with a star history badge and a request to star the project, so the only growth tracking on show is GitHub's own chart rather than anything the game reports.
Editorial conclusion
Read it as a build size study rather than a game to ship: the interesting part is a C library on the native activity API that stays under 100 KB, and the price of that choice is that you assemble the toolchain yourself from a six-variable .env file, with no gradle wrapper promise and no signed release to download. Before using any of it, settle the licensing, because there is no license file and the README hands the rights to the game and its resources to DotGEARS, and note that the only version record is three tags from three consecutive days.
Frequently asked questions
What is VadimBoev/FlappyBird built with?
C compiled into an Android library and wrapped with OpenGL ES 2 and shaders on Android Native Activity. Sound is MP3 played through OpenSLES and PNGs are decoded with upng. The project states the APK stays under 100 kilobytes.
How do I build VadimBoev/FlappyBird on Linux or macOS?
Create a .env in the project root from .env.example, fill in the Android SDK, NDK and keystore values, then cd FlappyBird and run make. The signed APK is written to FlappyBird/app/build/outputs/apk/FlappyBird-signed.apk.
Which Android versions does VadimBoev/FlappyBird run on?
The one-line project summary says Android 5.0 and above. The README body has no requirements section and states no minimum SDK anywhere else.
What licence covers VadimBoev/FlappyBird?
None is declared in the repository. There is no license file at the top level, the licence metadata records it as unknown, and the README says no copyright is claimed and that the rights to the game and resources belong to DotGEARS.
Why is the VadimBoev/FlappyBird APK so small?
It is C on Android Native Activity with OpenGL ES 2, with no managed runtime in the package. The earlier C++ attempt with ImGui produced an APK of around 1 MB, crashed, and shipped only the armeabi-v7a library.
Does VadimBoev/FlappyBird keep a release history?
Three tags in three days: v1.9 on 2026-05-15, v1.9.1 on 2026-05-16 and v1.9.2 on 2026-05-17. There is no changelog file at the top level and the tags carry no release notes.
Official sources
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.
[](https://hysenlabs.com/projects/vadimboev-flappybird)Star history chart for your README
[](https://hysenlabs.com/projects/vadimboev-flappybird)Was this useful?