An attempt at directed constructive UI feedback: I dont know if its considered useful to do a breakdown. Additionally I am really really loath to post this considering the amount of me too jump on band wagon let me chime in too posts. So, against my better judgement: Considering : https://vuo.org/node/424 Theres a lot going on here, so much visual noise for such a theoretically simple graph. I would highly advise that: • All nodes enter and exit a port at 0º and then curve. This adds visual padding / white space to the nodes and gives them room to breath • As Ive suggested before, reducing the complexity of the silhouette of a node would help legibility greatly. Theres a reason we dont read books using Serif, script fonts, and that designers nuance Helvetica all day long: because the visual work you do to parse each letter, word fragment, word, and white space is less. Consider each node like a letter, and design with legibility in mind. Im serious, you read the graph in a similar way. Simplicity is key. Being clear, Im not talking about the actual font used, but as a metaphor for the silhouette and lines in the graph as a whole. Designers design the entire page. Just because a single node looks good on its own is meaningless when many nodes sit together. Design for something like this is aggregate. Small noise compounds itself as nodes are added. For example: https://dropbox/s/2xghnvn57sfvs91/Screen%20Shot%202014-08-24%20at%2010.48.13%20AM.png?dl=0 - which would you prefer to read your technical literature in? • Remove as many additional visual metaphors as possible. In the above posted graph, there are lots of competing visual metaphors: Stacked inputs, exposed lists, exposed text editing inputs, and then the nested metaphor. Why not make these similar to nodes, with the same design language? Simplify. They add a whole additional visual layer to parse, each looks slightly different from the next, and break up the flow of the nodes. I would suggest using patch coords for those additional input data type modifiers and input elements, and keep the UI the same (similar to input splitters in QC). This is a small small list, but these 3 would make a huge huge difference in legibility. Ive ordered them in easiest to most complex and nuanced to change. I think the first 2 alone would go huge huge distances for increasing Vuo legibility. Thanks.
Posted on: Sun, 24 Aug 2014 16:25:42 +0000
Trending Topics
Recently Viewed Topics
© 2015