← All frames · Frame 03 · states & edges · 375px

The bottom nav is shell chrome, so its states are about never blocking navigation. The bar renders its static destinations instantly; only the app-registry-derived long tail (in the drawer) has data states. Navigation stays fail-open — Home / Orgs / More work even when the registry call fails. Plus the safe-area, touch-target, reduced-motion and long-label edges the shell must honour.

Loading · bar instant, drawer apps skeleton

FuzeFront

Empty · no registered apps

FuzeFront

No apps yet

Nothing's been activated for this workspace. The bottom nav still works — browse the catalogue to add one.

Error · registry failed, nav fail-open

FuzeFront

Safe-area · notch + home indicator

FuzeFront

Dashboard

The top bar pads below the notch (--safe-area-top); the bar pads above the home indicator (--safe-area-bottom). Shown forced to 26/24px.

Content clears both insets

Nothing hidden under the notch or the bar.

Edge · long label truncates, ≥44px targets

FuzeFront

Organizations

A localized / long label never wraps or pushes a sibling — it ellipsizes. Each tab keeps a ≥--touch-target (44px) hit area (dashed = measured).

What QA writes RED specs against

Frame 03 / 03 · States & edges · 375px · tokens only

Review · mobile-bottom-nav approve or reject each flow ↓
mobile-bottom-navpendingApproveReject