Forewords vs Oku: Which Minimal Book Tracker Fits You? (2026)

Oku is a good-looking book app, and the community consistently says so. Clean typography, calm colour palette, not-a-pixel-wasted layout. You see Oku recommended in Reddit threads and blog roundups specifically because it “feels like the bookshelf I wish I had,” which is earned in a category dominated by cluttered UI.

Forewords’s design philosophy is a different flavour of minimal: dark-first, literary, opinionated. Instead of whitespace and airy typography, it leans into the feel of a physical library at night — warm accents, shelf metaphors, atmospheric backdrops. Both end up in the same neighbourhood (minimal, considered, not-startup-y) but from opposite directions.

If you sit down and open Oku after a day of looking at cluttered apps, it feels like a breath. If you sit down and open Forewords, it feels like settling into a reading chair. Pick the one that matches how you want to feel when you log a book.

This is the main functional gap between the two apps. Oku’s positioning is minimal tracker + bookshelf + UGC. Discovery happens through other people’s collections and reviews, not through an algorithm tuned to your taste. That’s fine — it’s a deliberate choice — but it means if you’re looking for a book recommendation engine, Oku isn’t really trying to be one.

Forewords’s recommendation system runs embeddings on a ~51k-book catalogue, clusters your reading into 4–7 taste centroids, and uses an LLM to explain why a specific book might resonate. It’s closer to what you’d get from a thoughtful librarian who has actually read what you’ve read than from a collaborative-filter recommender.

If discovery matters to you — if you finish a book and immediately want the next one that fits — Forewords is going to do more for you than Oku. If you mostly find books through friends, bookstagram, or your own wishlist, the discovery gap probably doesn’t matter and Oku’s other strengths win.

Oku’s collections are a genuine feature, not just a folder abstraction. They live on public URLs, other readers can follow them, and there’s an emergent curator scene around them. Roughly 7,000 user-created collections are indexed on the open web. If you love the idea of building a public bookshelf that strangers discover and follow, that’s a real Oku-specific use case.

Forewords has custom shelves with tag rules — you can build a shelf like “slow-burn romantasy with unreliable narrators” by combining tags rather than dragging books. Useful for expressive library structure, but they’re private by default. The social-curation angle isn’t something Forewords is trying to do.

Direct answer: if shareable collections are a dominant factor for how you want to use a book app, Oku is the right pick.

Oku is web-first with an iOS app, and has no Android app. Forewords is Android-first today with iOS mid-2026 and no full web app. These are opposite tradeoffs, so the right pick depends on where you actually read.

If you want to track books from a laptop browser during the day and pick up on your iPhone on the train, Oku does that cleanly. Forewords doesn’t match that workflow yet, and that’s an honest gap. The web app is on the Forewords roadmap but isn’t available yet.

If you’re an Android reader, Oku isn’t available to you at all. Forewords is the clean answer in that direction.

Oku surfaces UGC publicly by default — reviews, collections, and some profile metadata live on the open web as indexed URLs. That’s actually a big part of how discovery happens on Oku. It’s not a privacy failure; it’s a product choice.

Forewords has no public profiles. Your reading doesn’t show up on indexed URLs. No social features, no ads, no follow-the-reader graph. For readers who want their reading life fully private — not hidden in a friends-only group, but actually private — Forewords is the straightforward answer.

One is optimised for a public-bookshelf use case; the other is optimised for a closed-door reading life. Neither is right or wrong; they answer different questions.

If you’re coming from Goodreads, Forewords has the smoothest path: WebView import signs you in and pulls the library in one tap. Oku supports CSV import from Goodreads — works, takes more steps.

Moving between Forewords and Oku directly is harder because Oku doesn’t have a public CSV export at the time of writing. The cleanest approach is to export from whichever app your library originally came from (Goodreads, StoryGraph, spreadsheet) and import into the other tool.

My practical recommendation: try both for a few weeks on your Goodreads export. The answer for which one you actually keep opening usually becomes obvious inside two weeks.