Skip to content
HAv5.0
Patterns

Navigation

How people find their way, and when the best navigation is less of it. Drawn from Trainest, where four tabs became one plan, and Oya, where every action lives on a key.

The rule

Organise around what people came to do, not around your features.

Before and after

From Trainest
Trainest before: four separate tab screens, Nutrition, Workout, Check-in and Progress, each with its own tab in the bottom bar
Before · four tabsA tab for every feature

Nutrition, workout, check-in and progress, each in its own silo. People opened the app and didn’t know what to do.

Trainest after: Today’s Plan, with today’s priority and three more actions on one screen
After · one planOne screen for today

People don’t choose where to start. The plan tells them.

Try it

Find out what’s due today, both ways
Nutrition
Daily goals1205Calories left
Track meal
Taps so far
0
Still hidden
  • Workout
  • Check-in
  • Progress

Tap through the tabs to find everything due today.

The app should answer one question: what do I need to do today? Not which tab to open.

Keys as navigation

From Oya

Oya has one screen, so there’s nowhere to go. Navigation becomes reaching an action without looking. Moving to the mouse breaks flow, so every action lives on a key.

Space
Start or pause
Take off or add 5 seconds. A toast confirms it, no modal.
123
Switch preset
R
Reset
Try the Oya countdown in the Playground

Ways in

Way inProductHow
A plan instead of tabsTrainestFour tabs became one daily screen. The plan says where to start.
Keys instead of clicksOyaSpace, arrows, 1 2 3 and R. No menus.
Search straight to a streetSpottaServer-rendered pages with structured data, so a search like “Allen Avenue Ikeja reviews” can land on the street page
A link to one reviewSpottaEvery review has its own shareable deep link
Tabs only where allowedAyikaOutlook gets Overview, Tracking and Forecast tabs. Google Calendar allows none.
A sidebar and searchThis portfolioDocs-style sidebar, search on ⌘K, and an “On this page” rail on long pages

Rules

Do
  • Start from the question people open the app with.
  • Put the next step on the first screen.
  • Give frequent actions a key.
  • Make every page reachable from search and from a link.
Don’t
  • Copy your feature list into the tab bar.
  • Make people tap around to find out what’s due.
  • Hide a frequent action behind a menu.