Grill: MVP screen inventory and IA #5

Closed
opened 2026-08-02 15:15:20 +00:00 by TheAnachronism · 1 comment

Part of #1
Blocked by: #2, #3

Question

What is the MVP screen inventory and information architecture?

Decide the set of screens/routes (account/instance switcher & login, category/feed drawer, article list for feed/category/virtual feed, article reader, any settings stub), navigation edges, and how nested-category drill semantics from the Notes show up in concrete UI states — without designing every pixel.

Part of #1 Blocked by: #2, #3 ## Question What is the MVP screen inventory and information architecture? Decide the set of screens/routes (account/instance switcher & login, category/feed drawer, article list for feed/category/virtual feed, article reader, any settings stub), navigation edges, and how nested-category drill semantics from the Notes show up in concrete UI states — without designing every pixel.
Author
Owner

Resolution

MVP screen inventory and information architecture locked as follows.

Screens

  1. Sign-in — add/connect an Account (root when none exist)
  2. Manage accounts — list / switch / add / remove
  3. Settings — Mark-read mode preference + link to Manage accounts
  4. List hub — article list + drawer tree
  5. Reader — pushed route (no drawer)

Shell & routing

  • Primary shell: list hub + drawer; reader is a pushed route
  • No accounts ⇒ Sign-in is root; successful sign-in ⇒ list hub
  • Cold start and account switch ⇒ Fresh selection, Unread filter on
  • Settings via list hub app bar; Manage accounts via Settings and drawer header (active Account)

Drawer tree

  • Header virtual feeds: All / Fresh / Starred
  • Nested category → feed tree (tap selects; chevron expands)
  • Category selection ⇒ articles for category and descendants; feed ⇒ that feed only
  • Labels / Published / Recently Read out of MVP drawer

List hub behavior

  • Global Unread / All toggle
  • If selection has 0 unread, auto-show all articles while toggle stays Unread
  • Opening an article pushes the Reader

Reader

  • Actions: open original, star, mark unread, back
  • Next/prev (or swipe) within the current list context (same selection + effective filter)

Mark-read mode (Settings)

  • Options: opened in reader | read to end | scrolled/swiped past
  • Default: opened in reader

Glossary

Terms captured in repo-root CONTEXT.md.

Explicitly not decided here

Pixel/theme density; image/enclosure policy; precise scroll thresholds for “read to end” / “scrolled past”; architecture/storage of preferences (see architecture & account tickets).

## Resolution MVP screen inventory and information architecture locked as follows. ### Screens 1. **Sign-in** — add/connect an Account (root when none exist) 2. **Manage accounts** — list / switch / add / remove 3. **Settings** — Mark-read mode preference + link to Manage accounts 4. **List hub** — article list + drawer tree 5. **Reader** — pushed route (no drawer) ### Shell & routing - Primary shell: list hub + drawer; reader is a pushed route - No accounts ⇒ Sign-in is root; successful sign-in ⇒ list hub - Cold start and account switch ⇒ **Fresh** selection, Unread filter on - Settings via list hub app bar; Manage accounts via Settings **and** drawer header (active Account) ### Drawer tree - Header virtual feeds: All / Fresh / Starred - Nested category → feed tree (tap selects; chevron expands) - Category selection ⇒ articles for category **and descendants**; feed ⇒ that feed only - Labels / Published / Recently Read out of MVP drawer ### List hub behavior - Global Unread / All toggle - If selection has **0 unread**, auto-show all articles while toggle stays Unread - Opening an article pushes the Reader ### Reader - Actions: open original, star, mark unread, back - Next/prev (or swipe) within the current list context (same selection + effective filter) ### Mark-read mode (Settings) - Options: opened in reader | read to end | scrolled/swiped past - **Default:** opened in reader ### Glossary Terms captured in repo-root `CONTEXT.md`. ### Explicitly not decided here Pixel/theme density; image/enclosure policy; precise scroll thresholds for “read to end” / “scrolled past”; architecture/storage of preferences (see architecture & account tickets).
Sign in to join this conversation.
No description provided.