<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:wfw="http://wellformedweb.org/CommentAPI/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom"
    xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    >

<channel>
    <title>Webmonkey &#187; The Web Is Dead</title>
    <atom:link href="http://www.webmonkey.com/tag/the-web-is-dead/feed/" rel="self" type="application/rss+xml" />
    <link>http://www.webmonkey.com</link>
    <description>The Web Developer&#039;s Resource</description>
    <lastBuildDate>Mon, 06 May 2013 17:29:19 +0000</lastBuildDate>
    <language>en-US</language>
    <sy:updatePeriod>hourly</sy:updatePeriod>
    <sy:updateFrequency>1</sy:updateFrequency>
    <generator>http://wordpress.org/?v=3.4.2</generator>
    
    <item>
        <title>How Do Native Apps and Web Apps Compare?</title>
        <link>http://www.webmonkey.com/2010/08/how-do-native-apps-and-web-apps-compare/</link>
        <comments>http://www.webmonkey.com/2010/08/how-do-native-apps-and-web-apps-compare/#comments</comments>
        <pubDate>Tue, 17 Aug 2010 13:00:46 +0000</pubDate>

                <dc:creator>Michael Calore</dc:creator>

        <guid isPermaLink="false">http://www.webmonkey.com/?p=48283</guid>
        		<category><![CDATA[HTML5]]></category>
		<category><![CDATA[Mobile]]></category>
		<category><![CDATA[Web Apps]]></category>
		<category><![CDATA[android]]></category>
		<category><![CDATA[iPad]]></category>
		<category><![CDATA[The Web Is Dead]]></category>
		<category><![CDATA[Wired Magazine]]></category>
        <description><![CDATA[The Web is Dead. Long Live the Internet The Web is Dead?! A Debate How the Web Wins How Do Native Apps and Web Apps Compare? Two roads diverge on a tablet screen. One is the path to the native app, the other leads to the open web. Luckily, you can take both. The latest [...]]]></description>

            <content:encoded><![CDATA[<p><!-- wpautop enabled --><br />
<style type="text/css">
.skull_nav  { background:#FFF; width:200px; float:right; padding:0 0 5px; margin:0 0px 20px 30px; border-bottom:solid #FFF 5px; font-size:0.9em;}
.link-container { padding-bottom:10px; width:200px; }
</style>
<p><!-- START INSET --></p>
<div class="skull_nav">
 <a href="http://www.wired.com/magazine/2010/08/ff_webrip/"><img alt="Skull" src="http://www.webmonkey.com/wp-content/uploads/2010/08/web_rip_200_monkey.gif" height="50px" /></a></p>
<div class="link-container"><a href="http://www.wired.com/magazine/2010/08/ff_webrip/">The Web is Dead. Long Live the Internet</a></div>
<div class="link-container"><a href="http://www.wired.com/magazine/2010/08/ff_webrip_debate/">The Web is Dead?! A Debate</a></div>
<div class="link-container"><a href="http://www.wired.com/epicenter/2010/08/how-the-web-wins/">How the Web Wins</a></div>
<div class="link-container"><a href="http://www.webmonkey.com/2010/08/how-do-native-apps-and-web-apps-compare/">How Do Native Apps and Web Apps Compare?</a></div>
</div>
<p><!-- END INSET --></p>
<p>Two roads diverge on a tablet screen. One is the path to the native app, the other leads to the open web.</p>
<p>Luckily, you can take both. The latest mobile devices ship with a thoroughly modern browser capable of handling emerging web standards. Beneath that is a modern operating system with access to the magic inside the hardware: the camera, GPS, gyroscope and compass. But if you had to pick one &#8212; native app or web app &#8212; which would you choose? Your decision will make all the difference in how you approach your design, development and distribution.</p>
<style type="text/css">
<!--
@import url("http://www.webmonkey.com/wp-content/uploads/2010/08/styleTable4.css");
-->
</style>
<table id="ver-zebra" summary="How Do Web Apps and Native Apps Compare?">
<colgroup>
<col />
<col class="vzebra-odd" />
<col class="vzebra-even" />
 	</colgroup>
<thead>
<tr>
<th scope="col" id="feature">The Issues</th>
<th scope="col" id="vzebra-native">Native Apps</th>
<th scope="col" id="vzebra-web">Web Apps</th>
</tr>
</thead>
<tbody>
<tr>
<td>Internet access</td>
<td>Not required</td>
<td>Required, except for rare apps with offline capability</td>
</tr>
<tr>
<td>Installation/updates</td>
<td>Must be deployed or downloaded</td>
<td>Hit refresh</td>
</tr>
<tr>
<td>User interface</td>
<td>Native apps are responsive and functional</td>
<td>Browsers can be clunky, but new advancements in JavaScript like <a href="http://jquerymobile.com/">jQuery Mobile</a> are catching up fast</td>
</tr>
<tr>
<td>Device compatibility</td>
<td>Platform-dependent, hardware-dependent</td>
<td>Platform-agnostic, content can be reformatted with CSS to suit any device</td>
</tr>
<tr>
<td>Animation/Graphics</td>
<td>Fast and responsive</td>
<td>Web apps are getting closer, but will probably always lag</td>
</tr>
<tr>
<td>Streaming media</td>
<td>Few problems with audio and video. Flash works, but only if the device supports it</td>
<td>Flash works where supported. Browser-based audio and video are <a href="http://www.webmonkey.com/2010/07/youtube-launches-new-html5-mobile-site/">getting there</a>, but still beset by compatibility headaches. Give it a year or two</td>
</tr>
<tr>
<td>Fonts</td>
<td>Tight control over typefaces, layout</td>
<td>Almost on par, thanks to advancements in web standards. Give it six months</td>
</tr>
<tr>
<td>Is my content searchable?</td>
<td>Not on the web</td>
<td>By default</td>
</tr>
<tr>
<td>Sharable/Tweetable?</td>
<td>Only if you build it in</td>
<td>Web links are shared freely. Social APIs and widgets allow easy one-click posting</td>
</tr>
<tr>
<td>Discussion and collaboration</td>
<td>Only if you build it, and it&#8217;s more difficult if data is disparate</td>
<td>Discussion is easy, all data is stored on a server</td>
</tr>
<tr>
<td>Access to hardware sensors</td>
<td>Yes, all of them: camera, gyroscope, microphone, compass, accelerometer, GPS</td>
<td>Access through the browser is limited, though geolocation is common</td>
</tr>
<tr>
<td>Development</td>
<td>Specific tools required for some platforms (like Apple&#8217;s). You have to build a new app for each target platform</td>
<td>Write once, publish once, view it anywhere. Multiple tools and libraries to choose from</td>
</tr>
<tr>
<td>Can I sell it?</td>
<td>Charge whatever you want. Most app distributors take a slice, up to 30%</td>
<td>Advertising is tolerated, subscriptions and paywalls less so. No distribution costs beyond server fees</td>
</tr>
<tr>
<td>Distribution</td>
<td>Most app stores require approval. And you gotta wait</td>
<td>No such hassle</td>
</tr>
<tr>
<td>Outside access to your content</td>
<td>No, the reader must download your app</td>
<td>Yep, just click a link</td>
</tr>
<tr>
<td>Advertising</td>
<td>Control over design (though limited in <a href="http://www.wired.com/epicenter/2010/08/apples-control-issues-hamper-iad-rollout/">iAds</a>) and rate</td>
<td>More choices for design, plus access to web analytics. Rates vary widely</td>
</tr>
</tbody>
</table>
<p><b>See Also:</b></p>
<ul>
<li><a href="http://www.webmonkey.com/2010/07/youtube-launches-new-html5-mobile-site/">YouTube Launches New HTML5 Mobile Site</a></li>
<li><a href="http://www.webmonkey.com/2010/08/deviantarts-muro-drawing-app-is-pure-html5-awesomeness/">DeviantArt&#8217;s Muro Drawing App Is Pure HTML5 Awesomeness</a></li>
<li><a href="http://www.webmonkey.com/2010/07/test-your-site-at-any-size-with-resizemybrowser/">Test Your Site at Any Size With ResizeMyBrowser</a></li>
</ul>
<div id='linker_widget' class='contextly-widget'></div>]]></content:encoded>
            <wfw:commentRss>http://www.webmonkey.com/2010/08/how-do-native-apps-and-web-apps-compare/feed/</wfw:commentRss>
        <slash:comments>33</slash:comments>

        
    </item>
    </channel>
</rss>
