|
From: Trond L. <tro...@be...> - 2016-04-11 07:48:01
|
I believe the key thing about design is that good design helps you use the tools in the best possible way, in other words good design gives the tools good affordance. This includes having the information available to you that you need (but not info that you don’t need), and having information layed out in a way that direct your intention towards the essential information, and that don’t strain you when working with it for prolonged periods of time. Sometimes this may mean very minimal interfaces, and at other times they’ll be complex. i-score probably need a bit of both - the score itself should present the outline of the score in a clean way that helps you getting an overview while also accessing and asserting the details of it. The inspectors obviously will be more complex, but even then, if they are designed well, they are accessible, and when they are not designed well it may make the whole application inaccessible. I believe that e.g. thinking of interaction with inspectors as stories may help improving the layout. If possible it would be very useful to have a session where Jean Michael and Stian Remvik could sit down together, Stian is really good at critically reviewing design for functionality. One hour with him prior to the release of the new version of the Jamoma web site probably improved the structure of the site by 40-50%. Best, Trond > On 07 Apr 2016, at 13:30, Pascal Baltazar <pa...@ba...> wrote: > > :-) > >> https://m.signalvnoise.com/why-i-love-ugly-messy-interfaces-and-you-probably-do-too-edff4a896a83#.p9yuw33b7 |