Native, Web or Hybrid?
This presentation provides a very brief introduction on the benefits and drawbacks of developing mobile apps using native, web or hybrid approaches. More useful information can be found here: http://www.tcs.com/resources/white_papers/Pages/mobile_client_architecture.aspx
Published on: Mar 3, 2016
Transcripts - Native, Web or Hybrid?
iOSisbeautifulbut there are other options
2%1%29%68%iOS AndroidWindows OtherFeb 2013Source: http://www.egov.vic.gov.au/focus-on-countries/australia/website-practice-australia/mobile-web-australia/mobile-statistics-for-australia-february-2012-february-2013.html
marketsharetotal cost of ownershiptechnical advantages / limitsuser experience
advantages of nativeaccess to all hardware and sensorsfull, responsive, performant UXsuitableforgames /mediaintensiveapps marketed on app store
:(steeplearningcurvehigher costspecialisationfor eachplatformupdate process / people not updatingapp store process / censorship
advantagesinstant deploymentmulti-platformsupportinstant “updates”back/forward compatibilityquicker time to market / lower costHTML is searchable / indexable
hybridaccess to all sensorsapps marketed on the app storeeasier to support multiple platformsgenerally quicker time to market
performancenative apps outperform mobileapps by a large margin, especiallyif there are a large number of richUI elements
native look and feelSomeframeworks, suchastheSenchaTouchframework,attemptto mimic the native look and feelacross all devices under a singlecode base
searchanddistributionNative and hybrid apps can bemarketedandsearchedforonthe app store. Web apps requirethe knowledge of an explicit URL
offline capabilityHTML5 offers rudimentaryoffline capability / data storage,not fully supported acrossall devices