Se ha denunciado esta presentación.
Utilizamos tu perfil de LinkedIn y tus datos de actividad para personalizar los anuncios y mostrarte publicidad más relevante. Puedes cambiar tus preferencias de publicidad en cualquier momento.

Shaping a Technology Strategy for Mobile Development

4.404 visualizaciones

Publicado el

Publicado en: Tecnología, Diseño
  • Sé el primero en comentar

Shaping a Technology Strategy for Mobile Development

  1. 1. Shaping a Technology Strategyfor Mobile DevelopmentALEX CONCONI© 2013 frog - All rights reserved
  2. 2. Alex ConconiAssociate Technology Directoralex.conconi@frogdesign.com@aconconi
  3. 3. Background
  4. 4. “The web isdead.Apps are thepresent andthe future.”Keith Teare, MBLT 2013
  5. 5. “We provide our customerswith native applications onseveral platforms to accessour online services.Managing all those nativeapps is a real nightmare…”
  6. 6. “The biggestmistake we madeas a company wasbetting too muchon HTML5 asopposed to native”Mark Zuckerberg, 11 Sept. 2012
  7. 7. “...the very next daymy boss called andasked me:«Are you sure weare not making thesame mistake withthis HTML5?»”
  8. 8. Mobile device system modelTechnology backgroundHardwareCPU, Memory, I/O devices (storage, network,phone, screen, audio, GPS, accelerometer,…)Operating SystemKernel, Device drivers, Services, ShellApp X App Y BrowserAPI9© 2013 frog - All rights reserved – Confidential and Proprietary
  9. 9. Technology background10© 2013 frog - All rights reserved – Confidential and Proprietary
  10. 10. From web to native:the shades in between
  11. 11. Mobile website
  12. 12. Three approaches tomobile website creation1. Responsive design2. Dedicated m-site3. RESS (Responsive Web Design +Server Side Components)13Mobile website© 2013 frog - All rights reserved – Confidential and Proprietary
  13. 13. 14Responsive designResponsive DesignA unified client-side solution that dynamicallyadapts content and layout to device features
  14. 14. 15Dedicated mobile siteMobile site dedicatoTypical m-site fully optimized for mobile devices interms of layout, content and features
  15. 15. 16RESSRESS (Responsive Server Side)REsponsive web design + Server Side components usesserver-side logic and user detection to assemble and serve aversion of the web page optimized for the client device
  16. 16. Mobile site featuresMobile websiteTechnology Mixes client-side (HTML, CSS, JavaScript) and server-side (PHP,Ruby, .Net, Java etc.) technologiesDependency Platform-independent (runs in any modern browser)Connectivity Online onlyDevice features No access (or limited access if HTML5 browser API is available)Distribution Web17© 2013 frog - All rights reserved – Confidential and Proprietary
  17. 17. Web app
  18. 18. Web app featuresWeb appTechnology Open standard web technologies (HTML5, CSS3, JavaScript) withapplication logic moved to client sideDependency Platform-independent (runs in any modern browser)Connectivity Mostly online (partial offline support)Device features Limited access (through HTML5 browser API)Distribution Web21© 2013 frog - All rights reserved – Confidential and Proprietary
  19. 19. Hybrid apps
  20. 20. Hybrid app23© 2013 frog - All rights reserved – Confidential and Proprietary
  21. 21. Hybrid app24© 2013 frog - All rights reserved – Confidential and Proprietary
  22. 22. Hybrid app
  23. 23. Hybrid app
  24. 24. 27Hybrid apphttp://vimeo.com/55486684© 2013 frog - All rights reserved – Confidential and Proprietary
  25. 25. Hybrid app featuresHybrid appTechnology Open standard web technologies (HTML5, CSS3, JavaScript)+ abstract OS integration APIDependency Cross-platform (can be ported to most target platforms)Connectivity Online and offlineDevice features Almost complete access (through integration layer)Distribution App store28© 2013 frog - All rights reserved – Confidential and Proprietary
  26. 26. Cross-compiling SDK
  27. 27. Appcelerator TitaniumCross-compiling SDK30© 2013 frog - All rights reserved – Confidential and Proprietary
  28. 28. Cross-compiling SDK31© 2013 frog - All rights reserved – Confidential and Proprietary
  29. 29. MoSyncCross-compiling SDK32© 2013 frog - All rights reserved – Confidential and Proprietary
  30. 30. Cross-compiling SDK featuresCross-compiling SDKTechnology Custom API and language depending on selected SDK(e.g. Appcelerator Titanium: JavaScript, MoSync: C/C++)Dependency Cross-platform (can be ported to most target platforms)Connectivity Online and offlineDevice features Almost complete access (through integration layer)Fully native UI elementsDistribution App store33© 2013 frog - All rights reserved – Confidential and Proprietary
  31. 31. Native app
  32. 32. Native app35…???© 2013 frog - All rights reserved – Confidential and Proprietary
  33. 33. Native app featuresNative appTechnology Specific for each platform (e.g. Android: Java, iOS: Objective-C)Dependency Fully platform-dependentConnectivity Online and offlineDevice features Complete access (through individual OS API)Fully native UI elementsDistribution App store38© 2013 frog - All rights reserved – Confidential and Proprietary
  34. 34. Decision criteria
  35. 35. FunctionalityDecision criteria1Business model2Context340© 2013 frog - All rights reserved – Confidential and Proprietary
  36. 36. Decision criteria41© 2013 frog - All rights reserved – Confidential and Proprietary
  37. 37. There’s no “multi-platformsolution to rule them all” really
  38. 38. © 2013 frog - All rights reserved – Confidential and Proprietary

×