Calling bullshit on ‘Apple is really bad at design’

October 16, 2017

There’s one thing that’s really been itching a nerve with me. Lately, there’s been a lot of “Apple has lost it’s innovation” or “Apple sucks at design” pieces in personal blogs and in major news outlets. One of the most shared posts “Apple is really bad at design” (how’s that for a clickbait title?) makes me twitch.

Any opinion that you state as a hard fact without having the research to back it up is pretty much lying to your audience. To me, making sure that we have all of the necessary information before bashing other people’s work is one of the most ethically important processes we have as designers. Unfortunately, others seem to believe that having a strong opinion is far more important than having a validated one.

“The “notch” on the new iPhone X is not just strange, interesting, or even odd — it is bad. It is bad design, and as a result, bad for the user experience. The justification for the notch (the new Face ID tech, which lets you unlock the device just by looking at it) could have easily been accomplished with no visual break in the display.


To wit: no one wanted or asked for Face ID, and the feature actually raises new concerns about security for users.”

First of all, bad design isn’t necessarily the same as a bad user experience. The design of the notch aside, the feature the notch enables (Face ID) is what the user experience is about. I’m extremely skeptical of the statement that it could “easily have been accomplished with no visual break in the display”. If that’s the case, I’m sure Apple would love to have that input.

It’s also true that no one specifically asked for Face ID - that I know of, I’m pretty sure Apple could argue otherwise. To claim that no one ‘wanted’ it however, is just a wrongful claim because so far only a very number limited number of people have had the opportunity to actually try it out. If the claim that ‘no one wanted it’ is true, then that holds true for Touch ID, the iPhone itself, Tesla, Uber, Facebook, or any of the other groundbreaking devices and services that we’ve watched grow over the last decade. When I was using AltaVista I don’t remember anyone clearly saying they were missing a better search engine.

When the headphone jack was removed last year, the same kind of bashing happened. The Verge famously said that removing headphone jack was ‘user-hostile’ and stupid when the iPhone 7 was revealed. No more than 12 months later both Samsung and Google release new top of the line smartphones… without an headphone jack. I guess the ‘courage’ statement kinda makes more sense now?

As designers, a big part of our job is to think of solutions that we believe our users will benefit from. But in order for it to “hit the mark”, we need to know our users, their everyday lives, and what they are looking to get out of their experience with our products. Just designing great looking mockups is easy, making something useful is a lot harder.

A couple of weeks ago, another post surfaced; “Taking IKEA Out of Its Box and Redesigning It for 1.6B Users”. It’s a visual delight to look at the screens and there’s even some reasoning behind some of the decisions. Having just a quick look, I was amazed at some of the visual cues that had been incorporated. There’s a lot more drop shadows and weird shapes than I’ve ever seen IKEA communicate before. Hmm.

Normally, I just quickly scroll through these and close them, but because I have a lot of [experience working with IKEA and know a thing or two about their process, I wanted to continue reading. I scrolled down to the very end to find… “Note: this is a concept design case study, IKEA didn’t implement any of these designs.” (which also seems to be the only highlight of the post).

Designing a great product without knowing the

  • technical restrictions that are in place, your guess is as good as a random person on the street. Just “improving their search so it works” is easy to write in a post, but a lot harder to process in reality with thousands of products - all with variations - across multiple systems. This is similar to the scale that Apple has to design products for. Every second there’s more than 10,000 iPhones being produced simultaneously. What does this has to do with anything? Well, turns out, very few suppliers can meet that demand. So every piece of technology that Apple chooses to implement will need to be available at that scale. That’s a very different scenario than Apple was in just 5-7 years ago. So saying Apple was “innovative” back then, but now they’ve lost it, is really just half the story.
  • user base that you’re talking to, it’s really hard to design something that’s “for everyone”. Apple products are not just for the tech elite nor is the IKEA website for people on dribbble. The only way to design products that work is to find out more about what your users hope to achieve.
  • worst-case scenario for a template. Background images can have a light or a dark color scheme so adding text on top of an image needs to take that into account. Also, designing for IKEA or designing iOS requires all typography to work in multiple languages. The difference in length between English and Finnish is no joke. Also, we haven’t even started looking into Arabic languages and how everything will flow right-to-left rather than left-to-right.
  • accessibility requirements. When designing for millions, you’ll have at least tens of thousands of people that have an eye problem of some sort. Using tools like Stark is a great asset for this, but far too few people take the time to think about this.

Turns out, attacking a company is easy. Coming up with better, more friendly (for everyone) solutions is a lot harder. Brings me back to a favorite quote from Chuq von Rospach:

A lot of it boils down to this concept:

We demand Apple innovate, but we insist they don’t change anything.

Will I love the new iPhone X? I’m not sure at all to be honest, but I’m going to try it out before posting any unvalidated opinions on it. Rather than critiquing their inability to innovate or bashing their new design decisions, I’m eager to try something new. What about you?

It’s honest, authentic, and accessible.

I love sharing my experiences working in design and what’ve I’ve learned along the way. Join a community of thousands of designers, developers, and product professionals by signing up to my newsletter!

Not quite ready to sign up? I totally understand! Why not start by reading some of my past issues?

Great! Just “one more thing”...

You need to confirm your email to confirm your subscription.

  1. February, 2024

  2. January, 2024

  3. December, 2023

  4. November, 2023

  5. October, 2023

  6. September, 2023

  7. August, 2023

  8. July, 2023

  9. June, 2023

  10. May, 2023

  11. April, 2023

  12. March, 2023

  13. January, 2023

  14. December, 2022

  15. November, 2022

  16. September, 2022

  17. August, 2022

  18. July, 2022

  19. June, 2022

  20. May, 2022

  21. April, 2022

  22. January, 2022

  23. December, 2021

  24. November, 2021

  25. October, 2021

  26. September, 2021

  27. August, 2021

  28. July, 2021

  29. June, 2021

  30. May, 2021

  31. April, 2021

  32. March, 2021

  33. January, 2021

  34. November, 2020

  35. October, 2020

  36. September, 2020

  37. August, 2020

  38. June, 2020

  39. May, 2020

  40. April, 2020

  41. March, 2020

  42. February, 2020

  43. January, 2020

  44. December, 2019

  45. November, 2019

  46. October, 2019

  47. September, 2019

  48. August, 2019

  49. July, 2019

  50. June, 2019

  51. May, 2019

  52. April, 2019

  53. March, 2019

  54. February, 2019

  55. January, 2019

  56. December, 2018

  57. November, 2018

  58. October, 2018

  59. September, 2018

  60. August, 2018

  61. July, 2018

  62. June, 2018

  63. May, 2018

  64. April, 2018

  65. March, 2018

  66. February, 2018

  67. January, 2018

  68. December, 2017

  69. November, 2017

  70. October, 2017

  71. September, 2017

  72. August, 2017

  73. July, 2017

  74. June, 2017

  75. May, 2017

  76. April, 2017

  77. March, 2017

  78. February, 2017

  79. January, 2017

  80. December, 2016

  81. November, 2016

  82. October, 2016

  83. September, 2016

  84. August, 2016

  85. July, 2016

  86. June, 2016

  87. May, 2016

  88. April, 2016

  89. March, 2016

  90. February, 2016

  91. January, 2016

  92. December, 2015

  93. November, 2015

  94. October, 2015

  95. September, 2015

  96. August, 2015

  97. July, 2015

  98. June, 2015

  99. May, 2015

  100. April, 2015

  101. November, 2014

  102. April, 2013