TOUCHSCREENS, USER EXPERIENCE, UX FAILS

Why I hate touchscreens

Question: What do ovens and cars have in common?
Answer: They used to have buttons and were easy to operate. Now they have touch screens.

For decades, simple things were designed to be simple: The oven had a button and you turned it on and it heated. Now it has an interface, menus, scroll lists, etc. Don't get me wrong, touchscreens are not necessarily bad. Their usefulness depends on the context of use. Those of you who remember "mobile internet" (the quote marks are necessary) on feature phones know what I am talking about. A phone with a touch screen is a good thing. This does not mean that a touch screen is a good thing for everything.

It is hard to resist building the latest tech into products, but it should only be done if it improves the user experience. Some reasons to think twice before deciding if a touch screen is the right tech for your interface:

  • You cannot feel a touchscreen. In a car, you can locate and operate a heating dial without taking your eyes off the street. Several manufacturers have replaced these hard buttons and dials with touch screens – thereby losing a comfort and safety feature.
  • Touchscreens require precise hand-eye coordination to make your desired selection. In the case of the oven, try lowering the temperature on a touch screen with oven gloves. Also, making a rough input (e.g. increased heating) is often more important than getting an exact output (21° Celsius vs. 21.5°).
  • Touchscreens get dirty (especially on an oven). Cleaning them may execute unwanted actions, but if you don't clean them, in some cases they no longer work properly.
  • Environmental effects (such as reflecting sunlight or cold) limit a touch screen’s functionality, either because you cannot read it, or it no longer reacts to input. No kidding: we’ve tested touch screen equipped cars in which it was not possible to turn on the heating when it was cold! In contrast, a hard button does not care about these conditions.
  • Physical buttons or sliders react immediately. Touchscreens depend on device processing power to display the correct button at the right time (which can occasionally result in pressing the screen multiple time to elicit a response, which often leads to an unwanted outcome).
  • The lack of haptic feedback of many touchscreens (excluding latest phones) is often replaced by auditory feedback. Oh, how much we love beeping devices!
  • Touchscreens lead to feature creep. The processor ability combined with a touch screen tempts developers to overload devices with options, just because it’s possible. This increases interface complexity which usually negatively impacts user experience.


And, no, I do not really hate touchscreens. They are great where they make sense. But unfortunately, “sense” may not influence the product design decision. For my part, I’m glad that airplane cockpits still rely on hard buttons!

 


Also, check out our video of three of our UX experts failing to operate our new oven in the office:

 

Our UX experts are trying to work with a stove...

 

 

Author

Felix Vollmuth

Felix hat einen Bachelor-Abschluss in Bibliotheks- und Informationsmanagement und arbeitet seit 2009 im UX-Bereich. Im Laufe der Jahre hat er Projekte in verschiedenen Bereichen durchgeführt: Apps, Websites, Automotive, Healthcare, Finanzen – sein Favorit ist die qualitative Langzeitforschung.

Go back

Privacy settings

We use cookies on our website. Some of them are essential, while others help us to improve this website and your experience.
In this overview you can select and deselect individual cookies from a category or entire categories. You will also find more information about the cookies available.
Group Analyse
Name Google Analytics
Technical name _gat,_gtag_UA_120284862_1
Provider Google LLC
Expire in days 730
Privacy policy https://policies.google.com/privacy
Use Google cookie for website analysis. Generates anonymous statistical data on how the visitor uses the website.
Allowed
Group Essenziell
Name Contao CSRF Token
Technical name csrf_contao_csrf_token
Provider
Expire in days 0
Privacy policy
Use Serves to protect the website from falsification of cross-location inquiries. After closing the browser, the cookie is deleted again
Allowed
Group Essenziell
Name Contao HTTPS CSRF Token
Technical name csrf_https-contao_csrf_token
Provider
Expire in days 0
Privacy policy
Use Serves to protect the encrypted website (HTTPS) from falsification of cross-location inquiries. After closing the browser, the cookie is deleted again
Allowed
Group Essenziell
Name PHP SESSION ID
Technical name PHPSESSID
Provider
Expire in days 0
Privacy policy
Use PHP cookie (programming language), PHP data identifier. Contains only a reference to the current session. No information is stored in the user's browser and this cookie can only be used by the current website. This cookie is mainly used in forms to increase usability. Data entered in forms are e.g. B. stored briefly if there is an input error by the user and the user receives an error message. Otherwise all data would have to be re-entered.
Allowed
Group Essenziell
Name FE USER AUTH
Technical name FE_USER_AUTH
Provider
Expire in days 0
Privacy policy
Use Saves information of a visitor as soon as he logs into the frontend.
Allowed