Kwark. Design System
Open Kwark

Phones

On a phone Kwark gives the screen to the work: one 44px header line, content by the first fifth of the screen, one floating button for comments, notes and account, rows without buttons, and thumb-sized targets everywhere.

Patterns
Outline
Act 2

Mira finds the missing reel.

Scene 12

INT. EDIT SUITE – NIGHT

The problem

Kwark’s people write on phones: on the train home after a shift, between takes, in a queue. On 17 October 2026 the founder opened the Outline on his phone and found a two-line header (title and story name), account and comments icons, then three rows of controls (New Act, Cards, Find a beat, All beats, Pad, More) before any writing. Characters still showed a desktop breadcrumb running under the comments icon. His words: “80% of the page is non-writing stuff … header everywhere is bad … no breadcrumb, just a back button … comment, account and edit under one FAB at the bottom … do we need 2 lines in the top banner?”

The same week, Home on a phone showed a search box, New project, three filter chips, a sort arrow and two buttons on every story row; each row was about 160px and the first story sat low. And when a run-the-app audit measured the production office at 375 wide with real touch, 252 controls on 11 screens were smaller than 44px.

A phone has no space to waste, and a thumb is not a mouse pointer.

Kwark’s answer

One line at the top, one button at the bottom (Decision 0016)

  1. The header is one line, about 44px: a back chevron, a one-word screen title, and a labelled Menu ▾ button. No subtitle, no breadcrumb, no account or comments icons.
  2. Comments, Quick note and Account live in one floating button at the bottom corner. It opens a small dial of labelled 44px items: Comments, Quick note, Account. A dot on it means comments are waiting for you; that is its only badge. The page keeps a reserved slot at its foot (--k-fab-slot) so the button never covers content, and the button steps aside while comments, a note or a sheet is open.
  3. A screen’s own tools collapse into one compact row or into Menu, so the writer’s content starts by about y = 120 on a 375 × 812 screen. The Outline went from y≈392 to y≈222 in the first fix round; y≈120 still needs the act and view bar folded into the header.
  4. Desktop is unchanged.

The bottom corner is where thumbs are. And moving occasional actions out of the top-right fixed a whole class of collision bugs in which icons sat on top of each other.

Home: the projects take the attention (Decision 0021)

  • One bar: Yours and Shared tabs (a count only on the selected one) and four labelled icons: Search, Filter and sort, New project, and ⋯. A second band appears only while searching. Cards and List moved into ⋯.
  • A story row has no buttons. Tapping it opens the project as Decision 0018 says (Project home, or Where I left off). A row is about 103px.
  • The row’s ⋯ menu leads with Project home and Share (yours only), then Edit, Export, Move and Move to trash. Open in new tab is not offered on a phone.

The screenplay on a phone

  • The editor uses one compact query everywhere: (max-width: 767px), (pointer: coarse) and (max-height: 520px). A phone held sideways gets the phone layout. A test fails if a rule reverts to a bare max-width: 767px.
  • The five menus become a Menu sheet that opens on Showing (Script, Title page, the Prepare to shoot views), then Find, Read, Export, Quick note, Comments, then File, Edit, Format, View and Help, each drilling to its own page (Decision 0015).
  • The scene list is a labelled Scenes button, not an icon.
  • The timeline rests as a 22px strip under the menu: slide a thumb to scrub, tap to open; turned sideways it opens a full-screen edit bay (Decision 0007).
  • Zoom offers Fit width (“The page as wide as the window”) and Fit page.

Thumb-sized everywhere (Decision 0034)

On phones, upright or sideways, segments, icon buttons, fields, paperwork statuses, budget rows, desk statuses and notices are 44px targets (--k-tap). Buttons can be drawn at about 36px inside a 44px tap area. Office helper text is 12px, not 11. Paper is the exception on purpose: the call sheet, the stripboard strips and anything inside print rules keep their sizes, because changing them changes what prints. After the change the same 11 screens measured 138 small controls, mostly in Shots & Boards and on the call sheet’s paper fields; those need their own phone layouts, not smaller rules.

Anatomy

Part Size Means
Header 44px, safe-area inset at the top Where you are and the way back
Back chevron 44px target Up one rung of the ladder
Title One word where possible, truncated with an ellipsis The screen
Menu ▾ Word, icon and chevron Everything else on this screen
Floating button 46px disc, --k-shadow-pop (it floats) Your own shortcuts: Comments, Quick note, Account
Dot on the floating button Small, with an accessible count Comments waiting for you
Bottom sheet Grip, title, rows that drill down one page at a time, a labelled back row A menu or a short form
Fab slot Reserved padding at the foot Content never sits under the button

