Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Where There is No Vision, The People Perish


Published on

Most institutions think they have a solid mobile strategy, however most are wrong. Discussion will include decision making strategies for articulating your mobile vision, implementing responsive design, and deciding between building a "native" application versus mobile web applications.

Published in: Education
  • Be the first to comment

  • Be the first to like this

Where There is No Vision, The People Perish

  1. 1. Where There Is No Vision, The People Perish David J. Hinson, EVP & CIO Hendrix College
  2. 2. Alternate Translation:
  3. 3. Where There Is No Vision,The People Cast Off Restraint
  4. 4. Mobile First, Responsive WebDesign, Native Apps, And The WholeVision Thing
  5. 5. Mobile First
  6. 6. Luke Wroblewski, product designer,entrepreneur, author and speakerDesign with Mobile in mind,rather than the Desktop, FirstWith millions of mobile device activationsper day, people more likely to see your siteon mobile devices before they do ondesktopsLeads to better “full site” designs:simplify, prioritize, pick out the thingsthat really matterForces you to get down to the bare essenceof what makes your content workCapabilities that don’t exist on personal computers
  7. 7. Really big change to people’s processesand mindsetIt’s a lot of work
  8. 8. Responsive Web Design
  9. 9. Ethan Marcotte, web designer anddeveloperProcess of arranging layout so thatimportant information is presented in auser readable way, on any kind of deviceor screen sizeDesign meant to be viewed along agradient of different experiencesFluid grids, flexible images, media queriesSame code and content usedthroughout your site
  10. 10. It’s a lot of workCommon-denominator approach; eventhough it is meant to provide a “gradientof experiences”, not all experiences arecreated equally.Some duplicated content may benecessary; you may need to movecontent into areas that CSS can’t (now)accommodate (CSS Regions may providesome relief here).
  11. 11. WARNING: Humble brag, next 5 minutes
  12. 12. HTML5 / CSS3 Applications
  13. 13. Web applications written inHTML, Javascript,and CSSOften easier to develop thannative applicationsGenerally avoids device-specificdevelopmentFavors “reach” over “richness”Single code base across all platformsTitanium, Sencha, PhoneGap, and Mosync are examples of HTMLframeworks designed to support this model of development
  14. 14. A little more work to monetizeNo single authoritativesource for application“discovery”, beyond SEOThey look, act, and “feel”differently than native mobileappsAn active internet connection is (mostly) a mustCautionary (???) Tale: Facebook Mobile and HTML 5
  15. 15. Native Applications
  16. 16. A smartphone application thatis coded in a specificprogramming language,such as Objective C for iOSand Java for Androidoperating systems.Fast performance and a highdegree of reliabilityAccess to a phones various devices, such as its camera, accelerometer,compass, GPS, and address bookNative apps can be written to be used without an internet connectionTailored to the native capabilities of the device for which itis written: native APIs, specific hardware, and display form factors
  17. 17. For each native platform,expertise must be developedPlatform specialists aremore expensive per hour thanweb developers (generally)iOS development requiresMac OS X developmentmachines to run Xcode;Android may be developed using either Mac or PC; and so onDevice capabilities will prevent a uniform user experience from platformto platformArtwork and design assets, while sharable to some extent, must bespecialized by platformCode re-use between platforms? Aside from service / server side APIs,it’s a nice bed-time story to tell your kids
  18. 18. Yeah, Yeah Yeah. So What?
  19. 19. Before doing anything,
  20. 20. Define the problemyou’re solving, and what would constitute a successful outcome.
  21. 21. Who is your audience? What are their expected behavioral patterns?What kinds of devices do they carry?
  22. 22. Who “owns” your app? Who will maintain it?What skillsets do you currently have in-house?What is the expected lifetime of this app?
  23. 23. What will it cost to develop?Where does the money come from? Who decides on feature set? Who handles customer support?
  24. 24. Who performs QA?Who are your evangelists?Who is responsible for PR?Who declares “victory?”
  25. 25. Mobile Development Prime Directive: Strategize, then Operationalize What is the story you are trying to tell? NOT I have a hammer. Where are the nails?
  26. 26. Where There is No Vision,The People Perish
  27. 27. Questions?
  28. 28. Thank You! Twitter: @davidjhinson Email: hinson@hendrix.edu perish
  29. 29. Image Credits
  30. 30. Sites and Tools Mentioned
  31. 31. Sites and Tools Mentioned