1 / 60

Prepare for the Mobilacalypse

Slideshow about Prepare for the Mobilacalypse by Jeff Eaton

eaton
Download Presentation

Prepare for the Mobilacalypse

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. 2 preparing for the mobilacalypse why mobile sites are doomed, why the future is made of structured content, and how to build without breaking the bank

  2. 4 hi. i’m @eaton! i’m with lullabot. we plan, design, build, and teach.

  3. 6 mo·bil·ac·a·lypse (n) 1) The tipping point that occurs when building for one channel locks out a majority of users, but building for many bankrupts you.

  4. 7 you might want to leave now if… ‣ You don’t manage or publish content ‣ You have infinite budget, unlimited staff ‣ You’re retiring in 2014 ‣ Otherwise? Stick around, tweet to #postmobile

  5. 8 change is here

  6. 9 1. Mobile users are here, now

  7. 10 ‣88% of U.S. adults have cell phones ‣47% use their phone for browsing ‣15% use their phone for most browsing ‣25% of teens & minorities, 45% of girls

  8. 11 1. Mobile users are here, now 2. They want the same stuff

  9. 12 ‣75% of mobile usage is home or office ‣90% split tasks between devices ‣65% shopped on phone, purchased on PC ‣68% avoid desktop if mobile doesn’t satisfy ‣15% of U.S. adults are “mostly mobile”

  10. 13 1. Mobile users are here, now 2. They want the same stuff 3. Building separate sites kills

  11. 14 “The challenge for most organisations in the long run won’t be maintaining multiple sets of frontend code or different templates. It will be maintaining variations of duplicate content. Karen McGrane: A Separate Mobile Site? No Forking Way

  12. 15 1. Mobile users are here, now 2. They want the same stuff 3. Building separate sites kills 4. Responsive design is overtaxed

  13. 16 ©2012 Lyza Danger — http://flic.kr/p/cfkULL

  14. 17 BMW iDrive system — http://www.bmwcoop.com.

  15. 18 Google Glass breaks every web site’s interaction model. Sigh.

  16. 19 Drupal.org on my living room television. No, seriously.

  17. 19 100 75 50 25 Time Warner Dish DirecTV Comcast XBox Live PlayStation 46m on XBox Live Drupal.org on my living room television. No, seriously.

  18. 20 1. Mobile users are here, now 2. They want the same stuff 3. Building separate sites kills 4. Responsive design is overtaxed 5. New channels keep coming

  19. 23 Apps Search Social Email Print Web Feeds APIs

  20. 24 “People don't want different content or less content. They imagine that their devices are different windows on the same content, not entirely different containers. Karen McGrane, A List Apart

  21. 25 mo·bil·ac·a·lypse (n) 1) The tipping point that occurs when having for one channel locks out a majority of users, but building for many bankrupts you. 2)The revelation of a new way to publish content

  22. 26 there is a solution

  23. 27 “Rather than thinking primarily about the final presentation — publishing web pages, mobile applications or brochures — an information- centric approach focuses on ensuring our data and content are accurate, available, and secure. Whitehouse.gov, Digital Government Blueprint

  24. 28 1. Manage one pool of content

  25. 29

  26. 29

  27. 30 NPR COPE Create Once Publish Everywhere

  28. 30 NPR COPE ‣ Desktop

  29. 30 NPR COPE ‣ Desktop ‣ Mobile

  30. 30 NPR COPE ‣ Desktop ‣ Mobile ‣ iPhone

  31. 30 NPR COPE ‣ Desktop ‣ Mobile ‣ iPhone ‣ Android

  32. 30 NPR COPE ‣ Desktop ‣ Mobile ‣ iPhone ‣ Android ‣ Partner

  33. 30 NPR COPE ‣ Desktop ‣ Mobile ‣ iPhone ‣ Android ‣ Partner ‣ Microsite

  34. 30 NPR COPE ‣ Desktop ‣ Mobile ‣ iPhone ‣ Android ‣ Partner ‣ Microsite ‣ Youtube

  35. 30 NPR COPE ‣ Desktop ‣ Mobile ‣ iPhone ‣ Android ‣ Partner ‣ Microsite ‣ Youtube ‣ Social

  36. 31 1. Manage one pool of content 2. Structure content for remixing

  37. 32 Story title subtitle shortTitle teaser miniTeaser slug text textWithHtml thumbnail storyDate pubDate audio audioDuration audioDescription audioMp3 image pullQuote relatedLink keywords organization listText correction Program Series Blog

  38. 33 Flexible chunks beat content blobs

  39. 34

  40. 35

  41. 36 1. Manage one pool of content 2. Structure content for remixing 3. Decouple content, presentation

  42. 37 http://api.npr.org/query? fields=title,teasers &format=NRML &id=170510189 &apiKey=MDEwNzg…

  43. 38 <story id="161551774"> <link type="html">http://www.npr.org/2012/09/21/16…</link> <link type="api">http://api.npr.org/query?id=161551774</link> <link type="short">http://n.pr/Sc6mZV</link> <title>Printing Solar Panels In The Backyard</title> <teaser> With crowd-sourced funding through Kickstarter, a team of inventors are building a Solar Pocket Factory: a machine designed to print micro solar panels. Co-inventor Shawn Frayne stopped by Flora Lichtman's backyard with a few pieces of the prototype to explain how the machine works. </teaser> <miniTeaser> A Kickstarter-funded project aims to build a machine to print micro solar panels. </miniTeaser> </story>

  44. 38 <story id="161551774"> <link type="html">http://www.npr.org/2012/09/21/16…</link> <link type="api">http://api.npr.org/query?id=161551774</link> <link type="short">http://n.pr/Sc6mZV</link> <title>Printing Solar Panels In The Backyard</title> <teaser> With crowd-sourced funding through Kickstarter, a team of inventors are building a Solar Pocket Factory: a machine designed to print micro solar panels. Co-inventor Shawn Frayne stopped by Flora Lichtman's backyard with a few pieces of the prototype to explain how the machine works. </teaser> <miniTeaser> A Kickstarter-funded project aims to build a machine to print micro solar panels. </miniTeaser> </story>

  45. 39 is this the scheduled WYSIWYG rant? yes. ‣With multichannel, WYSIWYG isn’t. ‣“Dreamweaver fields” kill reuse ‣Limit allowed tags, watch for abuse ‣Aim for rich text, not full HTML

  46. 40 1. Manage one pool of content 2. Structure content for remixing 3. Decouple content, presentation 4. Payoff?

  47. 41 “Having an API allows us to be highly efficient at building new platforms. We build the presentation, and the ‘data’ is already ready to go. In 12 months we doubled our online audience and launched 11 products, including a site redesign, with limited dev resources. NPR, What We Did Wrong: NPR Improves Its API Architecture

  48. 42 making it happen

  49. 43 So. Much. Work. This man just read a case study about COPE transforming NPR’s business, but he needs to redesign a florist’s web site.

  50. 44 1. Identify your assets

More Related