Implements the researched IA fix: mobile nav UX consensus caps primary
destinations at 4-5 (uxpin.com, fintech/banking 2026 UX research), and
this app had grown to 22 tabs in one horizontally-scrolling row —
exactly the anti-pattern that research flags for choice paralysis and
slower task completion.
New structure — 5 bottom-nav hubs, grouped by what the user is actually
trying to do, not build order:
- Home: Coverage (unchanged, still the landing screen)
- Estate: Assets, Faraid, Insurance, Wassiyah, Hibah, Family Waqf,
Nominate, Claims (H2)
- Giving: Zakat, Sadaqah, Khairat
- Family: Tree, Trigger, Mutawalli, Manage (was 'Family', renamed to
avoid colliding with the hub's own label), Neighbourhood
- Daily: Prayer Times, Qibla, Quran, Locate
Each hub reveals its own sub-nav one tap in, instead of every tab
competing for space in a single row. Settings moved out of the tab
strip entirely into a header gear icon, matching the banking-app pattern
of keeping settings out of primary thumb-reach real estate. The bottom
nav is now fixed (thumb-zone), sub-nav keeps the old sticky-top position.
Cross-component navigation (nav.js requestedTab, used by the Family
Tree's 'give sadaqah in memory' link) now resolves a tab label to its
owning (hub, sub-tab) pair instead of a flat index — verified live.
This touches every E2E suite: a single click on a tab's old selector no
longer reaches it (hub, then sub-tab). Added a shared gotoTab(page, label)
helper to e2e-auth-helper.cjs encapsulating the two-step navigation, and
migrated all ~22 affected test files off direct nav-button selectors —
mechanical substitution followed by manual fixes for local clickTab
wrappers, template-literal selectors, and active-state assertions that
needed to target the new .hub-tab/.subnav structure specifically.
Full regression after migration: every suite passes (one isolated
Family Tree flake confirmed clean on rerun, unrelated to navigation).
Closes 3 of the remaining 4 gaps from the competitive benchmark:
- Coverage Dashboard now has a rule-based recommendations engine
(recommendations.js) surfacing plain-language next steps from data
already in the app — exposed assets, missing Wassiyah, unverified
assets, unlinked liabilities, missing insurance/Zakat setup,
insufficient attestors, no agent assigned, no Waqf configured.
- Faraid Calculator gains a madhab selector (Shafi'i/Hanafi/Maliki/
Hanbali) encoding the one well-documented divergence this engine's
existing rules touch: whether radd extends to a sole-heir spouse
(Hanafi: yes; Shafi'i/Maliki/Hanbali: no, residue unallocated).
Ja'fari (Shia) is honestly gated as unsupported rather than silently
computed with Sunni rules, since it's a structurally different
classification system, not a parameter tweak. faraid.test.js grows
from 14 to 17 cases covering the divergence and the gating.
- Wassiyah tab gains a 'Generate draft will document' button producing
a formatted, statutory-style DRAFT will (declaration/revocation,
executor appointment, bequest schedule, witness attestation blocks)
via browser print-to-PDF — no new PDF dependency. Clearly watermarked
'DRAFT — NOT EXECUTED, requires physical signing and witnessing.'
Not a claim of legal validity, a lawyer-reviewable starting point.
The 4th gap (human-in-the-loop professional tier) remains open — out
of scope for a self-serve prevention tool. COMPETITIVE_BENCHMARK.md
updated to reflect closed/partially-closed status on each item.
Covered by e2e-gaps-round2.cjs (14/14) plus 3 new faraid.test.js cases.
Full regression: 226/226 across all suites.
wmj