Posts on UX.
18 posts tagged "UX".
Seven navigation phases. The prerequisite chips encoded the one thing the others couldn't.
The learning navigation spec ran seven phases from foundational structure to site-wide search. P5 — prerequisite chips, a static 'Read first' link at each chapter head — was the smallest implementation. It was also the highest return: every other phase encoded page structure, and P5 encoded reader intent.
The navigation plan shipped on Pagefind. Prerequisite chips were the higher-leverage fix.
Six phases of navigation work shipped on the learning hub in July. Pagefind — site-wide search — closed the programme. Prerequisite chips, one phase earlier, delivered more navigability per line of code by firing at orientation time rather than recovery time.
The navigation spec pre-ranked prerequisite chips over search. Six phases later, that held.
The conventions.md backlog called prerequisite chips at the chapter head the single highest-value navigability fix before any code shipped. Pagefind search and an IntersectionObserver right-rail TOC both landed in the same programme. The ranking held. This is why.
I had the Accounts calendar scoped as one level. Mid-design I deepened it to three.
Phase K shipped a horizontally-scrollable daily-activity strip on the Accounts screen. Phase O was meant to replace it with a calendar — I had a compact, single-level surface already scoped. Mid-design I deepened the ask to full-screen plus day mode, and a back-nav regression in round-2 device QA explains why that was the right call.
The Accounts screen took four iterations. Each one bought fidelity by spending scope.
Sprint 2 shipped a SwiftUI list with CRUD. Phase K rebuilt it into a module stack with a trend chart and activity strip. Phase O turned the strip into a three-level calendar flow. Round-2 device QA on AnF found the back-nav bug that came with it.