Rules

  • Must use one header line on phones: back, title, at most two labelled actions, and Menu ▾.
  • Must start the person’s content by about y = 200, aiming for y≈120 on 375 × 812.
  • Must use 44px targets wherever the pointer is coarse.
  • Must use the shared compact query in the screenplay, so sideways phones get the phone layout.
  • Must reserve the floating button’s slot so it never covers content or a toast.
  • Never show a breadcrumb, a subtitle, an explanatory sentence or a row of chips above the content on a phone.
  • Never put buttons on a list row; the row opens, and its ⋯ menu holds the actions.
  • Never use “⋯” alone in a header. The word is Menu. (“3 dots means nothing”, the founder.)
  • Never rely on hover or drag alone. Every hover tip and drag has a tap or menu equivalent.
  • Always make bottom sheets drill down one level per page with a labelled back row, never a 62-row list.
  • Always shrink nothing on paper to fit a phone. Paper prints as paper.

Edge cases

  • 320 wide. Check headers at 320. The title truncates before the Menu button does; Menu never wraps.
  • The keyboard is open. Bottom bars ride above the visual viewport; the floating button hides while a field has focus.
  • Sideways phone. Compact layout, safe-area insets on both sides; the timeline opens as the full-screen bay.
  • A notch or home bar. viewport-fit=cover and safe-area insets on the header and any bottom bar; 100dvh, never 100vh.
  • Android back. Closes an open sheet before it leaves the page.
  • Screens not yet migrated. A few screens without PageHeader keep a fixed top-right fallback; do not copy it.

Writing

  • Header: one word. “Outline”, “Characters”, “Schedule”.
  • Menu, never “More” or “⋯”.
  • Dial items: Comments, Quick note, Account. The dial’s accessible name: “Comments, quick note and account”.
  • Sheet hints may replace keyboard shortcuts on a phone: Keep a restore point, “A point inside this draft you can go back to”; Dual dialogue, “Two people speaking at the same time”.

Accessibility

  • The floating button has an accessible name that lists what it opens, aria-haspopup="menu" and aria-expanded.
  • The comments dot is mirrored in the accessible name (“Comments, 2 waiting”).
  • Sheets are modal dialogs: focus moves in, is held, and returns to the trigger; Escape and the back gesture close them.
  • Text zoom to 200% must not clip the header; the title truncates.
  • Nothing under 12px on a phone, nothing under 11px anywhere.

Back, “Outline”, Menu ▾ on one line; the first act card at y≈220; one pen at the bottom corner.

Do

“Outline” and “Blank Pages” on two lines, account and comments icons, and three rows of tools before the first card.

Don’t

A story row with the poster, title and one line of facts; tap opens it; ⋯ holds Project home and Share.

Do

A story row with Project home and Continue writing buttons at 32px, each 160px tall.

Don’t

Demo

Schedule
<div style="width:100%;max-width:360px;border:1px solid var(--k-line);border-radius:22px;background:var(--k-bg);overflow:hidden">
<div class="kw-page-header" style="background:var(--k-surface);border-bottom:1px solid var(--k-line)"><button class="kw-icon-button" type="button" aria-label="Back to Home"><svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><path d="m15 18-6-6 6-6"/></svg></button><h1>Schedule</h1><button class="kw-text-button" type="button">Menu <svg viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" aria-hidden="true"><path d="m6 9 6 6 6-6"/></svg></button></div>
<div style="padding:12px 16px;display:grid;gap:4px">
<a class="kw-row" href="#"><span class="kw-row__title">Day 3 · Edit suite</span><span class="kw-row__meta">Rev 2</span></a>
<a class="kw-row" href="#"><span class="kw-row__title">Day 4 · Rao Farm</span><span class="kw-row__meta">Draft</span></a>
</div>
<div class="kw-sheet" style="margin-top:8px"><div class="kw-sheet__grip" aria-hidden="true"></div>
<button class="kw-menu-item" type="button">Comments <span class="kw-badge kw-badge--warn" style="margin-left:auto">2</span></button>
<button class="kw-menu-item" type="button">Quick note</button>
<button class="kw-menu-item" type="button">Account</button>
</div>
</div>

Page header, Floating dial, Sheet, List row, Navigation, Menus and shortcuts, Layout.

AI readiness test

Task. Bring the Budget screen to the phone pattern.

Give the agent. This page, Decisions 0016, 0021, 0034, Page header, Floating dial.

Constraint. Desktop unchanged; paper sizes unchanged.

A reliable answer

  • One 44px header with back, “Budget” and Menu
  • no breadcrumb or subtitle
  • Account rows are 44px and hold no buttons, actions in a ⋯ sheet
  • Content starts by about y = 200 at 375 wide, checked at 320 too
  • The floating slot is reserved
  • the printed top sheet keeps its sizes

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

Open .mdllms.txt
Loading…