A succinct way I’ve framed the split is that a front-of-the-front-end developer determines the look and feel of a button, while a back-of-the-front-end developer determines what happens when that button is clicked.
Doing it right requires a different pace of working and a much broader thought process than “ok, let’s get this thing out the door.” Which is super tough because most workplaces place a huge emphasis on getting things out the door, and fast. Little agile tickets that are expected to be completed in micro sprints to me seem to be antithetical to doing it right.
Ive and his team worked with Apple's Korean manufacturers to perfect the process of making the cases, and they even went to a jelly bean factory to study how to make translucent colors look enticing. The cost of each case was more than $60 per unit, three times that of a regular computer case. Other companies would probably have demanded presentations and studies to show whether the translucent case would increase sales enough to justify the extra cost. Jobs asked for no such analysis.
Topping off the design was the handle nestled into the iMac. It was more playful and semiotic than it was functional. This was a desktop computer; not many people were really going to carry it it around. But as Ive later explained:
Back then, people weren't comfortable with technology. If you're scared of something, then you won't touch it. I could see my mum being scared to touch it. So I thought, if there's this handle on it, it makes a relationship possible. It's approachable. It's intuitive. It gives you permission to touch. It gives a sense of deference to you.