Mobile Web

versus

NATIVE



tale of the tape

Drew Engelson
Chief Architect
McLean, VA
Jay Kissman
Mobile Lead
Wexford, PA
vs


CELERITY's mission


To accelerate business 

results in the digital economy. 







Mobile Web

  • Runs in mobile web browser 
  • Built with HTML5 + JS + CSS
  • Served by web server
  • No approvals or app store
  • Can look a lot like native
  • May be responsive 
    or target specific screen sizes
 

Native APP

  • Runs as locally installed app 
  • Built with Objective C *
    • and/or Java
    • and/or C#
  • Runs on device
    • Fed by APIs
  • Approval and App stores
  • Built for specific devices/screens

Hybrid APP

  • Runs as locally installed app 
  • Built with HTML5 + JS + CSS
  • Runs on device
    • In embedded web browser
    • Fed by APIs
  • Approval and App stores
  • Built for specific devices
    • May be responsive
    • Cross platform compilers

THUNderdome

Device features

Native

Offline Access

Native

discoverability

Mobile Web

Performance

Native

Installation

Tie

maintenance

Mobile Web

Platform independence

Mobile Web

Red Tape

Mobile Web

development cost

Mobile Web

User interface

Native

Go To the cards




   dengelson@celerity.com
   jkissman@celerity.com

photo: lwpkommunikacio 

Mobile Web vs. Native (ModevCon 2014)

By Drew Engelson

Mobile Web vs. Native (ModevCon 2014)

Not really a battle between mobile web vs. native. But really just highlights of which aspects make one a better choice for a particular situation.

  • 955