O slideshow foi denunciado.
Seu SlideShare está sendo baixado. ×

Shaping a Technology Strategy for Mobile Development

Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Anúncio
Próximos SlideShares
HTML5 App Dev on BlackBerry 10
HTML5 App Dev on BlackBerry 10
Carregando em…3
×

Confira estes a seguir

1 de 43 Anúncio

Mais Conteúdo rRelacionado

Quem viu também gostou (20)

Semelhante a Shaping a Technology Strategy for Mobile Development (20)

Anúncio

Mais de frog (15)

Mais recentes (20)

Anúncio

Shaping a Technology Strategy for Mobile Development

  1. 1. Shaping a Technology Strategy for Mobile Development ALEX CONCONI © 2013 frog - All rights reserved
  2. 2. Alex Conconi Associate Technology Director alex.conconi@frogdesign.com @aconconi
  3. 3. Background
  4. 4. “The web is dead. Apps are the present and the future.” Keith Teare, MBLT 2013
  5. 5. “We provide our customers with native applications on several platforms to access our online services. Managing all those native apps is a real nightmare…”
  6. 6. “The biggest mistake we made as a company was betting too much on HTML5 as opposed to native” Mark Zuckerberg, 11 Sept. 2012
  7. 7. “...the very next day my boss called and asked me: «Are you sure we are not making the same mistake with this HTML5?»”
  8. 8. Mobile device system model Technology background Hardware CPU, Memory, I/O devices (storage, network, phone, screen, audio, GPS, accelerometer,…) Operating System Kernel, Device drivers, Services, Shell App X App Y Browser API 9© 2013 frog - All rights reserved – Confidential and Proprietary
  9. 9. Technology background 10© 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 to mobile website creation 1. Responsive design 2. Dedicated m-site 3. RESS (Responsive Web Design + Server Side Components) 13 Mobile website © 2013 frog - All rights reserved – Confidential and Proprietary
  13. 13. 14 Responsive design Responsive Design A unified client-side solution that dynamically adapts content and layout to device features
  14. 14. 15 Dedicated mobile site Mobile site dedicato Typical m-site fully optimized for mobile devices in terms of layout, content and features
  15. 15. 16 RESS RESS (Responsive Server Side) REsponsive web design + Server Side components uses server-side logic and user detection to assemble and serve a version of the web page optimized for the client device
  16. 16. Mobile site features Mobile website Technology Mixes client-side (HTML, CSS, JavaScript) and server-side (PHP, Ruby, .Net, Java etc.) technologies Dependency Platform-independent (runs in any modern browser) Connectivity Online only Device features No access (or limited access if HTML5 browser API is available) Distribution Web 17© 2013 frog - All rights reserved – Confidential and Proprietary
  17. 17. Web app
  18. 18. Web app features Web app Technology Open standard web technologies (HTML5, CSS3, JavaScript) with application logic moved to client side Dependency Platform-independent (runs in any modern browser) Connectivity Mostly online (partial offline support) Device features Limited access (through HTML5 browser API) Distribution Web 21© 2013 frog - All rights reserved – Confidential and Proprietary
  19. 19. Hybrid apps
  20. 20. Hybrid app 23© 2013 frog - All rights reserved – Confidential and Proprietary
  21. 21. Hybrid app 24© 2013 frog - All rights reserved – Confidential and Proprietary
  22. 22. Hybrid app
  23. 23. Hybrid app
  24. 24. 27 Hybrid app http://vimeo.com/55486684 © 2013 frog - All rights reserved – Confidential and Proprietary
  25. 25. Hybrid app features Hybrid app Technology Open standard web technologies (HTML5, CSS3, JavaScript) + abstract OS integration API Dependency Cross-platform (can be ported to most target platforms) Connectivity Online and offline Device features Almost complete access (through integration layer) Distribution App store 28© 2013 frog - All rights reserved – Confidential and Proprietary
  26. 26. Cross-compiling SDK
  27. 27. Appcelerator Titanium Cross-compiling SDK 30© 2013 frog - All rights reserved – Confidential and Proprietary
  28. 28. Cross-compiling SDK 31© 2013 frog - All rights reserved – Confidential and Proprietary
  29. 29. MoSync Cross-compiling SDK 32© 2013 frog - All rights reserved – Confidential and Proprietary
  30. 30. Cross-compiling SDK features Cross-compiling SDK Technology 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 offline Device features Almost complete access (through integration layer) Fully native UI elements Distribution App store 33© 2013 frog - All rights reserved – Confidential and Proprietary
  31. 31. Native app
  32. 32. Native app 35 …??? © 2013 frog - All rights reserved – Confidential and Proprietary
  33. 33. Native app features Native app Technology Specific for each platform (e.g. Android: Java, iOS: Objective-C) Dependency Fully platform-dependent Connectivity Online and offline Device features Complete access (through individual OS API) Fully native UI elements Distribution App store 38© 2013 frog - All rights reserved – Confidential and Proprietary
  34. 34. Decision criteria
  35. 35. Functionality Decision criteria 1 Business model2 Context3 40© 2013 frog - All rights reserved – Confidential and Proprietary
  36. 36. Decision criteria 41© 2013 frog - All rights reserved – Confidential and Proprietary
  37. 37. There’s no “multi-platform solution to rule them all” really
  38. 38. © 2013 frog - All rights reserved – Confidential and Proprietary

×