The shorter we wait, the more engaged we are. And we're the most productive, when there's no visible lag between what the digital product shows us and our actions. 

Sometimes, however, it's inevitable for some data to load. How to handle it then? 

You can reduce perceived wait time in a couple of ways. One way is with progress bars. They don't have to be precise, just the fact that a progress is animating is enough to calm the users and let them know something is happening. 

Another great way is using skeleton screens. They're grayed out "layout" blocks before the data loads. Many apps and websites do it and it's the best approach when the data we load has predictable boundaries. So if you're loading a graph, a data table, or a photo with a description, all of these can be converted into blocks. Those blocks can fade in and out a little bit to indicate the real data is loading.

Doherty Threshold

 It's easier to hit big targets Small buttons positioned close to one another make it difficult to touch (or click) the right one.

 Make actionable elements big enough for comfortable use.

Fitts

Fitts's Law

Keep it simple

Millers Law

 Goal-Gradient effect 

Hick's law

Hick's Law

Jakobs

Jakobs Law

The more elements people have to process, the easier for them to make a mistake. On average people can rember between 5 and 9 items, with 7 being the magic number most designers use. Instead of focusing on that number so much, however, it's good to simply reduce complexity in a system overall. 

Split tasks into easy to follow, logical steps instead of adding in everything at once.

Every additional element on the screen will require some processing time. The more "busy" our brain gets, the bigger the chance for a mistake or abandoning the process altogether.

Keep it simple

Liked the tip? Share it!