Skip to content
ThorbisInterface Guidelines (opens in a new tab)

Picture

One focused chapter from the Thorbis interface research. 8 rules. Read the research index for every chapter and focused study.

Picture

  • One focus. The sheet is figure. Chrome is ground. Size, then position, then weight. Color last. If two things shout, neither is read. A board is not a poster. A reel is not a board.
  • The inverted L is the composition. Sidebar, location, view, sheet. Do not break it with a second header, a hero, or a card grid. Tight inside a group. Generous between groups. F-pattern on a list. Street first. How a screen is composed.
  • Video uses the rule of thirds. Showcase and product film only. One object, named. Subject on an intersection. Horizon on a third. Lead room in the direction of the face or the move. A little headroom. Match the line across a cut so the object does not jump. Caption in the empty third, never larger than the product. Center is legal when the object is the poster — name it. 16:9 and 9:16. Safe area is the middle 80%. A dispatch board does not get a thirds overlay. Frame.
  • One idea per scene. Showcase discloses one level at a time. A viewport has one idea, one subject, one headline. Isolation is the hierarchy: scale, space, contrast, position, type, photography. Not six benefits in a card grid. Intent sets the mode. Homepage is a router of storefront windows. A family page explores. A product page is a film. Pricing is a store: dense, money, start. A workbench is none of these. D-022. Chapters.
  • Desire, then proof, then price. Reveal in order: what it is, why it matters, how it looks and feels, how it performs in the shop, evidence, configuration and start. Do not dump the spec in the hero. Do not hide the commercial model behind a film. Apple can lean on recognition. A contractor evaluating software cannot. Emotion first. Proof second. Purchase last, and findable.
  • Scroll is a timeline. The visitor owns it. On a Film page, a sequence may move with the wheel, pause, and reverse. The browser still owns the scroll. Do not pin the page and fake a reel. Motion must explain a join, a before/after, a config, a dimension. One subject. One or two properties. Headings that drift and cards that float are costume. Reduced-motion stills of the same crop always exist. The film is never the only explanation.
  • Establish, then crop. The whole object first. Extreme crop second. A camera, an edge, a material landscape is new only after they have seen the board, the phone, or the truck. Recompose on a phone; do not shrink the desktop hero. Copy is HTML in a third, not painted into the picture. The product supplies color in the shot. The chrome stays grey.
  • Mostly product. Some proof. A little cinema. About 60–70% calm product, 20–30% evidence, 10–15% cinema. One or two sequences on a homepage. Breadth is a structured grid, not another film. Every cinematic beat shows how Thorbis connects, simplifies, or accelerates the shop. Do not add movement so the site resembles Apple.

I built this for the dispatcher at 7 a.m., the tech in a crawlspace, and the owner closing the books. Quiet chrome. Precise work. I’m still learning. These are the notes.

Applied bookmark research

Reviewed 2026-09-06. These examples reinforce the existing owners; they do not introduce another visual style or claim the product behavior is implemented. Read the 26-source review and access limits.

Make the task easier, not the screen busier

A feature can look complete while the dispatcher still has to reconstruct context or wait for unrelated content.

Start from one person, interruption, and completed task. Keep the current job and its next action usable while optional evidence arrives. Treat the real constraint as part of the brief, not something polished away afterward.

Thorbis example. For assigning a tech, show the job, relevant availability, and the consequence of the assignment. Do not make the dispatcher traverse a marketing-style sequence or a new shell to finish a routine task.

Verify. Walk through the task with representative long and missing records. Check that the essential action remains understandable when optional content is slow or unavailable. Record the result rather than claiming a performance improvement without measurement.

Do not import. No additional shell, feature hero, framework migration, or new dependency. Keep the approved surface role.

Open the product skill · Evidence: Design Engineer Principles; How we think about design; Component Architecture for React Server Components

Preserve the place as the collection grows

Large customer, property, and inspiration collections become expensive to navigate when every inspection loses the current place.

Treat filters, selected records, scroll, and Back behavior as part of the task. Loading a child or optional panel should not reset the whole collection. A saved reference includes enough context to be useful when revisited.

Thorbis example. Open a property from a filtered customer list and return to the same filter and position. On the inspiration wall, reserve the media footprint and retain source credit even when the preview is unavailable.

Verify. Try refresh, Back and Forward, a direct record link, an empty result, a failed preview, and a long collection. Check that late data does not overwrite a draft or move the action under the pointer.

Do not import. No unbounded eager media, private information in shareable URLs, or a local-only storage promise borrowed from Copper.

Open the ecosystem skill · Evidence: 7 Principles of Rich Web Applications; Component Architecture for React Server Components; Philosophy; Copper

Loading search…

Loading search. You can close this message and keep reading.