How to avoid micro-horrors in UX

Is it just me, or are you, too, getting stressed by the false error messages that are sometimes presented for a little while when systems are loading?

What to do and not to do while waiting for content to load

Scaffolding is quite a nice a design pattern: When waiting for the real content, a generic silhouette of the kind of content that will soon be loaded is shown temporarily. Thanks to the scaffolding, users know what to expect and rendering engines can immediately render the rest of the page, for users to explore while waiting.

But recently, I have repeatedly come across a similar but much less friendly kind of scaffolding: A technically robust fallback for worst case scenarios.

Suddenly, I get unexpected negative messages such as

  • No such user
  • Invalid request
  • Permission denied
  • Warning, system not responding
  • File could not be found
  • Network error
  • Server unreachable

Such messages briefly appear on my screen immediately after I start some applications or go from one screen to another. A fragment of a second later they are usually replaced by the fully functioning app or website. 

Sometimes the message is not possible to see, because it disappears so quickly. But since I am often using a screen reader, I hear it, until it is interrupted by the newly loaded screen/page.

The benefits

From a technical robustness perspective these temporary error messages make some sense. Because from time to time it is not possible to connect to a back-end, read a file or do some other necessary initialisation. So when the application is about to make a connection that could go wrong but is usually very quick, why not begin by displaying a static fallback message?

If everything works as it should, users will have no time to even notice the message. And IF the connection for some reason cannot be made, or if the app freezes, there will be an immediately available feedback to the user. Kind of clever.

The horrors

The problem is that the user’s computer or connection isn’t always as fast as the one used during design. The message that was supposed to be immediately replaced will actually show for one entire second or more - not a tiny fraction of one. Enough for the user to read or hear the message. 

And enough to have a micro-horror user experience (M-HUX). Just think of all the situations when you do NOT want to hear that

  • the video conference you must join this very minute is unreachable, or
  • the document you’ve been working on so long has somehow been erased, or
  • your account does no longer exist, or
  • the system you are responsible for is not working.

When this happens, instead of enjoying the robust system, I start panicking. Usually only for a few seconds, until I realize what happened. But still. 

I’m not a doctor, but my intuition is that M-HUX are not healthy. It may be technically robust, but probably not psychologically.

Recommendation

Please don’t use this design pattern! Or, if you use it, try to delay the message for a second or two, so it won’t appear when not needed.

I don’t think this pattern is listed as one of the dark ones, because it is probably not designed with a bad intention. I don’t even know what the pattern is called. Please tell me if you do! If there isn’t already a name for it, I propose M-HUX.

More about design patterns

Kvinna som sitter framför en dator, uppgiven, med händerna för ansiktet.

Dark Patterns - blir du lurad på nätet?

Fylls din inkorg av reklam och nyhetsbrev som du inte minns att du har signat upp dig för? Då är det risk att du har stött på något som kallas Dark Patterns.

Blandning av starka färger

More colourful web with invisible design

New standard proposal to make the web more personal and, if you like, more colourful!

Publicerad:
Pär Lannerö, porträtt

Pär Lannerö

Senior konsult inom digital tillgänglighet