Billy (William) Waller Sean Frankruyter Chris Bell Josh Parsons
Billy (William) Waller Sean Frankruyter Chris Bell Josh Parsons
Anyone whos betting against the web right now is an idiot. -Daniel Appelquist,
Co-Chair W3C Mobile Web Initiative
Device Compatibility
Web Apps Compatible across all devices with a web browser. CSS can reformat content to work with any device Native App Platform dependant Hardware optimized
Development
Web Apps Same code can be run on any device with a browser Collaboration is easy since everything is on the server Can be tested from any device Native App App will only run on the device OS it was built for (Android, iOS, Blackberry OS, Symbian) Specific tools required for developing on each device family
User Interface
Web Apps Browsers can be clunky With a 20kB limit, its hard to design an attractive interface Native App Responsive and functional Can have high-quality graphics since it utilizes the full hardware capabilities of the device
WINNER: Native
WINNER: Tie
HTML5
New form input types such as Number and Email Allow the mobile device to automatically use the correct input type
The `placeholder` attribute Saves space
Questions?
Reference
eMarketer
http://www.emarketer.com/Article.aspx?R=1008010 Wikipedia http://en.wikipedia.org/ WebMonkey -http://www.webmonkey.com/2010/08/howdo-native-apps-and-web-apps-compare/ Fling, Brian. Mobile Design and Development ReadWriteWeb http://www.readwriteweb.com/start/2010/01/html5-isgreat-for-mobile.php MobileOpen http://www.mobilopen.org/2011/01/26/webversus-native-apps/