 




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments on: Does Your Company Really Need a Custom Mobile App?</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/cheap-computing/does-your-company-really-need-a-custom-mobile-app/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/cheap-computing/does-your-company-really-need-a-custom-mobile-app/</link>
	<description>Your guide to low-cost computer hardware and software for both home and business use</description>
	<lastBuildDate>Thu, 11 Apr 2013 07:05:40 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Robin "Roblimo" Miller</title>
		<link>http://itknowledgeexchange.techtarget.com/cheap-computing/does-your-company-really-need-a-custom-mobile-app/#comment-17</link>
		<dc:creator>Robin "Roblimo" Miller</dc:creator>
		<pubDate>Tue, 15 Jan 2013 23:29:02 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/cheap-computing/?p=276#comment-17</guid>
		<description><![CDATA[ggruber, you&#039;re right. You can get as complicated as you want with mobile site(s), optimizing them for Galaxy S2 and iPhone 3 and so on. You can also believe in the KISS principle, and make your computer and mobile sites both as simple as possible.&#160;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;The thing is, browsers and mobile CSS are both getting better all the time. Designers, too, are getting more experience with designing for mobile devices.&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;Remember the days of &quot;best viewed with (browser)&quot; sites? That&#039;s sort of where we are with the mobile web. At the moment. But we won&#039;t be there for long. Please watch this space (same bat time, same bat channel) for another bit of information coming soon about why sanity and budgets will dictate the use of mobile &quot;all OSes&quot; sites instead of dedicated apps.&#160;&lt;/div&gt;]]></description>
		<content:encoded><![CDATA[<p>ggruber, you&#8217;re right. You can get as complicated as you want with mobile site(s), optimizing them for Galaxy S2 and iPhone 3 and so on. You can also believe in the KISS principle, and make your computer and mobile sites both as simple as possible.&nbsp;
<div></div>
<div>The thing is, browsers and mobile CSS are both getting better all the time. Designers, too, are getting more experience with designing for mobile devices.</div>
<div></div>
<div>Remember the days of &#8220;best viewed with (browser)&#8221; sites? That&#8217;s sort of where we are with the mobile web. At the moment. But we won&#8217;t be there for long. Please watch this space (same bat time, same bat channel) for another bit of information coming soon about why sanity and budgets will dictate the use of mobile &#8220;all OSes&#8221; sites instead of dedicated apps.&nbsp;</div>
]]></content:encoded>
	</item>
	<item>
		<title>By: ggruber66</title>
		<link>http://itknowledgeexchange.techtarget.com/cheap-computing/does-your-company-really-need-a-custom-mobile-app/#comment-16</link>
		<dc:creator>ggruber66</dc:creator>
		<pubDate>Mon, 14 Jan 2013 22:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://itknowledgeexchange.techtarget.com/cheap-computing/?p=276#comment-16</guid>
		<description><![CDATA[There is nothing wrong with this article, but on the other hand it is far from being right. Yes, building a mobile website has the flavor of build once, distribute everywhere, but it does not always lead to the best result. Many will likely interpret this article to say that you need just 1 mobile-optimized site. Yet there are phones and tablets to consider. You can utilize responsive design, but it is not simple, nor does it solve all the world&#039;s problems. Here&#039;s a good article on a &lt;a href=&quot;http://sixrevisions.com/mobile/methods-mobile-websites/&quot;&gt;comparison for building mobile optimized sites&lt;/a&gt;.&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;Secondly, the article quotes IDC market share numbers between iOS and Android to make the case that WTSP and others made a mistake in targeting iOS in addition to building a dedicated app. But the writer also conveniently leaves out statistics which say that even with the difference in &quot;activation&quot; share, that iOS leads in mobile browsing usage by a factor of 4:1 even with the imbalance the other way in activation share. Further the writer also leaves out the fact that user engagement is typically much higher in a dedicated native app than in a mobile site, in part because of finer control of the environment and the ability to leverage the native capabilities&#160;of the devices themselves in the interaction.&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;But&#160;despite&#160;the inaccuracies in the article, there are companies who would be better served with a mobile website than incurring the expense of a native app (whether iOS or Android). But it&#039;s decision that must be made thoughtfully, without bias and based on the objectives you want to achieve. This is not a religious battle, nor is it one where you should look only for the lowest cost solution.&lt;/div&gt;]]></description>
		<content:encoded><![CDATA[<p>There is nothing wrong with this article, but on the other hand it is far from being right. Yes, building a mobile website has the flavor of build once, distribute everywhere, but it does not always lead to the best result. Many will likely interpret this article to say that you need just 1 mobile-optimized site. Yet there are phones and tablets to consider. You can utilize responsive design, but it is not simple, nor does it solve all the world&#8217;s problems. Here&#8217;s a good article on a <a href="http://sixrevisions.com/mobile/methods-mobile-websites/">comparison for building mobile optimized sites</a>.
<div></div>
<div>Secondly, the article quotes IDC market share numbers between iOS and Android to make the case that WTSP and others made a mistake in targeting iOS in addition to building a dedicated app. But the writer also conveniently leaves out statistics which say that even with the difference in &#8220;activation&#8221; share, that iOS leads in mobile browsing usage by a factor of 4:1 even with the imbalance the other way in activation share. Further the writer also leaves out the fact that user engagement is typically much higher in a dedicated native app than in a mobile site, in part because of finer control of the environment and the ability to leverage the native capabilities&nbsp;of the devices themselves in the interaction.</div>
<div></div>
<div>But&nbsp;despite&nbsp;the inaccuracies in the article, there are companies who would be better served with a mobile website than incurring the expense of a native app (whether iOS or Android). But it&#8217;s decision that must be made thoughtfully, without bias and based on the objectives you want to achieve. This is not a religious battle, nor is it one where you should look only for the lowest cost solution.</div>
]]></content:encoded>
	</item>
</channel>
</rss>
