Read You's feature list is a checklist with two boxes still open

The feature list is a roadmap in tick boxes

The features section is a markdown task list rather than prose, and it is split into done and not done.

Marked complete: subscribing to feed links, importing and exporting files in a standard subscription format, notification of new articles, article readability optimisation, full content parsing of original articles, multiple accounts, and reading aloud.

Marked incomplete: an Android widget, and then an ellipsis.

That last tick box is the honest part. A roadmap that ends in an ellipsis is a project stating that the list is open rather than pretending the two remaining items are the whole future.

So the reader gets the feature set and the author gets a to-do list in the same section, which is unusual and more useful than a marketing paragraph.

Three sync services work and four are wanted

The integration section is a second tick box list, and it is about using existing cloud accounts as data sources rather than about exporting anything.

Three are marked complete, and they are telling choices: a minimal self-hosted service, a discontinued reader whose API is still widely deployed, and another self-hosted service. In other words, the finished integrations are the ones people who already have data tend to have.

Five are marked incomplete: Miniflux, Tiny Tiny RSS, Inoreader, Feedly and Feedbin, plus an ellipsis.

Read as a set, the completed integrations are self-hosted or legacy APIs, while the incomplete ones mix self-hosted services and commercial readers.

F-Droid builds cannot upgrade to other builds

There are three download sources, and one of them comes with a restriction stated in the same paragraph.

Project releases, a chat channel, and a package repository are the three routes. Next to the package repository the readme says that builds from it cannot upgrade to other releases, and that they are compiled, signed and distributed uniformly by that project.

That is a packaging property rather than a defect, but it has a real consequence for users. If you install from there, you stay there: a later version from the project's own releases will have a different signature, and the updater will not cross that boundary.

So the choice of channel at install time is a choice about how you will be updated for the life of the installation. The readme tells you this once, in a sentence, and it is the sentence to read before tapping install.

Nightly comes out of a workflow run, with a backup warning

There is a separate section for testing builds, and it is more careful than most.

The builds include the latest features and improvements but may not be as stable as the regular releases, and they are explicitly not recommended for everyday use. They may have bugs.

The delivery mechanism is unusual and worth noting: there is no download page. You go to a continuous integration workflow, choose the latest run, and download the artefacts from that run's summary page, which may require signing in to the forge.

And then the reminder to back up your data before trying one.

That combination is coherent. If the artefact is the output of a commit rather than of a release, it is unreviewed by definition, and the readme is telling you that the cost of testing it is your subscription database.

Every package flavour is built on every commit

The build section is four sentences long, and the second one is the important one.

Continuous integration automatically packages all flavours of the package files for each commit. That is a stronger guarantee than most small projects make, and it means the build matrix is part of the repository's normal operation rather than something that happens at release time.

The rest is the ordinary contributor path: get the source with one command, open it in a recent version of the integrated development environment, and press run.

git clone https://github.com/ReadYouApp/ReadYou.git

The repository also carries a Gradle wrapper, a build script written with the Kotlin DSL, a settings script, a properties file, a release automation directory and a signing directory, which is what the automated packaging runs against. The project is based on a declarative UI toolkit for Android, so there is no native build to configure by hand.

There is one odd instruction at the end: in case of lag, select the release build variant. That is a debugging-oriented note for developers rather than for users, and it tells you the debug variant is meaningfully slower.

Six translations exist and two are labelled outdated

The header of the readme is a language selector, and it carries status information that translation files rarely do.

Five languages are listed: English, German, Simplified Chinese, and two that are explicitly marked as outdated, Traditional Chinese and Persian.

The repository contains five translated readme files, which means there is one more than the selector links: a Japanese translation exists in the tree and is not linked from the language line.

So there are three states here rather than two. Current, outdated, and present but unlisted. That is useful information for a translator looking for work, and it is unusual to see a project volunteer the staleness of its own translations in the header.

Jetpack Compose, and a design lineage named in the credits

The technology choice is stated once: the project is based on the declarative UI toolkit for Android's native interfaces, and the readme links the design language specification it follows.

The credits section is longer than the technology section, and it is the more informative of the two. Around a dozen open source projects are credited, and they map onto the features.

The readability work is a stack of three: a parser, an article extraction library, and a component that renders extracted HTML in a declarative tree. There is also a subscription format parser, and the syndication library that project is probably best known for.

Then the acknowledgements. A named individual is thanked for the design inspiration and for the Monet engine implementation, which explains where the visual identity came from. Two more are thanked for infrastructure: free development-environment licences, and free hosting for the translation platform that the localisation section points at.

Editorial conclusion

Read You fits an Android user who wants a native feed reader with real article extraction rather than a web view, and who keeps subscriptions in a service it can sync with. It does not fit someone who needs a home server install or a stable nightly channel. Before adopting, note that F-Droid builds cannot upgrade to builds from elsewhere, so pick one distribution channel and stay on it, and back up before trying a nightly build.

Frequently asked questions

Official sources

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