<?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>DudaMobile Blog &#187; portability</title>
	<atom:link href="http://blog.dudamobile.com/tag/portability/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.dudamobile.com</link>
	<description>Click. Create. Mobile. Turning websites into mobile sites.</description>
	<lastBuildDate>Wed, 25 Jan 2012 19:46:42 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>Mobile Web vs. Mobile Apps</title>
		<link>http://blog.dudamobile.com/mobile-web-vs-mobile-apps/</link>
		<comments>http://blog.dudamobile.com/mobile-web-vs-mobile-apps/#comments</comments>
		<pubDate>Mon, 07 Sep 2009 20:25:11 +0000</pubDate>
		<dc:creator>DudaMobile</dc:creator>
				<category><![CDATA[Mobile Website]]></category>
		<category><![CDATA[app store]]></category>
		<category><![CDATA[appstore]]></category>
		<category><![CDATA[Discoverability]]></category>
		<category><![CDATA[Hyper Links]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[mobile applications]]></category>
		<category><![CDATA[mobile apps]]></category>
		<category><![CDATA[mobile browser]]></category>
		<category><![CDATA[Mobile Device Capabilities]]></category>
		<category><![CDATA[mobile site]]></category>
		<category><![CDATA[Mobile Web]]></category>
		<category><![CDATA[performance]]></category>
		<category><![CDATA[portability]]></category>
		<category><![CDATA[user experience]]></category>

		<guid isPermaLink="false">http://blog.dudamobile.com/?p=67</guid>
		<description><![CDATA[You probably already have an Internet website and are now considering to create a mobile website. One of the main questions you might be debating with is whether to create a mobile application (app) or a mobile website. There has been quite a bit of discussion on the web regarding the pros and cons of]]></description>
			<content:encoded><![CDATA[<p>You probably already have an Internet website and are now considering to create a <a href="http://www.dudamobile.com/">mobile website</a>. One of the main questions you might be debating with is whether to create a mobile application (app) or a mobile website. There has been quite a bit of discussion on the web regarding the pros and cons of each of these options.</p>
<p><a href="http://blog.dudamobile.com/wp-content/uploads/2009/09/app-vs-web.png"><img class="aligncenter size-medium wp-image-111" title="mobile apps vs mobile web" src="http://blog.dudamobile.com/wp-content/uploads/2009/09/app-vs-web-300x120.png" alt="mobile apps vs mobile web" width="300" height="120" /></a></p>
<p>With the huge buzz around Apple’s App Store and Blackberry’s App World it seems that mobile applications are taking over, but <strong>is an app the right solution for everyone?</strong> Doesn’t it seem like we have gone back fifteen years and once again being required to install packaged software? An interesting <a href="http://www.pinchmedia.com/appstore-secrets/">research by Pinch Media</a> shows that less than 5% of downloaded apps continue to be used 20 days after being downloaded.</p>
<p>There are some cases where an app makes more sense as for example: businesses who have a very large and dedicated user base (e.g . Facebook) or solutions that requires special capabilities of the mobile device that are not accessible through the web (e.g. gaming).</p>
<p>But in the <strong>majority of the cases businesses and individuals will gain more from going through the mobile web route</strong>. The development costs will be lower, the potential market size will be bigger and it will be much easier for people to find your site by using any search engine.</p>
<p>Before making a decision several criteria should be considered. Below I summarized some of the main points to help you make the right decision for your business. Feel free to comment or add to my list.</p>
<table border="1" cellspacing="2" cellpadding="5" bordercolor="#D8AD22">
<tbody>
<tr bgcolor="#EB9D49">
<td width="128" valign="middle"><strong> </strong></td>
<td width="243" align="center" valign="middle"><strong>Mobile   App</strong>&nbsp;</p>
<p>Application designed to run on a specific mobile device &#8211;  download and installation required</td>
<td width="267" align="center" valign="middle"><strong>Mobile   Website</strong>&nbsp;</p>
<p>Website created specifically for mobile devices &#8211; accessible through mobile browsers, no download or installation required</td>
</tr>
<tr bgcolor="#E3E3E3">
<td width="128" valign="middle"><strong>Portability</strong></td>
<td width="243" valign="middle">Needs   to be developed for each platform (iPhone, BlackBerry, Android, Palm and the   list goes on…)</td>
<td width="267" valign="middle">Common   platform – some solutions (e.g. <span style="color: #ff6600;"><strong><a href="http://www.dudamobile.com" target="_blank"><span style="color: #ff6600;">D<span style="color: #ff6600;">ud</span></span><span style="color: #ff6600;">a</span></a></strong></span><em><span style="color: #808080;"><strong><a href="http://www.dudamobile.com" target="_blank"><span style="color: #808080;">Mobile</span></a></strong></span></em>) enable you to develop once and run on all web-enabled mobile devices</td>
</tr>
<tr>
<td width="128" valign="middle"><strong>Hyper   Links</strong></td>
<td width="243" valign="middle">It   is possible to link to an app but since most users will not have the app   installed, the most effective way is to link to the download page for this   app. It is possible to link from an app externally to other websites</td>
<td width="267" valign="middle">Possible   to provide links to different pages on your mobile site and to link from your   mobile site to other websites</td>
</tr>
<tr bgcolor="#E3E3E3">
<td width="128" valign="middle"><strong>Discoverability</strong></td>
<td width="243" valign="middle">Most   apps don’t achieve critical success and fade into the world of anonymity. You   will need a very well defined strategy to break into the top list for your   category in order to make it (AdWhirl estimates <a href="http://blog.adwhirl.com/2009/06/30/with-over-50000-apps-in-the-apple-app-store-how-do-apps-get-discovered/">$1875   per day advertising budget can get you there</a> , Pinch Media says the   impact of being in the top 100 is a daily increase of <a href="http://www.pinchmedia.com/appstore-secrets/">2.3x in the number of   users</a>)</td>
<td width="267" valign="middle">People   can find your site by using any of the search engines and via links from other   websites, blogs, Twitter and links embedded in emails. A good marketing strategy   can definitely increase the number of visitors, especially if it is viral.</td>
</tr>
<tr>
<td width="128" valign="middle"><strong>Distribution &amp;  Market Size</strong></td>
<td width="243" valign="middle">At   the mercy of the App Store police in regards to availability of your app and   approvals to get it in. Requires users to download – huge barrier to entry.&nbsp;</p>
<p>Limited   to the number of users on the released platform</td>
<td width="267" valign="middle">Anyone   on the web has access to your mobile site</td>
</tr>
<tr bgcolor="#E3E3E3">
<td width="128" valign="middle"><strong>Usage   of Device Capabilities</strong></td>
<td width="243" valign="middle">Able   to use all device capabilities (GPS, camera, voice, RFID, address book, calendar, etc.)</td>
<td width="267" valign="middle">It is possible to use features like <a href="http://www.techcrunch.com/2009/07/15/google-brings-location-to-the-mobile-web-on-the-iphone/">GPS</a>, <a href="http://www.wired.com/epicenter/2009/02/google-turns-to/">offline data storage</a> and   video from within mobile websites using the latest mobile browsers which support HTML5. Access from the web to some native capabilities of mobile devices is still limited due to security and privacy concerns (e.g. access to address book or calendar)</td>
</tr>
<tr>
<td width="128" valign="middle"><strong>Supportability   &amp; Upgradeability</strong></td>
<td width="243" valign="middle">Difficult   to support and maintain after app is downloaded. Every new release with bug   fixes requires to go through the entire approval process of the <a href="http://www.techcrunch.com/2009/08/31/another-popular-developer-lays-the-smack-down-on-apples-app-store/">app store</a>.&nbsp;</p>
<p>After   new version of application is placed in the store, it requires all existing users   to upgrade in order to get it- big barrier</td>
<td width="267" valign="middle">Easier   to support and maintain as developer has complete access to the site&nbsp;</p>
<p>No   need to upgrade, all users see the latest version</td>
</tr>
<tr bgcolor="#E3E3E3">
<td width="128" valign="middle"><strong>Entry   Costs</strong></td>
<td width="243" valign="middle">some   app stores charge extra fees for publishing or certifying your app (Apple   charges developers <a href="http://developer.apple.com/iphone/program/">$99   and enterprises $299</a>, RIM charges <a href="http://na.blackberry.com/eng/developers/appworld/faq.jsp">$200</a> )</td>
<td width="267" valign="middle">None</td>
</tr>
<tr>
<td width="128" valign="middle"><strong>Revenue   Share</strong></td>
<td width="243" valign="middle">Need   to share sales revenue with the app stores (Apple takes 30%, RIM takes 20%)</td>
<td width="267" valign="middle">It’s   all yours</td>
</tr>
<tr bgcolor="#E3E3E3">
<td width="128" valign="middle"><strong>User   Experience</strong></td>
<td width="243" valign="top">Full control of User Interface</td>
<td width="267" valign="middle">Limited to the capabilities of HTML/CSS. User experience will largely depend on how the mobile website is designed</td>
</tr>
<tr>
<td width="128" valign="middle"><strong>Performance</strong></td>
<td width="243" valign="middle">Able   to achieve high performance through app code that runs locally on the device</td>
<td width="267" valign="middle">Performance will largely depend on how the mobile website is designed</td>
</tr>
<tr bgcolor="#E3E3E3">
<td width="128" valign="middle"><strong>Offline   Browsing</strong></td>
<td width="243" valign="middle">Possible</td>
<td width="267" valign="middle">HTML5   enables it to some extent, but is supported only on selected devices</td>
</tr>
</tbody>
</table>
]]></content:encoded>
			<wfw:commentRss>http://blog.dudamobile.com/mobile-web-vs-mobile-apps/feed/</wfw:commentRss>
		<slash:comments>31</slash:comments>
		</item>
	</channel>
</rss>

