# MewX/light-novel-library_Wenku8_Android: a Wenku8 reader with a self-hosted API relay

> A GPL-2.0 Android light novel reader for Wenku8.com, started in 2014 and last pushed on 2026-09-05. It solves one narrow problem: reaching a site whose API was abused into closing, by routing requests through a Cloudflare Worker relay the maintainer operates.

**MewX/light-novel-library_Wenku8_Android** — [CASUALLY MAINTAINED] 轻小说文库 (Wenku8.com) 安卓版第三方公益App，始于2014年的初版Material Design风格、非盈利、Play Store上安装包最小的轻小说阅读器 (light novel reader)。目前网站的API由于被大量滥用，已更新成我自己架的 Cloudflare Worker API 中继节点，不然的话网站关闭API就全军覆没了。

- Repository: https://github.com/MewX/light-novel-library_Wenku8_Android
- Website: https://wenku8.mewx.org
- Stars: 3,037 · Forks: 316
- Language: Java
- License: GPL-2.0
- Published: 2026-09-24 · Updated: 2026-09-24 · Language: en
- Canonical page: https://hysenlabs.com/projects/mewx-light-novel-library-wenku8-android

## What the Wenku8 Android reader actually solves

Wenku8.com is a Chinese light novel site. This repository is a third-party Android client for it, not a general ebook reader. It began in October 2014 as the maintainer's first Android app, was rewritten into Material Design in 2015, and is released as a non-profit app on the Play Store under the package name org.mewx.wenku8. The README frames the whole project as an interest project and a portfolio piece, which explains why the code style is uneven: the author states plainly that 1.x sources partly copy the older 0.5.2.1 code, and that patterns such as an isLoading field declared outside the AsyncTask class survive in the old files.

The audience is narrow. You need to read Chinese light novels from Wenku8.com, you want a native Android client rather than a browser, and you accept that the app's data source is not the site's own public API. That last point is the real subject of this repository, and it is why the project still exists in 2026.

## The Cloudflare Worker relay is the load-bearing part

The README states that Wenku8's API was abused at scale, and that the site would have shut the API down entirely, which would have taken every third-party client with it. The maintainer's response was to stand up a Cloudflare Worker as an API relay node and point the app at that instead. So the data flow is: app, then the maintainer's Worker, then Wenku8. The app is not talking to the origin directly any more.

That single decision changes what you are depending on. Availability is now tied to one person's Cloudflare account and to their willingness to keep paying for and operating the relay. The README does not describe a fallback path, a configurable API base URL, or what happens when the Worker is unreachable. It also does not document rollback if a relay change breaks older installed versions. For a reader app this is a reasonable engineering trade against losing the API completely, but it is a centralised dependency in a project whose selling point is being a free client for a third-party site.

The rest of the architecture is conventional for its generation. The README lists Volley among the topics, third-party libraries are pulled in through Gradle dependencies and deliberately excluded from obfuscation, and the README notes that this lowers encryption strength in exchange for easier development. Screens are mapped to concrete files: WelcomeActivity for the splash, NavigationDrawerFragment for the side menu, FavFragment for the local bookshelf, SearchActivity and SearchResultActivity for search, and RKListFragment for ranking lists, each with a matching layout XML under layout/.

## Installing the APK and building from studio-android/

The README's install path is the Play Store badge, which links to the listing for org.mewx.wenku8. That is the practical route for a reader: no build toolchain, and the release notes show v1.30 published on 2026-08-29.

If you want to build it, the README is explicit that studio-android/ holds the 1.x sources and that this module compiles and runs. The other two Android directories are historical: eclipse-android/ is the 0.5.1.0030 source with the API portion stripped, so the README says a build from it cannot fetch data normally, and eclipse-android-old/ is the 0.5.2.1 archive copied out of the private repository. Clone the repository with submodules, since .gitmodules is present at the top level and the project depends on it.

```bash
git clone --recurse-submodules https://github.com/MewX/light-novel-library_Wenku8_Android.git
cd light-novel-library_Wenku8_Android
```

Open the studio-android directory in Android Studio and let Gradle resolve the dependencies declared in the build files. The README does not list a required JDK, Gradle or Android SDK version, so expect to reconcile the Gradle wrapper and compile SDK yourself if the project has aged past your installed toolchain.

```bash
cd studio-android
./gradlew assembleDebug
```

The README does not document the output path or a signing configuration for release builds. The first real use is the same either way: launch the app, land on the welcome screen, then use the drawer to reach the latest-updates list, search, or the ranking lists. Anything you want to keep should be added to the local bookshelf, because that is the only list the app owns locally.

