Upcoming post
Next up: extension reliability, resume flow, and private-beta polish
The next milestone is not broad feature expansion. It is making the extension trustworthy enough for repeat daily use: stronger popup cleanup, safer metadata detection, better duplicate prevention, clearer save and update feedback, and resume behavior that consistently returns readers to the right place.
Post links
Keep browsing
Move between upcoming work, shipped updates, and the editor from the same reading surface.
What is coming
A concise summary of the work planned for this upcoming item.
- Clean up popup detector architecture so description, title, source, and chapter fixes stop regressing unrelated sites.
- Keep hardening the floating quick-save button as a strict update-only control for already tracked entries.
- Improve duplicate prevention and series/chapter matching on the main manga and novel sites used most often.
- Make resume behavior clearer by keeping source URLs and last-read URLs aligned all the way through the extension browser.
Why it matters
How this planned work should improve the experience once it ships.
- Readers should trust that updating progress will touch the right entry instead of creating duplicate noise.
- Continue actions should feel dependable enough to use every day, not like a best-effort shortcut.
- Private beta testers will be able to judge the real reading workflow instead of fighting detector instability first.
- This is the work that most directly reduces public-release risk.
More detail
Additional roadmap context, scope notes, or rollout expectations for this upcoming post.
The extension already has the right shape: popup quick save, library browser, continue links, floating chapter updates, and shared save contracts. The near-term work now turns that MVP into a dependable private-beta tool.
That means focusing on detector cleanup instead of piling on more brittle site-specific hacks, tightening the floating button so it only appears when an existing entry can truly be updated, and making resume behavior visibly trustworthy from save to continue. Once that loop feels boringly reliable, the next steps become launch QA, permission review, and a smoother path to limited external testers.
Post status
Current state
A quick snapshot of how this upcoming post is categorized and published.
Category
Extension
Status
Live
Published
2026-03-31 21:49 UTC