<?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: Why App distribution policy could be bad for iPad</title>
	<atom:link href="http://tapadoo.com/2010/why-app-distribution-policy-could-be-bad-for-ipad/feed/" rel="self" type="application/rss+xml" />
	<link>http://tapadoo.com/2010/why-app-distribution-policy-could-be-bad-for-ipad/</link>
	<description>Incredible Mobile App Development</description>
	<lastBuildDate>Mon, 23 Apr 2012 14:51:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Douglas Gintz</title>
		<link>http://tapadoo.com/2010/why-app-distribution-policy-could-be-bad-for-ipad/comment-page-1/#comment-1688</link>
		<dc:creator>Douglas Gintz</dc:creator>
		<pubDate>Fri, 28 Jan 2011 03:34:10 +0000</pubDate>
		<guid isPermaLink="false">http://tapadoo.com/?p=380#comment-1688</guid>
		<description>Informative article. Struggling with the same thing myself. Throw into the mix the variety of smart devices &amp; platforms that need to be deployed to and its hard to see a clear strategy. Still looking at frameworks like Sencha and possibly leaving apps browser-based when possible. This approach too has drawbacks, and is definitely not as sexy. But then again, let&#039;s not forget that part of the Web 2.0 revolution was an effort to move off individual desktops w/ their own environmental restrictions, and to a single, easily maintainable, source. Feels like we&#039;re heading in the wrong direction at the moment for the benefit of the the device makers looking at apps as a way to add value. It&#039;ll will be interesting to see what happens over the next 12 months.</description>
		<content:encoded><![CDATA[<p>Informative article. Struggling with the same thing myself. Throw into the mix the variety of smart devices &amp; platforms that need to be deployed to and its hard to see a clear strategy. Still looking at frameworks like Sencha and possibly leaving apps browser-based when possible. This approach too has drawbacks, and is definitely not as sexy. But then again, let&#8217;s not forget that part of the Web 2.0 revolution was an effort to move off individual desktops w/ their own environmental restrictions, and to a single, easily maintainable, source. Feels like we&#8217;re heading in the wrong direction at the moment for the benefit of the the device makers looking at apps as a way to add value. It&#8217;ll will be interesting to see what happens over the next 12 months.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Van Alstine</title>
		<link>http://tapadoo.com/2010/why-app-distribution-policy-could-be-bad-for-ipad/comment-page-1/#comment-827</link>
		<dc:creator>Mike Van Alstine</dc:creator>
		<pubDate>Tue, 07 Sep 2010 20:01:14 +0000</pubDate>
		<guid isPermaLink="false">http://tapadoo.com/?p=380#comment-827</guid>
		<description>You know,

I really want to like Apple, I do. But with Monopolistic polices that make it impossible to practically distribute applications to small-medium sized niche businesses, they will keep losing the business clients.  This is one case where Apple needs to take a lesson from Microsoft, let everyone distribute software that they write for your platform freely.</description>
		<content:encoded><![CDATA[<p>You know,</p>
<p>I really want to like Apple, I do. But with Monopolistic polices that make it impossible to practically distribute applications to small-medium sized niche businesses, they will keep losing the business clients.  This is one case where Apple needs to take a lesson from Microsoft, let everyone distribute software that they write for your platform freely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Betlehem</title>
		<link>http://tapadoo.com/2010/why-app-distribution-policy-could-be-bad-for-ipad/comment-page-1/#comment-406</link>
		<dc:creator>Andrew Betlehem</dc:creator>
		<pubDate>Thu, 22 Apr 2010 06:09:14 +0000</pubDate>
		<guid isPermaLink="false">http://tapadoo.com/?p=380#comment-406</guid>
		<description>I totally agree. I&#039;ve been looking into ways to distribute custom apps to potential customers and as you say, there really isn&#039;t a nice way to do it.
We&#039;ll have to use Adhoc distribution, and just keep adding new Apple Developer accounts. Not sure if there&#039;s a limit to how many developer accounts you can have though.

It really means that you can&#039;t use iPhone/iPads to develop small scale apps for specific clients very easily. So compared to writing Java or VB apps, it&#039;s really hard to distribute them.

Maybe, we&#039;ll just have to employ 490 extra staff to get our enterprise licence.</description>
		<content:encoded><![CDATA[<p>I totally agree. I&#8217;ve been looking into ways to distribute custom apps to potential customers and as you say, there really isn&#8217;t a nice way to do it.<br />
We&#8217;ll have to use Adhoc distribution, and just keep adding new Apple Developer accounts. Not sure if there&#8217;s a limit to how many developer accounts you can have though.</p>
<p>It really means that you can&#8217;t use iPhone/iPads to develop small scale apps for specific clients very easily. So compared to writing Java or VB apps, it&#8217;s really hard to distribute them.</p>
<p>Maybe, we&#8217;ll just have to employ 490 extra staff to get our enterprise licence.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Keneth Scarfi</title>
		<link>http://tapadoo.com/2010/why-app-distribution-policy-could-be-bad-for-ipad/comment-page-1/#comment-361</link>
		<dc:creator>Keneth Scarfi</dc:creator>
		<pubDate>Fri, 02 Apr 2010 09:49:25 +0000</pubDate>
		<guid isPermaLink="false">http://tapadoo.com/?p=380#comment-361</guid>
		<description>Hey great post! I enjoyed that.</description>
		<content:encoded><![CDATA[<p>Hey great post! I enjoyed that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dermdaly</title>
		<link>http://tapadoo.com/2010/why-app-distribution-policy-could-be-bad-for-ipad/comment-page-1/#comment-299</link>
		<dc:creator>dermdaly</dc:creator>
		<pubDate>Mon, 01 Mar 2010 22:57:00 +0000</pubDate>
		<guid isPermaLink="false">http://tapadoo.com/?p=380#comment-299</guid>
		<description>Hi Ian,
thanks for your comment.  Like I mentioned, none of these are insurmountable.  I do believe that to the uninitiated (i.e. business people rather than developers), it will appear to be unreasonable.  This is the challenge to us.</description>
		<content:encoded><![CDATA[<p>Hi Ian,<br />
thanks for your comment.  Like I mentioned, none of these are insurmountable.  I do believe that to the uninitiated (i.e. business people rather than developers), it will appear to be unreasonable.  This is the challenge to us.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian Robinson</title>
		<link>http://tapadoo.com/2010/why-app-distribution-policy-could-be-bad-for-ipad/comment-page-1/#comment-298</link>
		<dc:creator>Ian Robinson</dc:creator>
		<pubDate>Mon, 01 Mar 2010 22:45:33 +0000</pubDate>
		<guid isPermaLink="false">http://tapadoo.com/?p=380#comment-298</guid>
		<description>If each ad hoc end user had their own Apple Developer account for $99, would that give them 100 devices ID slots to use each year? The developer could manage it for them. So restaurant with 10 iPads could use ad hoc distribution for theirs. If the developer worked with another restaurant they could have their own account for their device slots etc. I think some devs we know do this now.

Ian</description>
		<content:encoded><![CDATA[<p>If each ad hoc end user had their own Apple Developer account for $99, would that give them 100 devices ID slots to use each year? The developer could manage it for them. So restaurant with 10 iPads could use ad hoc distribution for theirs. If the developer worked with another restaurant they could have their own account for their device slots etc. I think some devs we know do this now.</p>
<p>Ian</p>
]]></content:encoded>
	</item>
</channel>
</rss>

