Native vs web apps
0 likes534 views
Mobile HTML5 Applications can save development time by allowing creation of apps for multiple platforms like Android, iOS, and Windows Mobile using a single codebase. However, HTML5 apps still cannot perfectly match the look and functionality of native apps, and have issues with performance, integration with other apps and devices, and varying support across browsers and devices. Hybrid apps that combine HTML5 and native platform features try to address these limitations but often lack the quality of fully native apps. While HTML5 will continue to improve, it still may not be a full replacement for native mobile app development in all cases.
Native vs web apps
- 2. Why? • Android, BlackBerry, iPhone, Windows Mobile, ... • Hopefully: • Save time / no duplicate development • Only one source code for all plattforms • Web developers are a commodity • The Web has improved a lot Copyright (c) 2011 match2blue, Inc. 2
- 3. Estimation • How much time can we save? • 3 platforms, |native dev| == |web dev|, no platform specific work • at most factor 3 • That‘s pretty good • But not too good • Very good vs. mediocre developer are at least factor 10 • (tenfinity factor, etc...) Copyright (c) 2011 match2blue, Inc. 3
- 4. JavaScript resurrection • Introduced with Netscape Navigator 2.0 in September 1995 • Java Applets, Java FX and other replacements • all failed miserably • Nevertheless interest declined • Ajax & JIT Compiler • Huge performance improvements Copyright (c) 2011 match2blue, Inc. 4
- 5. HTML5 • <video>, <audio>, and <canvas> • SVG Images • offline storage • Geolocation access • Initial release: 26 January 2000 • still a working draft Copyright (c) 2011 match2blue, Inc. 5
- 6. All shiny and good? • Successful native apps • Facebook, Twitter, Maps, Earth, Angry Birds, ... • Successful HTML5 apps •? • Copyright (c) 2011 match2blue, Inc. 6
- 7. What is wrong? • Native look & feel (impossible per definition) • Still missing functionality • record video, alarm clock, file access, push notification, ... • Integration with existing apps • launch maps, mail, camera, youtube, gallery, ... • Speed Copyright (c) 2011 match2blue, Inc. 7
- 8. What is wrong? Part 2 • Different web engines & plugins • available <video> codecs • Dev tool support • debugging? • Handling different screen sizes and densities • either simple layout or different code-paths Copyright (c) 2011 match2blue, Inc. 8
- 9. Screen estate, resources Copyright (c) 2011 match2blue, Inc. 9
- 10. Hybrid Apps • Native App with parts of HTML • we do that already (Kurt Beck, MemberScout) • service agreement, group descriptions, help, <video> • PhoneGap & Rhomobile • access to features like camera, gps, etc • for web-only devs • quality vs. quantity Copyright (c) 2011 match2blue, Inc. 10
- 11. Example: 70‘s Rock Trivia Copyright (c) 2011 match2blue, Inc. 11
- 12. Example: 70‘s Rock Trivia Copyright (c) 2011 match2blue, Inc. 12
- 13. Example: Medical App Copyright (c) 2011 match2blue, Inc. 13
- 14. PhoneGap Examples • Majority of apps is single-platform • only 1/10 is multi-platform • Don‘t need to learn sth. new • Often lack of quality Copyright (c) 2011 match2blue, Inc. 14
- 15. Conclusion • HTML5 will get more and more important • You can always improve a web app with a native one • In some cases, web might be „good enough“ or even better • custom UI design, show/edit data • parts of the app: documents, high-score, video-list • Not yet ready for prime-time as a replacement Copyright (c) 2011 match2blue, Inc. 15