HTML5 vs. Native

HTML5 vs. Native

The mobile scene has greatly evolved over the last 10 years; new operating systems and app stores have materialised and flipped on its head the existent postulates on information consumption on the go. We are more connected, less private and data hungrier than ever before - not to mention the higher standards.
HTML5 has now matured as the ubiquitous platform for the web and cannot be dismissed any longer as an incomplete solution for mobile. On the other hand, native apps can offer better performance, greater engagement and lucrative ecosystem.
Which one shall we use? There is only one right answer...

B726bf6980ae838cb19d2f0ee2cec9ef?s=128

Paul Ardeleanu

May 11, 2016
Tweet

Transcript

  1. Mobile wars: 
 HTML5 vs. Native @pardel Paul Ardeleanu

  2. flickr.com/photos/photomato/3581886493/

  3. None
  4. http://liquidsouldesign.deviantart.com/art/Game-of-Thrones-House-Stark-252288741

  5. http://liquidsouldesign.deviantart.com/art/House-Lannister-252291094

  6. http://liquidsouldesign.deviantart.com/art/House-Targaryen-252290069

  7. http://liquidsouldesign.deviantart.com/art/House-Baelish-260319395

  8. https://www.flickr.com/photos/fouquier/14144024197

  9. HTML5?

  10. Native?

  11. flickr.com/photos/tucamon/5618419983

  12. https://www.flickr.com/photos/rickmccharles/4179034985

  13. https://www.flickr.com/photos/lancesh/22496520524

  14. http://flurrymobile.tumblr.com/post/127638842745/seven-years-into-the-mobile-revolution-content-is

  15. https://www.flickr.com/photos/andrewmalone/5163238038

  16. Huge series of tubes http://news.netcraft.com/archives/2016/04/21/april-2016-web-server-survey.html

  17. None
  18. http://www.kpcb.com/blog/2015-internet-trends

  19. How to… • Adaptive content • Truly embrace HTML5

  20. None
  21. None
  22. Javascript required

  23. Javascript required

  24. https://www.flickr.com/photos/nabroci/9785879596

  25. https://www.flickr.com/photos/125951485@N06/16290847332 The mobile mashup

  26. https://twitter.com/lukew/status/591296890030915585

  27. None
  28. Hybrid Apps

  29. Strengths & weaknesses cost performance

  30. Strengths & weaknesses cost performance native

  31. Strengths & weaknesses cost performance native web

  32. Strengths & weaknesses cost performance native web hybrid

  33. Strengths & weaknesses cost performance native web hybrid

  34. Ungraceful degradation

  35. None
  36. Cross-platform

  37. None
  38. None
  39. Best possible outcome

  40. flickr.com/photos/kenyee/358996991/

  41. None
  42. flickr.com/photos/kertong/4509481335/

  43. Surprise & Delight

  44. Surprise & Delight y h b t g v

  45. Learn from big players So while utilizing web technology has

    allowed us to support more than 500 million people using Facebook on more than 7000 supported devices, we realized that when it comes to platforms like iOS, people expect a fast, reliable experience and our iOS app was falling short. Now that our mobile services had breadth, we wanted depth. So, we rewrote Facebook for iOS from the ground up (I really did open up Xcode and click "New Project") with a focus on quality and leveraging the advances that have been made in iOS development. https://www.facebook.com/notes/facebook-engineering/under- the-hood-rebuilding-facebook-for-ios/10151036091753920
  46. None
  47. You have a choice

  48. https://www.flickr.com/photos/purple-lover/13583362554

  49. Q & A

  50. None
  51. Thank you! @pardel paul@lupo.uk