Knowledgebase

Designing for Real Conditions Print

  • uiuxdesign, performance, errors, guide, howto, solution, zillionkinghost, hosting
  • 0

Not the ideal case.

WHAT DESIGNS ARE USUALLY TESTED ON

A large screen, a fast connection, perfect data, an unhurried user.

WHAT ACTUAL USE LOOKS LIKE

A phone Mobile data, possibly poor One hand, while distracted Incomplete or awkward data Someone in a hurry

WHY THAT MATTERS HERE PARTICULARLY

Most visitors are on phones, frequently on metered data, frequently on variable connections.

WHAT TO DESIGN FOR

Slow loading Long names and addresses Missing images Interrupted connections Errors

WHAT TO TEST WITH

Real data, including the awkward examples A real phone, on mobile data The empty state, before any data exists

THE EMPTY STATE POINT

Every screen has one, and it is usually designed last or not at all.

It is the first thing a new user sees.

WHAT TO ALSO DESIGN

The loading state The error state The state with far more data than expected

WHAT TO AVOID

Designing only the ideal case.


Was this answer helpful?
Back

Are you happy with your experience? Leave us a review on Trustpilot.


Trustpilot