Frequent items should sit near the default focus
Aliases: landing focus · initial focus placement · default focus
What it is
When a screen appears, focus already rests on some object; every later arrival is measured from there. Putting the highest-frequency actions next to that landing point drives the most common tasks to zero or one step. Putting them on the opposite corner charges a fixed cross-screen tax on every open. Default-focus proximity is about the origin, not how dense the grid is or how expensive a row change is.
Why it happens
Default focus is the shared source of all paths. Frequency is skewed: resume, search, the first rail of home, account for most first actions after an open. Parking that source on a low-frequency decoration, an ad card, or the third tile of “Today’s picks” forces high-frequency work to start from the wrong origin every day. Muscle memory forms—two Rights after power-on—and a redesign that moves the origin makes that memory hit a different object.
“Near” is step-near, not visual-centre-near. A hero in the middle of the screen is still far to a D-pad if the user must walk there from the top-left. Conversely, default focus on the hero’s Play control makes Resume zero steps even if the art sits high.
Returns and deep links rewrite the origin. Coming back from a detail page to Home, if focus resets to the top-left instead of the card just left, the path already paid is thrown away, and the proximity advantage of frequent items holds only for the first entry.
Where it stops holding
First-run has no frequency data; default focus should land on a “get started” action (Resume, the first popular title), not an empty personalization slot. Kids profiles, hotel modes, and demo units have different high-frequency items than the household master account; one shared landing pushes the wrong item to zero steps. A search field always top-left and content always lower-right is platform convention, not frequency—breaking it to save two steps wrecks cross-app spatial memory. If ads buy the default focus, frequency is commercially overridden; users learn to tap a direction immediately to dodge.
Applying it
- Rank the landing from first-action logs after the screen appears: Resume, an unfinished setup, the rail last left, ahead of the brand mark and campaign slots.
- Land default focus on a confirmable action, not on a container or section title that still needs one more step to reach an action.
- On return from a child page, restore focus to the item just left; only if that item is gone, fall back to the row’s default column, not a full-page reset.
- Verify with the distribution of keypresses from screen appearance to the first OK. If the peak sits stably above three steps, the landing is not aimed at high-frequency items. After moving it, check that the same distribution collapses toward zero–one steps, and spot-check that the new origin does not smash return memory.