uxjulie:

If you need to explain responsive to someone, check out Responsive Layouts, Responsively Wireframed by @thismanslife, an awesome way to demo concept of responsive layouts to non-web-geeks via @boagworld

(via AIGA)

Books

• Communicating Design: Developing Web Site Documentation for Design and Planning (New Riders) by Dan M. Brown
• Sketching User Experiences: Getting the Design Right and the Right Design (Elsevier) by Bill Buxton
• Subject To Change: Creating Great Products and Services for an Uncertain World (Adaptive Path for Design/O’Reilly) by Peter Merholz, Todd Wilkens, Brandon Schauer and David Verba
• Inspired: How To Create Products Customers Love (SVPG Press) by Marty Cagan
• The Designful Company (New Riders) by Marty Neumeier
• Universal Principles of Design (Rockport) by William Lidwell
• Lots of books published by Rosenfeld Media

Websites

• DesignMind 
• Quora: UX Design 
• Ninakix’s Posterous
• Teehan+Lax’s blog
• Ambidextrous
• A List Apart
• Swipe
• iOS HIG
• IxDA discussion boards 
• “Implementing a Pattern Library in the Real World” by Erin Malone, Matt Leacock and Chanel Wheeler, boxesandarrows.com
• Scrum Alliance
• Luke W’s blog

Technology

• jQuery Mobile
• Sencha

Tools

• iOS (sign-up required)
• Android SDK
• Prototypes
• Live View
• EightShapes wireframing plug-ins

(via AIGA) the cities with the highest demand for freelancers in the interactive design space are:

• San Francisco/Silicon Valley
• Los Angeles
• New York
• Portland, OR
• Seattle, WA

• Publish your application’s goals and objectives, your “mission statement” if you will.
• The less choices you present to the user, the better. Users get confused rather quickly.
• User Interface should remain consistent from screen to screen.
• No “Smart Menus” that change depending on how you use the application. Users hate their application “changing” on them.
• Keep the “Noise” to a minimum. People don’t need to know about the business as usual messages. Don’t annoy your user.
• Avoid acronyms if at all possible. If you must use them, supply a descriptive message right beside it.
• Your application must run lean and mean. As pretty as your interface might be, if the software seems slow, no sale.
• Let them explore the application, without fear they will cause a disaster. Undo, Redo, and History features might be a good idea.
• Ensure your software works the first time its run.
• Configurations can occur later, but out of the box, you should have intelligent defaults.
• Have an easy way of allowing your users to provide feedback.

• Information Architecture
• Interaction Design
• Usability Engineering
• Visual Design
• Prototype Engineering