Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Apps: Web vs Native, two technologies, one problem

Apps: Web vs Native, two technologies, one problem

With the exponential growth of mobile devices companies need to be prepared to release mobile versions of their applications. What are the technologies available, what are their key benefits and caveats?

Mariz Melo

May 24, 2013
Tweet

More Decks by Mariz Melo

Other Decks in Technology

Transcript

  1. The Problem • Mobile marketshare exponential growth • Competition providing

    mobile solutions by eGain 10% 7% 40% 43% IOS Android Blackberry Others source: http://gs.statcounter.com
  2. Round 1: Web Apps by eGain • Fast to get

    started with • Well known technology (HTML) • Highly customizable • Adaptable • Cost PROS
  3. Round 1: Web Apps by eGain • Slower than native

    apps* • Limited hardware access • Low availability** • No central of distribution CONS * advances have been made with asm.js (Mozilla) ** offline techniques can be used, but they are not trivial.
  4. Round 2: Native Apps by eGain PROS • Performance •

    Full hardware access • Security • High availability* * most apps today require users to be online
  5. Round 2: Native Apps by eGain CONS • Slower to

    get started with • Specific technologies • Harder to change • Cost
  6. Round 3: Hybrid Apps by eGain • All the benefits

    of Web Apps • Faster than Web Apps • Access to hardware • Multi-platform • High availability • Acceptable on App Stores PROS
  7. Round 3: Hybrid Apps by eGain • Slower than native

    • Application layer dependency* CONS * PhoneGap
  8. Conclusions • Web or Native will depend of your type

    of app • Hybrid apps are growing in popularity and acceptance by eGain 40% 20% 40% Native Web Hybrid source: Gartner - Consumer App Landscape 2015