Native VS HTML5


Published on

Native Apps vs Web Apps - presented in the Smart Mobile City event of EESTEC LC Trieste in July 2013

Published in: Technology
  • Be the first to comment

No Downloads
Total Views
On Slideshare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Native VS HTML5

  1. 1. VS
  2. 2. /m.sencerkaradayi /msencer
  3. 3. • The great app debate • May the best app wins, the fight begins • User Exprience • Performance • Monetization • Security • Cross-Platform costs • Updates and Distribution • And the winner is… • Quiz time • Q&A
  4. 4. NATIVE or HTML5?
  5. 5. ‘’ A native mobile app is a smartphone application that is coded in a specific programming language, such as Objective C for iOS and Java for Android operating systems. Native mobile apps provide fast performance and a high degree of reliability. …. ’’
  6. 6.
  7. 7. A web- based program designed to run on any mobile device via a browser.
  8. 8.
  9. 9. *according to Appcelerator/ IDC’s Q2 2012 survey %6Of the apps target as a Web App* 500kAndroid Apps in Google Play
  11. 11. USER EXPERIENCE Only native apps can deliver the best user expriences leveraging the full capabilities of the device and OS to offer innovative ways of doing things.
  12. 12. ‘’The biggest mistake we made as a company was betting too much on HTML5 as opposed to native. It just wasn’t ready.‘’ — Mark Zuckerberg, Sep. 2012
  13. 13.
  14. 14. ‘’Our view is that HTML5 technologies can deliver as-good- as-native experiences – and that will continue to be the focus for our core application, where we’ll continue to improve our performance on all devices. And we were all extremely impressed by Sencha’s Fastbook which is a testament to the ability to deliver great experiences using web technology. But the lesson from Fastbook is that it’s hard work – you don’t get those experiences out-of-the- box. And the lesson we’ve learnt over the last 12 months has been that the cost in time, effort and testing to bring an HTML5 application to a native level of performance seems to be far greater than if the application was built with native technologies from the get-go.’’
  15. 15. PERFORMANCE HTML5 still faces challenges in accessing device-native features across all mobile browsers, and in rendering graphically-rich user interfaces and data presentations.
  16. 16. MONETIZATION Google Play Store has 500k native apps, 15 billion downloads. On the other hand, Web apps have no Play Store-ish Marketplace except
  17. 17. SECURITY A native app’s source and cache is encrypted. On the other hand, a web app’s source is much easier to access and corrupt.
  18. 18. CROSS-PLATFORM DEPLOYMENT COSTS Native apps require a new development and testing process for each platform. HTML5 was built to be the common language of the Web regardless of the device or the OS.
  19. 19. UPDATES AND DISTRIBUTION CONTROL Web is an open platform which is not under a monopoly of any companies like Google, Apple or Microsoft. However, HTML5 is a bit slow in supporting new phone features as device makers innovate.
  20. 20. Neither of them!
  21. 21. I want to make money from selling an app at the Marketplace. HTML5 or Native?
  22. 22. For many years I’ ve been working on Web Technologies like HTML + CSS + JS. HTML5 or Native?
  23. 23. I want to publish my application to as many mobile markets as possible. HTML5 or Native?
  24. 24. Security and UX is highly essential! HTML5 or Native?
  25. 25. Q&A /m.sencerkaradayi /msencer
  26. 26. • html5-in-favor-of-native-ios-and-android-apps/ • html5.pdf • was-betting-too-much-on-html5/ • html5-in-favor-of-native-ios-and-android-apps/ • •