5 ms·
This example made the point unbeknownst to the author. This Dieter Rams mantra is a recurring theme. What do you think about cockpits interfaces and Bloomberg
by rq1 7y ago
This example made the point unbeknownst to the author.
This Dieter Rams mantra is a recurring theme.
What do you think about cockpits interfaces and Bloomberg terminals? Should we add some more “white spaces”?
Prioritising information/functionality does not mean sacrificing their density.
- Damogran6 7y agoI think some things can be easy and some things must trade low learning curve for functionality. I highly doubt Airbus will produce a commercial airliner with a big red “fly to destination” button. (Though I’ve been wrong before)
- bch 7y agoI think your comment points out “context matters”. Cockpits aren’t consumer goods.
- kinkrtyavimoodh 7y agoYes but most consumers aren't uneducated idiots, and for the purposes of this discussion, there is nothing that specific about a cockpit that can't be true for a scientific calculator or an audio console. This attitude is how you get Macbook "Professional"s whose keyboards stop working in 2 months.
- meerita 7y agoIndeed. As a designer, I've seen 3000 DR articles. It's a pity designers abuse DR work just to justify their hedonisms. All apps I've seen with DR style have failed. I remember a bizarre podcast app for iOS in 2012 that was like insane DR nightmare and it was pleasant to eyes, but completely useless and utterly boring. It died against other options who were using generic iOS components. DR has born in another era of product design: most products had 1 or 2 features max. There were no playlists, no sharing, no connectivity, etc. It's easy to design when you have only those contraints.