1 / 20

Section 4: Why do an RIA Designing an RIA

Section 4: Why do an RIA Designing an RIA. Why?. Simply put … because you can. There is very little “should” here Looking back at John Maeda’s Laws of Simplicity Always question the addition of anything, even if it leads to the reduction of something else.

skylar
Download Presentation

Section 4: Why do an RIA Designing an RIA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Section 4: Why do an RIA Designing an RIA

  2. Why? Simply put … because you can. There is very little “should” here Looking back at John Maeda’s Laws of Simplicity Always question the addition of anything, even if it leads to the reduction of something else. Let’s look deeper at some good reasons why.

  3. Hello! Humans are Emotional Don Norman’s Emotional Design Your emotional state when using a product will effect not just your enjoyment of it, but your effectiveness (at least perceptual) with it. “Attractive Things Work Better” is the very title of the first chapter.

  4. Location, Location, Location That works for real estate … … for UX Designers … Context, Context, Context

  5. Intuitive ? Creating an intuitive application is all about matching expectations of the user. Understanding the context of use is the best way to come as close as possible to do that. The desktop is a constant. The Operating System is the heart and soul of the desktop experience.

  6. Legacy of the Web ? Strong legacy with web metaphors Back button (or just “history”) Hyperlink

  7. RIAs offer Hybridization Toyota can’t have all the fun … Big challenges for designers, but the end-game is worth the effort. Yahoo Mail Beta Flickr

  8. Learnability Understanding where I was and where I’m going. Having the RIGHT information at the right time, with the right supporting information.

  9. Security Using windowing enhances security I know that I really didn’t leave I know when I’m done I’ll be going back to where I started Security allows for more risk taking

  10. Managing Complexity Discoverability Use scent to guide people Hide complexity to avoid overwhelming people with too much content Richness allows for fluidity and better invitations Baby Name Wizard

  11. Power of Movement Sometimes contrasts in color, shape, alignment are not enough Moving objects catch our eyes and our mind’s attention Time is perception Motion (and change) = activity Perception of system working if not faster, at least working for my benefit. Yahoo! Maps (beta)

  12. Playful Using your hands in multiple ways Novelty through animation and discoverability Engagement leads to productivity

  13. Design (Big ‘D’) “I design software” “I’m wearing designer jeans” “interaction design” “design school” “That design looks cool”

  14. What is “design”? • Design as noun (I like that “design”) • Is the result of a conceived idea, whether or not it was actually “designed” • Design as verb (I “design” software) • A process of creativity • Non-linear • Assumes there is more than one elegant solution to any single problem • Considers the measurable and the aesthetic

  15. Making Design (verb) Work • Divergent thinking • Skew, bend, melt, tear … change! • Evaluation is separate from Ideation • Put your judge on hold • Multiple minds • Model, Model, Model (AKA: sketch, sketch, sketch) • Taking the road least traveled can bring you back to the freeway • Process ideas in disconnected ways • Connect disconnected ideas in separate exercise

  16. Exercise: Criteria From Section 1 • Criteria for the design • Application Service (Hosted) • Infinite Audience • Business-to-Business community • File Management System • Moving lots of files • Collaborative • Media Centric • Criteria for Development • Old-school software engineering; • Highly formally educated group

  17. Exercise: Moving forward • Need to share corporate media objects across different enterprises • Need to collaborate on these objects • Annotate • Version • Append • Need to publish out to 3rd parties Don’t worry we aren’t doing this whole application …

  18. Exercise: Annotate Design a set of screens that make up one page • Displays both a list objects and single object • Allows the user to comment on that object • Track commenting • Annotate on media directly • Create a collection and “send” that collection

  19. Things to think about • Manage complexity through progressive presentation • Motion aids learnability • Prirotize information and tasks within a single context • “Do I need a new context?” “Why?” “Why not?” • “What is the nature of my data for this context?”

  20. Questions ? Resources: Dave’s Blog: www.synapticburn.com Bill’s Blog: looksgoodworkswell.blogspot.com

More Related