Your SlideShare is downloading. ×
User Experience Design
Upcoming SlideShare
Loading in...5

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

User Experience Design


Published on

User Experience Design

User Experience Design

  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

No notes for slide


  • 1. User eXperience Design @asadsafari For presenting on #TOSS
  • 2. User Experiencen. the overall experience andsatisfaction a user has whenusing a product or system
  • 3. User Experience is multifaceted
  • 4. Joshua Porter“The innovation in these applications is not that they let us do something new, but that they allow us to do what we already do better, more often, in more places, and more quickly. “(commenting on Web 2.0 interfaces)
  • 5. 6 LessonsAbout UX
  • 6. Lesson 1:Place better ‘experiences’ ahead of more features.
  • 7. Lesson 2:Start with actualexperiences.
  • 8. Cell phones do all kinds ofstuff—calling, textLesson 2:messaging, webbrowsing, contact Start with actualmanagement, music experiences.playback, photos and video—but they do it very badly, byforcing you to press lots of tinybuttons, navigate diverseheterogeneous interfaces andsquint at a tiny screen.“Everybody hates their phone,”Jobs says, “and that’s not a good
  • 9. Lesson 2:Start with actualexperiences.
  • 10. Lesson 3:Solve the realproblems.
  • 11. “Your phone’s got feet on,” hesays, not unkindly. “Why would Lesson 3:anybody put feet on a phone?” Solve the realIve has the answer, of course: “Itraises the speaker on the back the table. But the rightsolution is to put the speaker inthe right place in the first place.That’s why our speaker isn’t onthe bottom, so you can have iton the table, and you don’t needfeet.” Sure enough, no feet toethe iPhone’s smooth lines.
  • 12. Lesson 4:Play to think.
  • 13. The iPhone developed the way alot of cool things do: with a false Lesson 4:start. A few years ago Jobs Play to think.noticed how many developmentdollars were being spent... ontablet he had Apple engineersnoodle around with a tablet PC.When they showed him thetouch screen they came upwith, he got excited. So excitedhe forgot all about tabletcomputers.
  • 14. Lesson 5:Treatinterfaces likeconversations
  • 15. Lesson 5:When you need to dial, it shows Treatyou a keypad; when you needother buttons, the screen serves interfaces likethem up. When you want towatch a video, the buttons conversationsdisappear. Suddenly, theinterface isn’t fixed and rigid, it’sfluid and molten. Softwarereplaces hardware.
  • 16. Lesson 6:Obsess onthe details.
  • 17. Unlike most competitors, Apple also places an Lesson 7:inordinate emphasis on interface design. It sweats the Obsess oncosmetic details that don’t seem very important untilyou really sweat them. “I actually have a the details.photographer’s loupe that I use to look to make sureevery pixel is right,” says Scott Forstall, Apple’s head ofPlatform Experience (whatever that is). “We will argueover literally a single pixel.” As a result, when youswipe your finger across the screen to unlock theiPhone, you’re not just accessing a system of nestedmenus, you’re entering a tiny universe, where dataexist as bouncy, gemlike, animated objects that behaveaccording to consistent rules of virtual physics.
  • 18. So,what does UX Team do?
  • 19. We makeThings workFOR PEOPLE
  • 20. Things we’ll do (that you might care about)• map ‘stories’ back to Activities — so product releases make sense!• contribute to real product ownership (YEAH!)• create less rework• develop reusable code.• make our products more valuable
  • 21. “We set about rethinking the UI from the user’sperspective, which is ‘results-oriented,’ rather thanfrom the developer’s perspective, which tends tobe ‘feature-oriented’ or ‘command-oriented’–thereby enabling people to focus on what theywant to do rather than on how they do it.”(commenting on the new UI of Office 12)