Phase 2c — Recall in Your Pocket: the apps get the search
25 JUL AT 10:38 AM

Phase 2c — Recall in Your Pocket: the apps get the search

0 LOVES 0 VIEWS
The phones get the same search the web has. Flutter parity for the search core — the sidebar-drawer entry, the /search screen, the scoped header filter — both forks at full fidelity, OwnerBar at every width. Suite 409/409 green, on-device smoke passed desktop and mobile. Shipped 2026-07-11.

The web got the search in Phase 2b; Phase 2c puts it in your pocket. Flutter parity for the whole search surface — the same sidebar-drawer entry, the same /search screen, the same scoped category/tag header filter — so the app reader and the web reader get identical retrieval. Both forks at full fidelity; the OwnerBar holds at every width.

The discipline that made it correct: the mockups are the baseline, not the spec. Several details changed during operator design review after the mockups were approved, so every visual value was transcribed from the shipped CSS and every behavior from live kontent on dev — not from the mockup. The Flutter grep-audit spot-verified every doc claim against the shipped web code: zero divergences.

Search on mobile — one partial, every width

Three mobile phone states: a post list with a floating action button, the drawer open showing a search field, and mobile search results

The mobile search states the app mirrors: the list with its FAB, the FAB drawer opened to the o-sidebar-search field above the category tree, and mobile /search results. The same partial renders the pinned desktop sidebar and this drawer — zero mobile-specific work, one /search handler everywhere.

Total Recall — the AI Memory Layer (master)
Total Recall — the AI Memory Layer (master)
Jul 25, 2026 Total Recall
← Back to Total Recall