Android Design

Uploaded on


More in: Design
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    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
  • His need is checking email, he might have installed multiple email servers, and would want to check them right away. Notifications are good, but if he could see some of them
  • Provide resources for different screen densities (DPI) to ensure that your app looks great on any device.
  • Scale down and figure out the UI compromises you'll need to make on smaller screens
  • The Android design language relies on traditional typographic tools such as scale, space, rhythm, and alignment with an underlying grid. Successful deployment of these tools is essential to help users quickly understand a screen of information. To support such use of typography, Ice Cream Sandwich introduced a new type family named Roboto, created specifically for the requirements of UI and high-resolution screens. The current TextView framework supports regular, bold, italic, and bold italic weights by default.
  • Devices vary not only in physical size, but also in screen density (DPI). To simplify the way you design for multiple screens, think of each device as falling into a particular size bucket and density bucket. The size buckets are handset(smaller than 600dp) and tablet (larger than or equal 600dp). The density buckets are LDPI, MDPI, HDPI, and XHDPI. Optimize your application's UI by designing alternative layouts for some of the different size buckets, and provide alternative bitmap images for different density buckets.
  • A beautiful surface, a carefully-placed animation, or a well-timed sound effect is a joy to experience. Subtle effects contribute to a feeling of effortlessness and a sense that a powerful force is at hand.
  • Allow people to directly touch and manipulate objects in your app. It reduces the cognitive effort needed to perform a task while making it more emotionally satisfying.
  • Learn peoples' preferences over time. Rather than asking them to make the same choices over and over, place previous choices within easy reach.
  • People love to add personal touches because it helps them feel at home and in control. Provide sensible, beautiful defaults, but also consider fun, optional customizations that don't hinder primary tasks.
  • Use short phrases with simple words. People are likely to skip sentences if they're long
  • Consider using pictures to explain ideas. They get people's attention and can be much more efficient than words.
  • Take your best guess and act rather than asking first. Too many choices and decisions make people unhappy. Just in case you get it wrong, allow for 'undo'.
  • People get overwhelmed when they see too much at once. Break tasks and information into small, digestible chunks. Hide options that aren't essential at the moment, and teach people as they go.
  • Save what people took time to create and let them access it from anywhere. Remember settings, personal touches, and creations across phones, tablets, and computers. It makes upgrading the easiest thing in the world.
  • Help people discern functional differences by making them visually distinct rather than subtle. Avoid modes, which are places that look similar but act differently on the same input.
  • Like a good personal assistant, shield people from unimportant minutiae. People want to stay focused, and unless it's critical and time-sensitive, an interruption can be taxing and frustrating.
  • Not all actions are equal. Decide what's most important in your app and make it easy to find and fast to use, like the shutter button in a camera, or the pause button in a music player.
  • People feel great when they figure things out for themselves. Make your app easier to learn by leveraging visual patterns and muscle memory from other Android apps. For example, the swipe gesture may be a good navigational shortcut.
  • Break complex tasks into smaller steps that can be easily accomplished. Give feedback on actions, even if it's just a subtle glow.
  • Make novices feel like experts by enabling them to do things they never thought they could. For example, shortcuts that combine multiple photo effects can make amateur photographs look amazing in only a few steps.
  • Be gentle in how you prompt people to make corrections. They want to feel smart when they use your app. If something goes wrong, give clear recovery instructions but spare them the technical details. If you can fix it behind the scenes, even better.


  • 1. AndroidDesignShyamala Prayaga
  • 2. About Me Passionate User Experience Evangelist My Experiences  Pramati  Kony Solutions  Yodlee  Mindtree  AOL
  • 3. Today’s agenda Understanding need and context Android design challenges Android design goals Process
  • 4. Understanding need and context
  • 5. About the persona Name: Rex Lee Age: 28 Occupation: Businessman Interest: Travelling, playing guitar, listening music and photographyTechnology freak, Android and smartphone user
  • 6. Needs
  • 7. Checking mails
  • 8. Mobile Banking
  • 9. Socializing with friends
  • 10. Photography
  • 11. Navigation
  • 12. Listening music
  • 13. Latest updates
  • 14. Online shopping
  • 15. Context of use
  • 16. While driving
  • 17. Dining
  • 18. Work
  • 19. Challenges
  • 20. ProblemNeed to launch frequently usedapps from the menu
  • 21. SolutionIntegrate Widgets forfrequently used tasks
  • 22. SolutionIntegrate Notifications for Time Sensitive Events
  • 23. ProblemNeed to share news, information,pictures, notes etc with friends
  • 24. SolutionIntegration with social media
  • 25. ProblemContent is buried deeper in app.
  • 26. SolutionShow Interesting results immediately
  • 27. ProblemNeed to get in touch with contacts via mail, messenger, callfrom one application
  • 28. SolutionCross application access andIntegration
  • 29. Some Statistics
  • 30. Metrics Androidis the fastest growing mobile platform in the world More than 850,000 Android devices are activated each day Morethan 300 million Android devices have been activated globally
  • 31. How do I translate my websites experience to a phone or tablet experience?
  • 32. How do I best realize my service as a singleextended experience?
  • 33. Thinking Mobile Focus on essential use cases  Important things must be fast  Manage progressive complexity Double-down on emotional engagement  The magic of direct manipulation  Aesthetics & hero moments
  • 34. Thinking Mobile Contd… Take advantage of uniquely mobile opportunities Fear complex navigational models
  • 35. The consistency paradox Productconsistency  The same product experience on different devices
  • 36. My take on dealing with paradox Start from device consistency
  • 37. My take on dealing withparadox Fit as much product consistency
  • 38. My take on dealing withparadox breakdevice consistency in narrow, targeted ways
  • 39. Android Design Challenges
  • 40. Screen Size
  • 41. SolutionWork in the base standard (medium size, MDPI) and scale it up ordown for the other buckets
  • 42. Solution Start with the device with the largest screen size Scale down for smaller screen
  • 43. Diagram of various screenconfigurations
  • 44. Typography Limited fonts available can bundle external fonts
  • 45. Typographic Scale Android framework uses limited set of font size -* scale-independent pixels (sp)
  • 46. Screen pixel densitydensity-independent pixels (dp)
  • 47. Solution Categorize devices into size and density buckets The density buckets are LDPI, MDPI, HDPI, and XHDPI Provide alternative bitmap images for different density buckets
  • 48. Other challenges Radios,sensors, and feedback  WiFi? 3G? 4G? Bluetooth?  Front and rear-facing cameras  Haptic (vibration) feedback  GPS/Compass/accelerometer/NFC Screenaspect ratio  Primary / secondary orientations
  • 49. Android Design Goals
  • 50. Android design goals Enchant me Simplify my life Make me amazing
  • 51. Enchant me
  • 52. Delight me insurprising waysA beautiful surface A carefully-placed animation Well-timed sound effect Animated live wall paper which changes according to climate
  • 53. Real objects are more fun than buttons and menus Allow people to directly touch and manipulate objectsTouch collage to add photos, touch photos to change them
  • 54. Get to know me  Learn people’s preferences over time  Remember previous choices Seat selection choice for an airline booking app
  • 55. Let me make itmine People love to add personal touches Helps them feel at home and in control Personalized wallpaper selection
  • 56. Keep it briefUse short phrases with simple words
  • 57. Pictures arefaster than words Consider using pictures to explain idea Pictures get people’s attention Can be efficient than words
  • 58. Decide for mebut let me havethe final say Provide smart option based on user actions Allow undo if something went wrong
  • 59. Only show what I need when Ineed it Teach people as they go
  • 60. Never lose my stuff Remember settings, personal touches, and creations
  • 61. Simplify my life
  • 62. If it looks the same, it shouldact the same Help people discern functional differences by making them visually distinct
  • 63. Only interrupt me if it’simportant shield people from unimportant minutiae
  • 64. Make important things fast Decide whats most important in your app Make it easy to find and fast to use
  • 65. Make me amazing
  • 66. Give me tricks that workeverywhere Make your app easier to learn by leveraging visual patterns
  • 67. Sprinkleencouragement Break complex tasks into smaller steps Give feedback on actions
  • 68. Do the heavy liftingfor me  Make novices feel like experts by enabling new tasks
  • 69. It’s not my fault Be gentle in how you prompt people to make corrections If something goes wrong, give clear recovery instructions
  • 70. Process
  • 71. Establish shared, ambitiousUX goals
  • 72. Iterate and validate
  • 73. Explore designs
  • 74. We are all user experienceadvocates
  • 75. Resources
  • 76. Questions