Grill: online-first cache-ready Flutter architecture #6
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#6
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
Blocked by: #2, #4
Question
What Flutter app architecture keeps the MVP online-first while remaining cache-ready for a future offline reading feature?
Decide layering (UI / domain / API client / local cache seams), where multi-instance accounts live, how read/star mutations sync, and what deliberately is not built now so offline can plug in later without a large rewrite.
Resolution
Online-first, cache-ready Flutter architecture locked (see ADR-0001).
Layering & state
domain/+data/{api,local}/Accounts & isolation
package:http)sidinflutter_secure_storage; metadata in prefs/JSONSync & persistence (MVP)
updateArticle)sid; clear error onAPI_DISABLEDReads
getFeedTreegetHeadlinesfor List hub;getArticlefor Reader HTMLDeliberately not built now
ADR:
docs/adr/0001-online-first-cache-ready-architecture.md