iOS 7 and the Design Pendulum
Featuring Jony Ive, Scott Forstall
In 2013, Apple threw out seven years of accumulated visual language almost overnight. iOS 6 had been skeuomorphic: the Contacts app looked like a leather address book, Game Center had green casino felt, Calendar had stitched leather at the top. When Jony Ive took over software design after Scott Forstall's departure, iOS 7 went flat, thin fonts, translucent layers, bright colors, no textures. Half the design world cheered. The other half predicted users would revolt. Both camps missed the real lesson, and so did the flat purists who came next.
For anyone building a product, this is a case about a design decision that was right when you made it and may be quietly wrong now that your users have learned so much more. It sharpens the question of which interface pattern you still carry from an earlier version out of habit rather than need. Why skeuomorphism was correct for 2007 and wrong for 2013, why pure flat was a correction and not a destination, and what should actually drive the call, is the part the app saves for you.
Frequently asked questions
What changed with iOS 7's flat design?
In 2013, Apple replaced seven years of skeuomorphic visuals with a flat look: thin fonts, translucent layers, bright colors, and no textures. iOS 6 had mimicked real materials, such as leather in Contacts, green casino felt in Game Center, and stitched leather in Calendar, and iOS 7 swept all of it away.
Why did Jony Ive take iOS 7 flat after Scott Forstall left?
When Jony Ive took over software design following Scott Forstall's departure, he pushed away from skeuomorphism toward a flatter, more abstract visual language. The reasoning was that users no longer needed real-world textures to understand a touchscreen the way they had in 2007.
Why was skeuomorphism right for 2007 but wrong for 2013?
In 2007, leather and felt textures helped first-time touchscreen users understand what an element did, but by 2013 users had learned the conventions and the textures had become unnecessary decoration. The case argues that pure flat design was a correction rather than a final destination, since stripping away too many cues can hurt usability.
What can product and design teams learn from iOS 7?
A design decision can be right when you make it and quietly wrong once your users have learned more, so ask which interface patterns you still carry out of habit rather than need. User familiarity, not aesthetic fashion, should drive the call. CaseBook turns this into a move you apply to your own product, with an AI coach that reads your answer.