Kwark. Design System
Open Kwark

Bottom navigation

A phone tab bar for a companion screen with three to five equal destinations. Kwark’s own phone chrome does not use one.

ComponentsNavigationReady for Kwark
<nav class="kw-bottomnav" aria-label="Call sheet">
  <a href="#" aria-current="page"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M15 2H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h12a2 2 0 0 0 2-2V7Z"/><path d="M14 2v4a2 2 0 0 0 2 2h4M10 9H8M16 13H8M16 17H8"/></svg><span>Today</span></a>
  <a href="#"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M20.2 6 3 11l-.9-2.4c-.3-1.1.3-2.2 1.3-2.5l13.5-4c1.1-.3 2.2.3 2.5 1.3Z"/><path d="m6.2 5.3 3.1 3.9M12.4 3.4l3.1 4M3 11h18v8a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2Z"/></svg><span>Scenes</span></a>
  <a href="#"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M16 21v-2a4 4 0 0 0-4-4H6a4 4 0 0 0-4 4v2"/><circle cx="9" cy="7" r="4"/><path d="M22 21v-2a4 4 0 0 0-3-3.9M16 3.1a4 4 0 0 1 0 7.8"/></svg><span>Cast</span></a>
  <a href="#"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M20 10c0 5-5.5 10.2-7.4 11.8a1 1 0 0 1-1.2 0C9.5 20.2 4 15 4 10a8 8 0 0 1 16 0"/><circle cx="12" cy="10" r="3"/></svg><span>Map</span></a>
</nav>

Kwark’s position

Kwark’s phone screens have no tab bar. A phone shows one 44px header (back, one-word title, Menu ▾) and one floating dial at the foot for Comments, Quick note and Account (Decision 0016). Phone Home is the projects (Decision 0021). A tab bar would add a second permanent band and push the writing down. There is no MobileBottomNav in the codebase.

When to use

  • A separate, read-mostly companion view that a crew member opens on set, such as an issued call sheet with Today, Scenes, Cast, Map. Three to five destinations, all equal, none of them editing.

When not to use

  • Anywhere the floating dial is on screen: the two collide at the foot.
  • In the screenplay, the outline or any writing screen.
  • For actions. New scene is not a destination.

Writing

One word per tab, a noun: Today, Scenes, Cast, Map.

Anatomy

  1. Bar: 56px plus env(safe-area-inset-bottom), --k-surface, 1px --k-line on top. Flat: no shadow, it does not float.
  2. Tab: equal width, at least 44 × 44px, icon 20px over the word in 12px Poppins 500, --k-text-2.
  3. Current tab: --k-text and a 2px bar in --k-accent-soft on the tab’s top edge, aria-current="page".

Tokens

Token Light Dark
--k-surface #ffffff #1a1a1a
--k-line #e2e8f0 rgba(255, 255, 255, .1)
--k-text #0f172a #e3e3e3
--k-text-2 #5b6779 #9ca3af
--k-accent-soft #e8b58b #e8b58b
--k-tap 44px
--k-fs-meta 12px

React

Use the HTML below with kwark.css. The example shows the markup and styling. Supply any application behavior described on this page.

HTML and CSS

Works anywhere with kwark.css.

<nav class="kw-bottomnav" aria-label="Call sheet">
  <a href="#" aria-current="page"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M15 2H6a2 2 0 0 0-2 2v16a2 2 0 0 0 2 2h12a2 2 0 0 0 2-2V7Z"/><path d="M14 2v4a2 2 0 0 0 2 2h4M10 9H8M16 13H8M16 17H8"/></svg><span>Today</span></a>
  <a href="#"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M20.2 6 3 11l-.9-2.4c-.3-1.1.3-2.2 1.3-2.5l13.5-4c1.1-.3 2.2.3 2.5 1.3Z"/><path d="m6.2 5.3 3.1 3.9M12.4 3.4l3.1 4M3 11h18v8a2 2 0 0 1-2 2H5a2 2 0 0 1-2-2Z"/></svg><span>Scenes</span></a>
  <a href="#"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M16 21v-2a4 4 0 0 0-4-4H6a4 4 0 0 0-4 4v2"/><circle cx="9" cy="7" r="4"/><path d="M22 21v-2a4 4 0 0 0-3-3.9M16 3.1a4 4 0 0 1 0 7.8"/></svg><span>Cast</span></a>
  <a href="#"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="1.75" stroke-linecap="round" stroke-linejoin="round" aria-hidden="true"><path d="M20 10c0 5-5.5 10.2-7.4 11.8a1 1 0 0 1-1.2 0C9.5 20.2 4 15 4 10a8 8 0 0 1 16 0"/><circle cx="12" cy="10" r="3"/></svg><span>Map</span></a>
</nav>

Keyboard

Key Does
Tab Moves between destinations.
Enter Opens the destination.

ARIA

  • <nav aria-label> named for the view; tabs are links with aria-current="page" on the current one. Do not use role="tablist": these navigate, they do not swap panels.

Rules

  • Never add a bottom navigation to a Kwark screen that shows the floating dial (Decision 0016).
  • Must keep three to five destinations, each an icon and one word.
  • Never put an action in a tab.

AI readiness test

Task. Give the phone Outline a bottom navigation for Acts, Beats and Notes.

Give the agent. This page, Decision 0016, the Floating dial page.

Constraint. Phone width 375px.

A reliable answer

  • Declines and explains that the dial and the one-line header own the phone chrome
  • Offers a Segmented control in the one allowed band instead
  • Keeps writing starting near y = 200

Give this Markdown to your coding agent or share its URL.

Open .mdllms.txt
Loading…