Your SlideShare is downloading. ×

Native Vs HTML5 Apps

371
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
371
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Well, it is AquestionBut not THE question
  • Zuckerberg.Whatdid he say? Bettingon HTML5 wasthebiggestmistakethey have madeIn whatcontextdid he say it? In thecontextof native apps. In thecontextofFacebook.
  • Zuckerberg.Whatdid he say? Bettingon HTML5 wasthebiggestmistakethey have madeIn whatcontextdid he say it? In thecontextof native apps. In thecontextofFacebook.
  • No, not thateither. «vs» implies a dichotomy, whichthis is not.So let’s break it up
  • No, not thateither. «vs» implies a dichotomy, whichthis is not.So let’s break it up
  • No, not thateither. «vs» implies a dichotomy, whichthis is not.So let’s break it up
  • Yes/No?For almosteveryone, theanswer is yes. Onlyifyouare an appcompany (thinkWordfeud) or making an app for a veryspecifictaskwouldyou not do Web.Granted, thatmayinclude a good part ofthisaudience. Butifyouare in thisgroup, theanswer to thequestionthis talk is about is prettymucha given. Willget back to that.
  • Yes. Duh.We’rebeyondthepointwerethisquestionevenneeds to be askedThe Web is the Web. You do Web, you do mobile.
  • Yes. Duh.We’rebeyondthepointwerethisquestionevenneeds to be askedThe Web is the Web. You do Web, you do mobile.
  • Now, this is an interestingquestionAnd nowtheanswer is not so clearcutanymoreOptions:Two or more code basesOne codebase to span across all devicesAnswer: it dependsFactors:Varians i enhetene vi ønsker å addresereBrukskontekst (skrivebordet, sofaen, trikken, i butikken, i transaksjonsøyeblikket)Størrelse (håndholdt, tablet, desktop, tv)Interaksjon (mus, tastatur, touch, stemme)Nettverk (rask/treg, høy/lav latency, billig/dyrt)Interaksjonsintensitet i tjenesten som leveresKostnad ved duplisering av kode per klientAmbisjonsnivåRessurser
  • Now, this is an interestingquestionAnd nowtheanswer is not so clearcutanymoreOptions:Two or more code basesOne codebase to span across all devicesAnswer: it dependsFactors:Varians i enhetene vi ønsker å addresereBrukskontekst (skrivebordet, sofaen, trikken, i butikken, i transaksjonsøyeblikket)Størrelse (håndholdt, tablet, desktop, tv)Interaksjon (mus, tastatur, touch, stemme)Nettverk (rask/treg, høy/lav latency, billig/dyrt)Interaksjonsintensitet i tjenesten som leveresKostnad ved duplisering av kode per klientAmbisjonsnivåRessurser
  • Now, this is an interestingquestionAnd nowtheanswer is not so clearcutanymoreOptions:Two or more code basesOne codebase to span across all devicesAnswer: it dependsFactors:Varians i enhetene vi ønsker å addresereBrukskontekst (skrivebordet, sofaen, trikken, i butikken, i transaksjonsøyeblikket)Størrelse (håndholdt, tablet, desktop, tv)Interaksjon (mus, tastatur, touch, stemme)Nettverk (rask/treg, høy/lav latency, billig/dyrt)Interaksjonsintensitet i tjenesten som leveresKostnad ved duplisering av kode per klientAmbisjonsnivåRessurser
  • Now, this is an interestingquestionAnd nowtheanswer is not so clearcutanymoreOptions:Two or more code basesOne codebase to span across all devicesAnswer: it dependsFactors:Varians i enhetene vi ønsker å addresereBrukskontekst (skrivebordet, sofaen, trikken, i butikken, i transaksjonsøyeblikket)Størrelse (håndholdt, tablet, desktop, tv)Interaksjon (mus, tastatur, touch, stemme)Nettverk (rask/treg, høy/lav latency, billig/dyrt)Interaksjonsintensitet i tjenesten som leveresKostnad ved duplisering av kode per klientAmbisjonsnivåRessurser
  • Now, this is an interestingquestionAnd nowtheanswer is not so clearcutanymoreOptions:Two or more code basesOne codebase to span across all devicesAnswer: it dependsFactors:Varians i enhetene vi ønsker å addresereBrukskontekst (skrivebordet, sofaen, trikken, i butikken, i transaksjonsøyeblikket)Størrelse (håndholdt, tablet, desktop, tv)Interaksjon (mus, tastatur, touch, stemme)Nettverk (rask/treg, høy/lav latency, billig/dyrt)Interaksjonsintensitet i tjenesten som leveresKostnad ved duplisering av kode per klientAmbisjonsnivåRessurser
  • Now, this is an interestingquestionAnd nowtheanswer is not so clearcutanymoreOptions:Two or more code basesOne codebase to span across all devicesAnswer: it dependsFactors:Varians i enhetene vi ønsker å addresereBrukskontekst (skrivebordet, sofaen, trikken, i butikken, i transaksjonsøyeblikket)Størrelse (håndholdt, tablet, desktop, tv)Interaksjon (mus, tastatur, touch, stemme)Nettverk (rask/treg, høy/lav latency, billig/dyrt)Interaksjonsintensitet i tjenesten som leveresKostnad ved duplisering av kode per klientAmbisjonsnivåRessurser
  • Transcript

    • 1. Native vs HTML5Dag Olav NoremFINN.no
    • 2. We’re 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. Native vsHTML5?
    • 4. That is thequestion!
    • 5. Or is it?
    • 6. Native vsHTML5?
    • 7. Digression/rant #1• The HTML5 moniker is a distraction• It’s HTML (+ CSS, JavaScript etc). It’s the Web.• It’s been around for a long time, 5 is just the number that comes after 4. One day there will be a 6.• Yes, HTML version 5 has important improvements that are particlularly relevant in the app context, but the topic is really the web development platform vs native development platforms.
    • 8. So, what is THEquestion?
    • 9. Web vsApps?
    • 10. Web vsApps?
    • 11. Web?---------------- Apps?
    • 12. Should Ido Web?
    • 13. Should Ido Mobile Web?
    • 14. Should Ido Mobile Web?
    • 15. HOWshould I do Mobile Web?
    • 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, you are not adressing the core issue• The complexity is happening outside of your control. What is under your control is your choice of how to address that complexity.• If you do choose one codebase, forget about using an old www. 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 can’t 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 take over 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 do Apps?
    • 23. Finally,back to the firstquestion 
    • 24. Or, almost
    • 25. Native OrHybrid?
    • 26. How should I do Apps?• If you do apps only: – Native! – You are an app company. You compete with other app companies. You have to squeeze out every little bit of advantage 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 not important AND webview is more cost efficient – But be aware that hybrid approach is not necessarily simpler or cheaper. There are pros and cons.• If you make a simple wrapper app around a webview, the only advantage you get from apps is distribution• Cross plattform frameworks are ok. But by definition a compromise.
    • 28. Summary• If you’re an app company, you’re an app company – 99% of you will go 100% native• If you’re 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, we’re 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