## Where the Wenku8 reader is the wrong tool

The clearest limitation is platform. This is an Android application in Java; the README describes no iOS target and no web client, so the related search for an iOS version has no answer inside this repository. If your reading happens on an iPhone or a desktop, this project cannot help you.

The second limitation is scope. It reads one source. The README's compatibility section explains how to make documents from other libraries work with the app, but that is about the local archive format, not about adding a second catalogue. If you want one reader for several sites, this is not that.

The third is the relay, already described, plus a milder one: the README says third-party libraries are excluded from obfuscation, so a build is easy to inspect. That is fine for an open source reader and a poor fit if you were hoping to wrap it in something commercial.

Finally, the maintenance signal deserves a plain reading. The repository is not archived, and the last push was on 2026-09-05, which is recent. But the project's own description labels it casually maintained, and the README opens with a note about a historical issue. Releases are irregular: v1.28 on 2026-02-24, v1.29 on 2026-03-07, then v1.30 on 2026-08-29. Treat it as a maintained hobby project, not a product with a support commitment.

## Alternatives and how their approach differs

The honest alternative is not another Wenku8 client, it is a general-purpose Android reader that takes the source as configuration. Legado is the obvious comparison point: it is built around user-imported book sources, so the catalogue logic lives in rules you supply rather than in the app, and adding or replacing a source does not require a new APK. This project takes the opposite approach. The Wenku8 API and its relay are compiled into the app, which is why an upstream API shutdown required a maintainer-side change and a new release rather than a rule edit.

That difference cuts both ways. A source-rule reader survives an endpoint change if someone publishes an updated rule, and it can read many sites. This app gives you a fixed, curated experience for one site, with a bookshelf, ranking lists and a search flow the maintainer designed, and it does not ask you to configure anything. If Wenku8 is the only site you read, the compiled approach is simpler. If you read three sites, it is the wrong shape.

Within this repository there is also a version choice. The README treats 0.5.2.1 as the archive branch, copied out of the private repository, and 1.x as the Material Design line under active use. For a new install, 1.x is the one the README points at.

## Licence and what upgrading costs you

The project is GPL-2.0. If you fork it or ship a modified APK, the copyleft terms travel with the code, and the README's own note that some 1.x sources are copied from the 0.5.2.1 branch means you are dealing with a single GPL-2.0 codebase rather than a mix of licences. This is not legal advice; read the LICENSE file at the repository root and the FOSSA badge report if you plan to redistribute.

Upgrade cost is low in normal operation because the app is distributed through the Play Store and the release cadence is a few builds a year. The expensive upgrade is the one nobody schedules: if the relay changes or Wenku8 alters what its API returns, the fix has to come from the maintainer as a new release. There is no plugin layer for you to patch locally, and the README does not describe a configurable endpoint, so a self-hosted fork would mean editing the source and shipping your own build. Budget for that possibility before you make this your only way to read the site.

## Conclusion

Adopt it if you read Wenku8.com on Android and accept that fetching depends on a relay operated by one person; the Play Store listing is the shortest path and studio-android/ is the only module the README says compiles and runs. Skip it if you need iOS, a general-purpose reader for several sources, or an offline-only library, because the 0.5.2.1 archive is the only fully private-code branch and the README does not describe an offline mode. Before relying on it, confirm the relay in the current release still answers, and check that GPL-2.0 distribution terms fit how you plan to redistribute the APK.

## FAQ

### Is MewX/light-novel-library_Wenku8_Android free?

Yes. The README describes it as a non-profit, completely free app, and the source is published under GPL-2.0.

### How do I install the Wenku8 reader on Android?

The README links to the Play Store listing for org.mewx.wenku8. To build it yourself, clone the repository with submodules and open the studio-android module, which the README says compiles and runs.

### Is there an iOS version of the Wenku8 reader?

The repository contains only Android sources in Java, and the README describes no iOS client or plan for one.

### Does the app talk to Wenku8.com directly?

No. The README states that the site's API was heavily abused, so the app now goes through a Cloudflare Worker API relay node that the maintainer set up.

## Sources

- [License: GPL-2.0](https://github.com/MewX/light-novel-library_Wenku8_Android/blob/master/LICENSE)
- [MewX/light-novel-library_Wenku8_Android on GitHub](https://github.com/MewX/light-novel-library_Wenku8_Android)
- [Project website](https://wenku8.mewx.org)
- [README](https://github.com/MewX/light-novel-library_Wenku8_Android/blob/master/README.md)
- [Releases](https://github.com/MewX/light-novel-library_Wenku8_Android/releases)

---

Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/mewx-light-novel-library-wenku8-android