Native Vs HTML5 Apps

  • View
    391

  • Download
    1

Embed Size (px)

Text of Native Vs HTML5 Apps

  • 1. Native vs HTML5Dag Olav NoremFINN.no

2. Were HIRING! Android developer Head of Interaction Design Manage a team of 5 very talented designers Will be out in a couple of weeks, but contact me anytime if you are interested 3. NativevsHTML5? 4. That is thequestion! 5. Or is it? 6. NativevsHTML5? 7. Digression/rant #1 The HTML5 moniker is a distraction Its HTML (+ CSS, JavaScript etc). Its the Web. Its been around for a long time, 5 is just the number thatcomes after 4. One day there will be a 6. Yes, HTML version 5 has important improvements that areparticlularly relevant in the app context, but the topic is reallythe web development platform vs native developmentplatforms. 8. So, what is THEquestion? 9. WebvsApps? 10. WebvsApps? 11. Web?---------------- Apps? 12. Should Ido Web? 13. Should Ido MobileWeb? 14. Should Ido MobileWeb? 15. HOWshould I doMobileWeb? 16. HOW should I do Mobile Web? Alternatives: One codebase to span across all devices Split between two code bases (typically an m. and a www.) Three or more codebases (tablet. , tv. or other) Answer It depends 17. Digression/rant #2: Responsive design It is not a question of mobile site vs responsive Everything has to be responsive. Both m. and www. The question is how broadly each should span If you simply assume that one is always simpler than two, youare not adressing the core issue The complexity is happening outside of your control. What isunder your control is your choice of how to address thatcomplexity. If you do choose one codebase, forget about using an oldwww. as a starting point. Mobile up is the only way to go. 18. Decision factors Device diversity Usage context (desk, couch, tram, store, toilet) Size (phone, tablet, desktop, tv) Input methods (touch, mouse, trackpad, remote) Network (fast/slow, high/low latency, cheap/expensive) Level and type of user interaction required Cost of duplicating code per codebase Ambition Resources 19. Should Ido Apps? 20. IT DEPENDS What apps can do that browsers cant or apps can do better: Performance Device integration (notifications, camera, sensors etc) Background processing Distribution channel Payment methods 21. Decision factors If it makes a difference! For your core business "If the app makes you sell more... bananas, airplanes, ads...then you should make an app - Luke W. If your competitors can use apps as a foot in the door to takeover your market Cost and ROI Apps is not a one-off effort. Once you make one, you have to maintain it and continue to improve it (if not, why did you make it in the first place?) 22. HOWshould I doApps? 23. Finally,back to the firstquestion 24. Or, almost 25. NativeOrHybrid? 26. How should I do Apps? If you do apps only: Native! You are an app company. You compete with other appcompanies. You have to squeeze out every little bit ofadvantage the native platform can give you. If both web and apps: It depends 27. Decision factors Use native where it makes a difference If performance is important, native is the way to go A hybrid app is part native, part web Use webview when the advantages of native are notimportant AND webview is more cost efficient But be aware that hybrid approach is not necessarilysimpler or cheaper. There are pros and cons. If you make a simple wrapper app around a webview, the onlyadvantage you get from apps is distribution Cross plattform frameworks are ok. But by definition acompromise. 28. Summary If youre an app company, youre an app company 99% of you will go 100% native If youre an Internet company Web is essential Web = Mobile Web -> essential How to do mobile web: depends Apps: depends How to do apps: depends Will it move the needle for your core business? Enough to compensate for the cost? 29. Questions ?BTW, were HIRING! Android developer Head of Interaction Design Manage a team of 5 very talented designers Will be out in a couple of weeks, but contact me anytime if you areinterested