And of course this boxesandarrows.com and this boxesandarrows.com. I'd argue Josh, your Principles is the beginning of a Elements of Visual Style bokardo.com or at least interface style. What other conventions should we consider?
And of course this http://boxesandarrows.com/the-elements-of-style-for-designers/ and this http://boxesandarrows.com/putting-the-white-back-in-strunk-and-white/. I'd argue Josh, your Principles is the beginning of a Elements of Visual Style http://bokardo.com/principles-of-user-interface-design/ or at least interface style. What other conventions should we consider?
And of course this boxesandarrows.com and this boxesandarrows.com. I'd argue Josh, your Principles is the beginning of a Elements of Visual Style bokardo.com or at least interface style. What other conventions should we consider?
I think at some level there are concept-sharing techniques that both writing and UI design share. On the high level they might be like the lessons from Made to Stick. story, concrete, etc.
But more specifically they are things like "one idea per artifact" (screen, article) and "use appropriate connections" (next step, connecting words) etc.
Re writing conventions: when I was working on my book, I found a useful habit. I'd use it at the chapter level, at the paragraph level, and sometimes when I had a particularly rambunctious sentence. It was to stop, and ask myself "What am I trying to say?" WAITTS. I think many many interfaces would do well for the designer to do the same.
What is an amazon product page saying? It is safe to buy this product.
What is a google results page saying? We found everything and these are the best ten.
Here is a lens from Jesse Schell. artofgamedesign.com It may be a stretch, but I think it's worth asking what stories your users are telling themselves ABOUT themselves as they use your interface.
Again:
Amazon: I am a good shopper. I compare, but I don't waste time.
Google: I am a great research. I know how to find what I want.
Facebook: I am not alone. I have something to share. I have value.
Making kids: yay!
Making stories: yay!
What if an application is a novel or short story. It's worth knowing which, for structural purposes.
Then each screen a paragraph, each module a sentence. The elements have semantic relationships. Undo must go next to the do, just as an "un" goes next ot the word it belongs to.
I'm intrigued by the idea that the size of the application might have structural ramifications. We don't discuss that much.
Thanks for your feedback! Team Branch
Please refresh the page and try again.