23 ms·
But there is a tension between badly implemented feature-rich solutions and well implemented special solutions and very often the specialized solution is much m
by atoav 7y ago
But there is a tension between badly implemented feature-rich solutions and well implemented special solutions and very often the specialized solution is much much better than anything else if it fits your usage.
I work with modular synthesizers and I certainly would use a well designed interface that knows it’s priorities over one that tries to make every parameter accessible and doesn’t priorize them in any way.
If all you want in a car radio is a USB charger and a volume control, a radio with just these two implemented in a deluxe variant (big knob with motor potentiometer?) would be better than say a super duper feature rich car radio that can do everything but hides it behind obscure button combinations and plastic encoders.
These complex all purpose devices of course also have their use cases. But very rarely any single user will need more than the most basic stuff.
Where it get’s dangerous, is when the general purpose device forgets to design these “90% of the time” use cases properly. So if you scientific calculator design makes it harder to do basic arithmetic, it is probably bad design. On the other hand if you leave out key scientific functionality because you want it to look sleek, it is also bad design.
Good design has to be based on real world usage and this is a very case-by-case thing. In the end we need to accept that it is hard to cover all use cases with one interface in a good way — so just make a more than one and let users switch.
- mark-r 7y agoI once had a car where I wanted to upgrade the stereo. Never did it, because the station buttons on the replacements were all too small.