Blog
Build update, September 2026: on track for a New Year launch
Where the Libryva build stands today — the app surfaces, the browser clipper, the deployed backend — and what is left before the public launch targeted around the new year.
The question we get most is simple: when can I actually use Libryva? The answer: we are in the building phase right now, and the public launch is targeted for around the new year — roughly the start of 2027. This post is a snapshot of exactly what exists today and what is left before launch.
What exists today
The app. The Flutter client has all four core surfaces working: the library (books, articles, downloads, playlists), the audiobook player (chapters, bookmarks, sleep timer, speed control, and exact resume backed by the local data layer), the ebook reader, and the saved-articles view for everything you clip from the web. Navigation and player flows are verified end to end with automated UI tests on an Android emulator, screen by screen.
The clipper. A browser extension saves articles straight from the page you are reading — full content plus metadata — into your library, so a clipped story is ready on your phone without a re-fetch.
The backend. The API server is deployed and running: it stores bookmarks and clipped content, and collects waitlist signups. Google-based sign-in and per-device sessions are in progress, so clipped articles and reading progress can follow you across devices.
This website. The site you are reading is live at libryva.com, and this build log is where we will post progress between now and launch.
What “launch” means
The first public release is the daily loop working end to end: clip from the browser, read and listen in the app, and resume exactly where you stopped — with your library stored locally first, not behind an account wall. The app targets iOS, Android, macOS, Windows, Linux, and the web from one Flutter codebase, and sync between them stays an opt-in convenience rather than a requirement.
What’s left before launch
In rough order:
- Accounts and sync — finishing Google sign-in and per-device sessions, then cross-device save.
- Packaging and store listings — getting the app and the browser extension through platform review.
- Polish and performance — the long-tail work that makes resume feel instant everywhere.
- Beta with early testers — waitlist members get the first builds, and their feedback decides what must be stable on day one. If that is you, join the Libryva waitlist.
The timeline
We are targeting a public launch around the new year. It is a target, not a promise carved in stone — the resume-everything core has to be genuinely dependable before it ships, and we would rather slip a week than break the one promise the app exists to keep. Between now and then, this build log will track the milestones as they land.
You can follow along through the RSS feed or the Libryva repository on GitHub.