Android-ZBLibrary: an MVP framework that stopped publishing at release 21.0
An Android MVP framework with the most comprehensive demos, most detailed documentation, simplest usage and strictest code among domestic Android open-source UI frameworks.
At a glance
- What is it?
- An Android MVP framework of base classes, one hundred style entries and thin wrappers over OkHttp, Glide, FastJson and a patched ZXing fork. Its newest release is from August 2019 while the repository kept taking commits through October 2026.
- Who is it for?
- ZBLibrary is a workable reference for an Android app that has decided to own its whole UI baseline, because the shared style file, the hand pasted manifest entries and the okio.jar obligation are all stated plainly, and the classes named in its credits are enough to build a screen. Two things need settling before anyone adopts it.
- 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 35 days ago.
- What is it written in?
- Mainly Java, 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
- TommyLemon/Android-ZBLibrary5,604 ★ · -1
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| TommyLemon/Android-ZBLibrary | 5.6k | 5.6k |
-1 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Seven years of commits with no release past 21.0
Version 21.0 was published on 2019-08-20 and its note is a user interface feature: custom BaseTabActivity and BaseTabFragment with a TopTabBar. Before it, 20.0 on 2019-06-22 added a thread pool wrapper class and better adaptation to full screen displays, and 19.2 on 2018-12-02 added the importantForAutofill attribute for input boxes. That is the entire recent release list, and it stops more than seven years before the newest recorded push on 2026-10-11.
The repository itself still carries a complete Gradle project at its root: build.gradle, settings.gradle, gradle.properties, a gradle directory, and both gradlew and gradlew.bat. So the code moved while the published artifact did not. Anything consumed as a versioned dependency is therefore pinned to a 2019 build, and the two paths drift apart without a marker: no release note tells a reader what master gained after August 2019, and no later tag records where the version and the tree stopped agreeing.
Two documented ways in, and a manifest you paste yourself
The initialization section assumes a specific shape for the host app. It takes the demo's Application class, zblibrary.demo.application.DemoApplication, as given, and expects it to be registered in AndroidManifest.xml already:
<application
android:name="zblibrary.demo.application.DemoApplication"
...
>
</application>From there a project picks one of two doors. The first is to extend the framework's own class:
public class DemoApplication extends BaseApplication {
...
}The second keeps your own Application and calls the initializer from onCreate:
public class DemoApplication extends Application {
@Override
public void onCreate() {
super.onCreate();
BaseApplication.init(this);
}
...
}Permissions and Activity declarations are not printed for the reader. The guidance is to copy the relevant <uses-permission/> and <activity/> entries out of ZBLibrary's own AndroidManifest.xml into yours. That puts the effective permission set of an app in the hands of whoever remembers to paste, with no manifest step in the framework to catch what was left behind.
okio.jar is the failure the compiler cannot report
One of the libraries in the credits section carries a warning about its own packaging. OkHttp is wrapped by HttpManager, which adds support for self signed HTTPS, and HttpRequest in the demo app is offered as the usage example. Directly beneath that pairing sits a note about okio.jar: it is part of OkHttp, it must not be removed, and deleting it produces no error in the code while it does fail at runtime.
That single line describes the entire failure surface. Nothing in the sources breaks, the build succeeds, and the failure appears later on a device, which makes it the kind of problem that gets misfiled as a framework bug. It is a packaging obligation carried by hand rather than enforced by anything in the project. The README's related reading list also points to a separate post about implementing self signed SSL certificates on Android in ten minutes, which is where the HTTPS behaviour of the wrapper is actually worked out.
QR scanning runs on a slimmed fork that was patched in place
Scanning is not delegated to an upstream library as published. ZBLibrary credits ZXingLib, written by a different author, as a slimmed version of the official ZXing QR code library, and states that modifications were made to it before it became the project's QRCodeLibrary. That relationship shows up in the repository layout: a QRCodeLibrary directory sits at the top level next to the ZBLibrary module, so the scanning code is a vendored and locally edited tree rather than a dependency resolved by version.
The consequence is narrow but real. Fixes, format additions or platform work done upstream in ZXing do not arrive on their own, because what ships here is a fork that has already diverged, and no note in the project explains how the two are resynchronized. Anyone scanning codes in production ends up owning that divergence.
The two cache clearing scripts are Windows batch files
Two files at the repository root exist for one job, clearing build caches: clearAllBuildCache.bat and clearAppBuildCache.bat. Both are Windows batch scripts, and neither has a shell equivalent beside it. That sits oddly against the rest of the project, which is otherwise platform neutral. The Gradle wrapper ships both gradlew and gradlew.bat, and the build definition is plain build.gradle alongside settings.gradle and gradle.properties.
So the build toolchain tries to work for everyone on a Mac or a Linux box, while the two housekeeping helpers only run under cmd.exe. A developer elsewhere gets the standard Gradle clean flags and loses the shortcut the author relies on day to day. Nothing in the project is broken by this, but it does tell you which machine the workflow was written on.
Model code comes from a second repository, and the framework says models are unnecessary
The framework gives two different answers to the same question about model classes. One is Entry<K, V>, a two variable Model or JavaBean promoted as the reason such classes no longer need to be written by hand. The other is APIAuto, a separate project at github.com/TommyLemon/APIAuto, which generates the code that wraps a request into JSON, the code that parses the response JSON, and the Model or JavaBean itself.
Adopting the full data path therefore means leaving this repository for another one. The demo set reflects that pairing: beside ZBLibraryDemoApp there is APIJSONApp, and of the two downloadable APKs one is labelled as APIJSON plus ZBLibrary. ZBLibrary's own JSON class is described as a thin wrapper over FastJson whose purpose is to prevent parse exceptions, so JSON handling sits between the generator that writes the code and the wrapper that runs it.
One styles.xml holds the UI baseline, and the swipe back gesture is gone
Most of the framework's appearance lives in a single resource file. More than a hundred Style entries in res/values/styles.xml are promoted as the way to set View attributes on one line and unify the interface at once, which means the look of every screen in an app inherits from a shared list that each project is expected to edit.
Two base classes supply the window treatment. SystemBarTint is applied inside BaseActivity to produce the immersive status bar, and BaseView is offered as the shortcut for writing custom Views. BaseHttpListActivity and BaseHttpRecyclerActivity carry the HTTP list and paging behaviour, with SmartRefreshLayout built into the latter for pull to refresh and load more. The README also promotes a new gesture, announcing that it makes side swipe back and global right swipe back old news.
Adoption is a self reported list of nine organizations and a group chat
There is no adoption figure to check here. A registration section asks readers whether they are using ZBLibrary and links an issue for answers, and next to it sits a hand maintained list of nine organizations written in Chinese legal company form. The names carry their own geography: one begins with 深圳, one with 浙江, two with 杭州 and a third gives 杭州 in brackets, two with 山东, one with 佛山市, and the last is a hospital, 宝鸡中心医院. Above the names sit logo links rather than identifiers, so no entry can be tied to a shipped product or a version.
The README also carries a badge linking to a program page on whitehub.net. Contact runs through QQ groups: one number is marked new and older ones are marked full. Everything claimed here is self reported.
Editorial conclusion
ZBLibrary is a workable reference for an Android app that has decided to own its whole UI baseline, because the shared style file, the hand pasted manifest entries and the okio.jar obligation are all stated plainly, and the classes named in its credits are enough to build a screen. Two things need settling before anyone adopts it. First, decide whether you build against release 21.0 from 2019 or against master, since the newest tag is from August 2019 and the newest recorded push is from October 2026, with nothing in between marking where the two parted. Second, accept the QR code path as a fork you now maintain yourself. Teams that need a published artifact, a resolved dependency version, or an upstream security feed for their scanner should look elsewhere.
Frequently asked questions
Is release 21.0 the last version of Android-ZBLibrary, or does the code move on without a release?
The newest recorded release is 21.0 from 2019-08-20, which added custom BaseTabActivity and BaseTabFragment with a TopTabBar. The newest recorded push is 2026-10-11 and the Gradle project is still at the repository root, so master has moved on without a newer tag.
What does Android-ZBLibrary ask me to change before the base classes work in my app?
Register your Application class in AndroidManifest.xml, then either extend BaseApplication or keep your own Application and call BaseApplication.init(this) inside onCreate. Permission and Activity declarations are not printed for you, the guidance is to copy the uses-permission and activity entries out of the framework's own manifest.
Does Android-ZBLibrary ship its own QR code scanner instead of using ZXing directly?
It does. A QRCodeLibrary directory sits at the top level next to the ZBLibrary module, and the credits say it was built from ZXingLib, which that author describes as a slimmed version of the official ZXing library, then modified further before being adopted.
Which libraries does Android-ZBLibrary wrap, and what do the wrappers change?
Glide for image loading, OkHttp inside HttpManager with support for self signed HTTPS, FastJson inside a JSON wrapper meant to prevent parse exceptions, SmartRefreshLayout built into classes such as BaseHttpRecyclerActivity, and SystemBarTint used in BaseActivity for the immersive status bar.
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/tommylemon-android-zblibrary)Star history chart for your README
[](https://hysenlabs.com/projects/tommylemon-android-zblibrary)Was this useful?