VANKPA
Start a project

Web development · 5 min

Put mobile customers first.

Start with what customers need to read and do, then make it easy on a smaller screen.

By Van Kpa
A designer comparing one content hierarchy across desktop, tablet, and mobile

Start with what customers need to read and do, then make it easy on a smaller screen.

A good mobile website preserves the information and actions people need. It considers touch controls, readable text, image crops, connection quality, and the order in which content appears.

Start with content order

Before choosing columns or breakpoints, write down what someone must understand first, what evidence supports it, and which action should remain available. That order should make sense in the document without relying on visual position alone.

A strong content order improves mobile layout, keyboard navigation, screen-reader use, and search understanding at the same time. It also exposes desktop compositions that depend on decoration rather than hierarchy.

The mobile layout does not create the priority. It reveals whether the priority was ever defined.

Let breakpoints change behavior

A breakpoint is useful when the current behavior stops serving the content. A comparison may become horizontally scrollable, a persistent navigation may become a dialog, or supporting details may move after the primary action.

These changes should be deliberate and testable. Device labels are less important than the point where reading, touch, focus order, or interaction quality begins to break down.

  • Change layout when the content needs it
  • Preserve logical focus and reading order
  • Avoid hover-only meaning
  • Keep controls large enough for touch
Hands testing a mobile interface with the same hierarchy visible on larger screens

Reduce input cost on smaller screens

Forms and workflows become more demanding when the keyboard covers the screen, context is limited, and the user may be moving or interrupted. Ask only for information required at the current decision point.

Progressive disclosure, sensible input types, clear errors, saved state, and an understandable path backward make the same workflow feel intentionally mobile rather than merely available on a phone.

Test the constraints people actually have

A responsive page can look correct in a narrow desktop window and still fail on a device. Test dynamic browser chrome, text zoom, reduced motion, keyboard focus, long labels, slower connections, landscape orientation, and representative content.

The result is not identical presentation across devices. It is a consistent promise: the important information remains readable, the action remains operable, and the interface does not hide its state.

  • Text zoom and long content
  • Keyboard and assistive technology
  • Real mobile viewport behavior
  • Media loading and layout stability

Continue reading

Related insights.

A research team organizing source artifacts and constraints before interface design
01 · Research practice · 7 min

Learn before redesigning

Use customer feedback, everyday tasks, and real constraints to guide your design decisions.

Read insight
Senior professionals reviewing evidence, a prepared recommendation, and a human approval boundary
02 · Responsible AI · 7 min

Automate with clear ownership.

Set clear limits for the information automation uses, the work it prepares, and the actions people approve.

Read insight
A young leadership and operations team redesigning an end-to-end workflow around a clear human approval point
03 · AI transformation · 9 min

Make AI useful at work.

Buying a tool is the first step. Value comes from fitting it to a real workflow and checking the results.

Read insight

Continue the conversation

Bring this to your project.

Bring the business question, available evidence, current constraints, and desired change. Vankpa will frame a responsible next step.