WikiReader is an Android reader for Wikipedia that loads the text before anything else

Text first, everything else after

The feature list opens with the thing that defines the app.

Fast loading: the article text is loaded before anything else, so you can get to reading, quick. That is stated as the first feature and it explains a lot of the rest of the design, because the other features are mostly things that could have been loaded first and were not.

The app is a lightweight Android app for reading Wikipedia articles distraction-free. It supports light mode, dark mode, Material You dynamic colors and over 300 Wikipedia languages, and it is written in Kotlin with Jetpack Compose. The topic tags confirm the stack: jetpack-compose, material-3, material-3-expressive, kotlin, wikipedia and wikipedia-api.

The screenshots are hosted in the fastlane metadata directory under the en-US locale, which tells you the app has a fastlane setup for store listings rather than just a manual build.

The library credits in the README are specific enough to be useful. Retrofit 2 for REST APIs, OkHttp for networking, Coil for loading images from the web, MaterialKolor for custom color themes, ComposeCharts for the view-count history graph in the feed, and Latex2Unicode for converting math into Unicode text.

That last one connects directly to the math expressions feature, which is described as viewing properly rendered mathematical expressions for easily reading mathematical articles. The Wikipedia API returns LaTeX in the wikitext, and Latex2Unicode is what turns that into something a phone can display as text.

The licence is GPL-3.0, the minimum API level is 26 according to the badge, and the last push to the repository was on 2026-10-16 with the newest tagged release being v2.5.5 from 2025-10-09.

Three distribution channels with different update speeds

The Download section gives three ways in, and the README is clear that they are not equivalent.

F-Droid is marked recommended. The app is on the official F-Droid repository, and the note is that updates on F-Droid are generally a week late. That lag comes from the review process F-Droid applies to each new build, and it is the price of a repository that audits what it ships.

IzzyOnDroid is the second option, and the note says you can download WikiReader from the IzzyOnDroid repository for faster updates.

Obtainium is the third and is also marked recommended. You add the GitHub repository on Obtainium and it fetches updates directly from the GitHub releases, which the README calls the fastest way to install and update WikiReader.

GitHub releases are the manual fallback. The README describes manually downloading and installing APKs from the Releases section of the repository, and says plainly that this method is not recommended and that Obtainium should be used instead.

That ordering is a good illustration of how an independent Android developer distributes today. The F-Droid route buys you a vetted store at the cost of a week. The Obtainium route buys you the newest build with you doing the verification yourself. The manual APK route is the one everybody ends up using at least once.

The wiki, of course, is not the only source of articles. The app talks to the Wikipedia API, and the README links the API topic tag, so the content comes from Wikimedia's own endpoints rather than from any local copy.

Verifying the APK yourself

The README includes a tip for verifying the APK downloaded from Obtainium or GitHub, and it gives the actual signing certificate fingerprints to check against.

SHA1: B1:4E:17:93:11:E8:DB:D5:35:EF:8D:E9:FB:8F:FF:08:F8:EC:65:08
SHA256: 07:BE:F3:05:81:BA:EE:8F:45:EC:93:E4:7E:E6:8E:F2:08:74:E5:0E:F5:70:9C:78:B2:EE:67:AC:86:BE:4C:3D

It links the apksigner documentation for the verification command, and adds that the SHA256 and MD5 hashes of the individual APK files are available in the checksum.txt file for each release.

This is the part of the distribution story that matters for the Obtainium route specifically. Pulling an APK directly from a GitHub release is installing a binary from a URL with no store in the middle, so the only thing standing between you and a tampered build is checking the signature yourself. Publishing the fingerprints in the README means the check does not depend on trusting the release page at the moment you download, which is the sensible way to do it.

The two channels where verification matters least are the ones where a repository is already in the loop. On F-Droid, the repository does the vetting. On Obtainium, you are the one doing it, and the README gives you the fingerprints to do it with.

The reading features that are not about the web

Away from the article text, the feature list covers the parts that make it an app rather than a page.

The Feed feature covers reading the article of the day, finding trending articles and getting up to speed on the news with the Wikipedia Feed. That is the entry point for someone who opens the app without knowing what they want to read.

The article image feature shows an image of the topic taken from the Wikipedia page, and clicking it enlarges the image and opens it full screen. The random article button is the other end of the spectrum, for the feeling lucky case.

Save articles downloads them to the device for offline reading, which is the feature that makes the app usable on a train or a plane.

One-handed use comes from the floating action buttons at the bottom, which the README describes as giving a complete one-handed experience. Immersive mode hides UI elements while scrolling.

The data saver is described as saving a limited data plan by loading text only, which pairs with the fast loading feature rather than contradicting it: the same ordering decision that gets you to the text quickly is what lets you ask for less of everything else.

