Design for Software : A ux playbook
- 19. v
Editor's Notes
- #4: 10 years in the making
- #5: The market is getting saturated with developersSoftware is getting easier to writeHybrids are starting to be the most valued employeesMany people think design is magic only creative people can design. Thats not true. Devs are highly creative problem solvers.
- #6: Took me the better part of a decade to create a design process that makes sense for software.These 10 things are the things I wish I knew as a new designerThis is not the typical abstract design talk. These are real nuggets of information you can use tomorrow to enhance your software.Best for something and worst for something else. Cherry pick what makes sense for you.
- #10: Photo from:http://www.uiowa.edu/~calvin/Old_Science_Hall.htm
- #11: There are many types of research. I choose to do the most obvious one, because it is easy and painless.
- #12: The most basic form of research is user interviews. Motivations are the triggers that lead to desirable behaviors. This is the most powerful research technique you can use. There are plenty more forms of research, but if you arent doing any of them today, this is where you should start.
- #14: Case Study from Adaptive Path:http://www.adaptivepath.com/ideas/charmr-initial-feedback
- #16: This is when I started realizing that other peoples designs had an element of polish mine didnt.
- #17: These are the places I find most of my inspiration now.
- #18: This can be a great way to start collecting ideas. And reference then in the future.
- #20: Specific Knowledge of products and people + general knowledge of life and event = ideas.
- #25: If there was only one think you took away from this talkthis would be it.
- #27: Define patterns Be consistentReduce steps
- #28: Borrow ideas from other industries
- #32: Establish layout patterns Visualize interactionsGet stakeholders buy-in
- #37: Picture from Wikipedia. ENIAC the firstcomputerhttp://en.wikipedia.org/wiki/ENIAC
- #38: Too many people get hung up on the word innovate. The ability to fail fast is invaluable in an organization that is used to throwing money away.
- #40: Muscle fatigue happens really quickly. 55 in touch screen examplePeripheralADA concerns
- #43: Interactive prototyping is really the focus
- #44: Sketching in c#This can be really powerful. Some times you can easily animated the visuals and get a sense for the way the software feels. This can be done with the storyboards built into wpf or silverlight. You can also use applications like Microsoft Sketchflow.
- #47: Quote from Anchor Man:http://www.imdb.com/title/tt0357413/Seriouslyno matter how low the fidelity isa working prototype will be more well received compared to a static comp.
- #48: Time check28 Min Elapsed16 Min Remaining
- #56: This is pretty hard stuff. I feel like I barely have scratched the surface of type. Its something of an underground cult thing.But when its done right it can make all the difference. Simple rule of thumb for mixing serifs and san-serifs. Thanks to Robby for the inspiring talk from MIXhttp://channel9.msdn.com/events/MIX/MIX11/EXT02
- #57: Discordance when you dont use sizes in a scale These two scales will suit most typographic needs
- #61: Simplicitywhat is your design really saying?Clean UI?ConsistencyLogically organizedAnd
- #62: Rule of thumb:Groupingby size, content, color, action.I identify the relationships between the elements on the screen then start to group them.
- #63: Grouping of artists, albumb, and songs. All visually similar .
- #67: Aligning things to a grid is the simplest way to create order and hierarchy. I usually tend to design by gut.then align to a grid. Some people put the grid on the pagefirst thing they do.
- #68: Thanks again to Robby Ingerbretson for his awesome slides on design 101. Check out his work here: http://nerdplusart.com/
- #75: Photography :http://www.flickr.com/photos/cubagallery/3643547984/
- #80: What? Windows apps do this the best?