Optimizing Sites for Mobile Devices

2,447 views

Published on

Making sure your site works as well on mobile devices as it does on desktop can be frustrating. This presentation gives an overview of techniques you can use from planning to delivery to help make sure your site performs well across devices

Published in: Design, Art & Photos, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,447
On SlideShare
0
From Embeds
0
Number of Embeds
182
Actions
Shares
0
Downloads
45
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Optimizing Sites for Mobile Devices

  1. 1. Optimizing sites forMOBILE DEVICES james williamson | lynda.com
  2. 2. Howdy again y’all james williamson | senior author @jameswillweb on the Twitter
  3. 3. Today I want to talk about techniques youcan use to plan and develop sites so they perform well on mobile devices. (it’s kind of a big deal)
  4. 4. We are now in the age of mobile500 million 180 million presentCambrian Jurassic Cupertino
  5. 5. Or are we?It might be more accurate to call it“The Age of Constant Connectivity”
  6. 6. This means that over time we need tochange the way we approach design. We need a fundamental shift in content planning and site architecture to help usdesign always-connected user experiences
  7. 7. ...but that’s an entirely different presentation (maybe next year) However, it’s now critical for you to have a strategy in place for how your site looks and performs on mobile devices.
  8. 8. So what does that entail?Changing the way we plan sites to include mobileUsing responsive design techniques that allow flexible layoutsManaging resources responsiblyTaking advantage of device capabilities
  9. 9. Planning for mobileMobile needs to be an equal partner, if not theprimary platform you design towards Check out Mobile First* Popularized by Luke Wroblewski, it emphasizes starting the design process with mobile in mind. *http://www.lukew.com/presos/preso.asp?26
  10. 10. Remember contexts when designingMobile devices are always on andalways there fat-fingers... 44px x 44pxMobile users are not distracted, noton-the-go, and not disengagedDon’t block access becausesomeone’s on a mobile deviceMobile capabilities increase what you The Thumb Zonecan do, not limit you!
  11. 11. Use responsive design techniques Fluid grids Media Queries Responsive ImagesResponsive Web Design by Ethan Marcottehttp://www.abookapart.com/products/responsive-web-design
  12. 12. Use fluid layouts with breakpointsdesktop tablet mobile DESOLVE DESOLVE fine urban photography DESOLVE GALLERIES GEAR INTERACT SHOP GALLERIES GEAR INTERACT SHOP GALLERIES GEAR INTERACT SHOP WE LOVE URBAN PHOTOGRAPHY explore our photos our favorite equipment contact, follow, or submit your own buy our stuff We’re betting you do to. Welcome to our site, a growing collection of gal- We’re betting you do to. Welcome leries taken by a small group of pas- to our site, a growing collection of WE LOVE URBAN PHOTOGRAPHY sionate urban photographers. Visit our galleries taken by a small group of galleries, buy some of our prints, or passionate urban photographers. drop us a line. While you’re at it, feel Visit our galleries, buy some of our free to submit a gallery of your own. prints, or drop us a line. While Welcome. you’re at it, feel free to submit a gallery of your own. Welcome. We’re betting you do to. Welcome to our site, a growing collection of WE LOVE URBAN PHOTOGRAPHY galleries taken by a small group of passionate urban photographers. Visit our galleries, buy some of our prints, or drop us a line. While you’re at it, feel free to submit a gallery of your own. Welcome.Don’t lock breakpoints into fixed sizes (960px, 720px, 320px),keep layouts fluid within your breakpoints to account formultiple devices and screen sizes
  13. 13. Calculating percentage-based element widthsFor each breakpoint, determine an “ideal” target size(For example 960px for desktop)Determine percentages based off this target sizeMargin and padding values are calculated as percentages ofthe containing block (the parent element)
  14. 14. It’s not always going to be this hardFlexbox is coming! (http://www.w3.org/TR/css3-flexbox/)Other layout modules are being designed with mobile in mindGrid template, CSS Regions, Multi-column Layout, etc.(check out www.w3.org/Style/CSS/current-work.en.html for more info)
  15. 15. Using Media Queries CSS Media Queries allow you to control the application of styles based on the presence or absence of specific media features@media  only  screen  and  (max-­‐width:480px)  {  ...  } like viewport width!
  16. 16. Media Query syntax link  rel="stylesheet"  href="desktop.css"  media="[not  |  only  ]  screen  [and]  (expression)" or@media  [not  |  only  ]  screen  [and]  (expression)  {      } The keywords “not”, “only”, and “and” can be used to filter results, while expressions can be used to check for specific media features
  17. 17. Media Query syntaxMedia Featureswidth* color*height* color-­‐index*device-­‐width* monochrome*device-­‐height* resolution*orientation scanaspect-­‐ratio* griddevice-­‐aspect-­‐ratio* *accepts “min-” and “max-” prefixes
  18. 18. Meta Viewport tagsMeta viewport tags can be combined with mediaqueries to help ensure consistent experiences. CSS @viewport may eventually replace <meta  name="viewport"  content="width=device-­‐width,   initial-­‐scale=1.0"> for example, this meta viewport sets the viewport to the device width and sets the initial zoom to 100%.
  19. 19. Strategies for using media queriesUse inline syntax to reduce http requestsUse width instead of device-width to target viewportsCombine them with global styles for more maintainable code
  20. 20. Responsive Images Live Wo r m s Yeah, that.
  21. 21. Responsive Image challengesDesktop and mobile layouts usually require different image sizesLarger images add unnecessary overhead for mobile devicesScreen density differences now allow the use of higherresolution images for some screens
  22. 22. Responsive Image techniquesUse Background ImagesThrough media queries, you can change image requests basedon layout (Android 2.3 > still downloads ALL background-images)Larger decorative background images will clip if inside a fluidparent elementSince no img element is used, images are non-semantic
  23. 23. Responsive Image techniquesMake images fluidBy setting width or max-width to percentage values, you canmake images scale along with layoutStill forces mobile devices to download large image sizesImage scaling can harm performance on mobile devices
  24. 24. Responsive Image techniquesUse javascript to replace imagesUse javascript to determine which image is appropriate and thenserve that imageMultiple libraries have been created to enable thisCan be tricky to ensure that only the image you want isdownloadedIf the technique requires you to remove the src attribute, yourcode become non-semantic
  25. 25. WHATWG to the rescue?!Recently, the WHATWG added the srcset attribute to the img tagThis allows you to pass a comma separated list of multipleimages and the conditions (width, height, resolution) that triggertheir useCurrent unsupportedIgnored the recommendation of the Working Group thatproposed the picture elementIs a big mess
  26. 26. Managing resources Why the hell isn’t this faster?!! Mobile devices deal with a combination of varying bandwidth and latency issues.You can ease your users pain by managing resources wisely.
  27. 27. Fewer server requests are betterCondense multiple CSS and javascript files into single files whenpossibleMinify scripts and files and use gzip compression to reduce file sizeUse CSS Sprites to limit image requestsUse data-URLs in place of images when feasibleIn many instances CSS can be used in place of images
  28. 28. Only load resources if you need themOften, external scripts won’t be used on pages or on mobiledevices at allUse asynchronous loading and detection scripts to serve only whateach context needsThere are multiple options available, but Modernizr 2.0 combinesfeature detection, media query testing, and yepnope.js to give youa robust set of options (http://modernizr.com)
  29. 29. Take advantage of mobile capabilities Embrace the Possibilities
  30. 30. Mobile device capabilitiesGeolocationOrientation / AccelerometersSMSTouch / Gesture supportAudio & Video captureOMG! THEY CAN MAKE PHONE CALLS (some of them) Thinking about these capabilities during the planning process can result in more fulfilling user experiences
  31. 31. HTML5 and standards can helpAPIs for Geolocation, Touch Events, and SMS can helpmake it easy to add these capabilities to your siteHTML5 form elements are well supported in mobilebrowsersHTML5 audio/video formats are widely supported
  32. 32. Testing...testing...testingAlways test your site on as many browsers and devicesas you canEmulators are good, but actual devices are betterPay as close attention to loading times and serverrequests as you do page layout or functionality
  33. 33. Testing...testing...testingWeb Inspector Remote (weinre) | remote debugginghttp://people.apache.org/~pmuellr/weinre/Webkit Remote Debugginghttp://www.webkit.org/blog/1620/webkit-remote-debugging/Blaze mobile testing | Mobile performance testinghttp://www.blaze.io/mobile
  34. 34. A few things to remember....Make mobile an equal partner when planning and designing your sites.Use standards-compliant, clean, accessible code as the foundation forall your sites.Create responsive designs that work across multiple screensMange resources carefully and limit server requestsTake advantage of device capabilities to enhance user experiences
  35. 35. THANK YOUjames williamson | lynda.com jwilliamson@lynda.com@jameswillweb on the Twitter www.simpleprimate.com

×