Research: existing Android tt-rss clients #3
Labels
No labels
needs-info
needs-triage
ready-for-agent
ready-for-human
wayfinder:grilling
wayfinder:map
wayfinder:prototype
wayfinder:research
wayfinder:task
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
TheAnachronism/tt-rss-viewer#3
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #1
Question
What should we learn from existing Android tt-rss clients (and the retired official client docs) before designing ours greenfield?
Surface: how they model categories/feeds/virtual feeds; session and multi-server handling; read/star sync patterns; known API pitfalls or workarounds; UX patterns worth copying or avoiding for a nested-category drawer + article list + reader flow. Prefer primary sources (repos, F-Droid listings, archived official docs) over secondary blogs.
Resolution
Documented lessons from TTRSS-Reader (primary live Android client) and the retired official Android client notice.
Gist: Copy virtual feed ids, sid auth, optimistic mark+sync, unread toggle, and category-as-article-list capability; avoid flat categories, default category→feeds drill-down, and single-account prefs. Official app gone 2025-11-01 — greenfield Flutter still right.
Doc:
docs/research/android-tt-rss-clients.mdonmaster.