Then the display controls. Customizable colors means choosing from light and dark themes and customizing the Material 3 color palette, with MaterialKolor doing the work of deriving a palette. Customizable font size lets you set your own comfortable size. The app is described as designed according to the latest Material 3 Expressive design guidelines, and the smooth animations are listed as their own feature.

The repository layout of a modern Android app

The top level entries show what a current Android project looks like, and they are worth reading as a checklist for anyone building one.

There is the app module, a baselineprofile directory for Android baseline profiles, and the standard Gradle files: build.gradle.kts, settings.gradle.kts, gradle.properties, gradlew and gradlew.bat for the wrapper, and a gradle directory.

Then the release and store infrastructure. The fastlane directory holds the metadata, including the screenshots linked from the README, and weblate holds the translation configuration that matches the Hosted Weblate project. There is a discoverium.yml, which is the metadata file F-Droid reads to describe the app in its repository.

The automation is visible too: a renovate.json for dependency updates and a .github directory for the workflows.

What is missing from the list is worth noting as well. There is no docs directory and no README for contributors in the top level entries, and the project has no separate API or SDK module in the listing, so the Wikipedia access is part of the app module rather than a reusable library.

The translation arrangement is the part most open source Android projects get wrong, and this one has it right. Weblate hosts the translations, the weblate directory in the repository holds the config, and the README says you can contribute by translating into a language you know even if you are not a developer. The badge at the top tracks the translation progress.

Where WikiReader is the wrong tool

The first limitation is the scope of the content. This is a reader for articles, and the Wikipedia project contains much more than articles. History pages, talk pages, the citation tools, the edit interface, the structured data and the category graph are all out of reach, because the app is built around the article reading experience rather than around the wiki.

The second is that the reader is a client, so the article quality and the language coverage are the upstream's. The over 300 languages figure comes from Wikipedia's own editions, and the app inherits whatever an edition contains, including the unevenness of smaller language versions. A reader is a better way to read an article than a browser, but it does not make the article better.

The third is the platform. Android only, API 26 and above. There is no iOS version, no desktop version and no web version in this repository, so if your Wikipedia reading happens on a laptop, this does not help.

The fourth is the maintenance gap. The last push was on 2026-10-16, which is recent, but the newest tagged release is v2.5.5 from 2025-10-09, a year earlier. That gap is what produces the F-Droid lag the README mentions, and it is worth watching if you rely on offline downloads or on the data saver mode.

The fifth is that the app is funded by donations. The README points at GitHub Sponsors and a Buy Me a Coffee page. That is normal for this kind of project and it is not a red flag, but it does mean the roadmap is one person's spare time.

How it compares with the Wikipedia app and a browser

There are two other ways to read Wikipedia on an Android phone, and the difference between them is about focus rather than capability.

The official Wikipedia app is a full wiki client. It gives you the article reader, plus editing, history, talk pages, the donate flow and the account features, and it is maintained by the Wikimedia Foundation with the same release process as their other apps. What it does not do is strip the interface down to the text. It is a general purpose client for a general purpose site.

A browser gives you the mobile web experience, which the Wikimedia teams have improved considerably, and it gives you the entire web interface including the editor, the API docs and the sandbox. What it does not do is give you a saved article for offline reading, a data saver mode, or the Material You integration.

WikiReader sits between them. It takes the article and drops everything around it, then adds the things a browser cannot offer: saved articles, a text-only data saver, per-article offline availability, dynamic colour from the system, a font size control, and rendered math.

That math feature is the one that changes the calculus for a specific audience. A browser renders LaTeX through MathJax with a network fetch and a page-level script; WikiReader converts the LaTeX to Unicode text through Latex2Unicode, which means a mathematical article reads correctly without a script and without extra requests.

The honest framing is that this is a reading app, not a Wikipedia replacement. If your use is reading, it is better than both alternatives. If your use is contributing, it is the wrong tool entirely, and the Wikipedia app is the one to install.

Editorial conclusion

WikiReader fits an Android user who reads Wikipedia in short sessions and wants the text without the surrounding furniture, particularly on a device with limited data where the data saver mode matters or where offline articles are useful on a commute. It does not fit someone who needs the full breadth of the Wikipedia ecosystem, since the app is a reader rather than a browser, an editor or a research tool with the history, talk pages and citations in depth. Before installing, pick your distribution channel deliberately, because the README states that F-Droid updates are generally a week late while Obtainium tracks GitHub releases directly, and verify the downloaded APK against the SHA256 signing fingerprint the README publishes.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. nsh07/WikiReader on GitHub
4. README
5. Releases