<?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: iWork for the iPad:  Game changer for the software business</title>
	<atom:link href="http://mark.madsenlab.org/2010/01/iwork-for-the-ipad-game-changer-for-the-software-business.html/feed" rel="self" type="application/rss+xml" />
	<link>http://mark.madsenlab.org/2010/01/iwork-for-the-ipad-game-changer-for-the-software-business.html#utm_source=feed&amp;utm_medium=feed&amp;utm_campaign=feed</link>
	<description>Scientia non habet inimicum nisi ignorantem</description>
	<lastBuildDate>Sun, 31 Jul 2011 00:01:44 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.3</generator>
	<item>
		<title>By: admin</title>
		<link>http://mark.madsenlab.org/2010/01/iwork-for-the-ipad-game-changer-for-the-software-business.html/comment-page-1#comment-5866</link>
		<dc:creator>admin</dc:creator>
		<pubDate>Thu, 04 Feb 2010 06:35:38 +0000</pubDate>
		<guid isPermaLink="false">http://mark.madsenlab.org/?p=1029#comment-5866</guid>
		<description>Oh, I think there&#039;s absolutely both an opportunity here and a sea-change in app design, as you mention.  We&#039;ll build things in smaller pieces and for more specific functions, and rely on exchanging data.  You already see this in some ways, but it&#039;ll become more prevalent on a larger device like the iPad.  

Though it&#039;s going to cause more of the complexity I talked about in a post today; apps that we used to think of as unitary things will now rely on distributed systems and data, and that means as developers we have to be much better about ensuring consistency and not relying on the next code down the line to do it...</description>
		<content:encoded><![CDATA[<p>Oh, I think there&#8217;s absolutely both an opportunity here and a sea-change in app design, as you mention.  We&#8217;ll build things in smaller pieces and for more specific functions, and rely on exchanging data.  You already see this in some ways, but it&#8217;ll become more prevalent on a larger device like the iPad.  </p>
<p>Though it&#8217;s going to cause more of the complexity I talked about in a post today; apps that we used to think of as unitary things will now rely on distributed systems and data, and that means as developers we have to be much better about ensuring consistency and not relying on the next code down the line to do it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Jones</title>
		<link>http://mark.madsenlab.org/2010/01/iwork-for-the-ipad-game-changer-for-the-software-business.html/comment-page-1#comment-5864</link>
		<dc:creator>Kelly Jones</dc:creator>
		<pubDate>Wed, 03 Feb 2010 22:35:35 +0000</pubDate>
		<guid isPermaLink="false">http://mark.madsenlab.org/?p=1029#comment-5864</guid>
		<description>Getting back to your point about the change in the cost structure of applications. Think of the old argument about your typical office suite of applications. A person will use only 5% of the available features, but it&#039;s a different subset for each person. Hence the need to buy the entire suite to satisfy the universe of customers. Think of your typical iPhone application where the application provides functionality to post photos to Flickr. The iPhone application provides specific functionality to do just a few things out of the entire functionality of Flickr. Now imagine that there are many Flickr applications, some that allow for posting of pictures, some that allow for following photos that have been posted by your friends, etc... Notice that an iPhone Flickr application is not required to know everything about Flickr in order to function properly. I would consider the entire Flickr API as the entire &quot;Office Suite&quot;, but the client functionality has been decoupled. Hence the ability to offer an application for $9.99. In the old world the document format and the implicit functionality of the associated application defined the type of client that could use it in a meaningful way.  With a typical iPhone/iPad app, the barrier to entry is lowered and the low price makes it a low risk for the end user to try out. 

Anyways, I haven&#039;t fully fleshed out my thoughts on this topic, but it&#039;s very interesting.</description>
		<content:encoded><![CDATA[<p>Getting back to your point about the change in the cost structure of applications. Think of the old argument about your typical office suite of applications. A person will use only 5% of the available features, but it&#8217;s a different subset for each person. Hence the need to buy the entire suite to satisfy the universe of customers. Think of your typical iPhone application where the application provides functionality to post photos to Flickr. The iPhone application provides specific functionality to do just a few things out of the entire functionality of Flickr. Now imagine that there are many Flickr applications, some that allow for posting of pictures, some that allow for following photos that have been posted by your friends, etc&#8230; Notice that an iPhone Flickr application is not required to know everything about Flickr in order to function properly. I would consider the entire Flickr API as the entire &#8220;Office Suite&#8221;, but the client functionality has been decoupled. Hence the ability to offer an application for $9.99. In the old world the document format and the implicit functionality of the associated application defined the type of client that could use it in a meaningful way.  With a typical iPhone/iPad app, the barrier to entry is lowered and the low price makes it a low risk for the end user to try out. </p>
<p>Anyways, I haven&#8217;t fully fleshed out my thoughts on this topic, but it&#8217;s very interesting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mark</title>
		<link>http://mark.madsenlab.org/2010/01/iwork-for-the-ipad-game-changer-for-the-software-business.html/comment-page-1#comment-5862</link>
		<dc:creator>mark</dc:creator>
		<pubDate>Wed, 03 Feb 2010 20:56:26 +0000</pubDate>
		<guid isPermaLink="false">http://mark.madsenlab.org/?p=1029#comment-5862</guid>
		<description>Indeed Kelly, you&#039;re absolutely right.  Sharepoint is collaboration done 1995 style, with a thin veneer of web technology to obscure the fact that you&#039;re still using heavy desktop software.  

Not that heavy desktop apps will go away, in the slightest.  It&#039;s hard to imagine in the short term anyone paying the performance penalty to run Adobe Photoshop or Illustrator, or Mathematica, in a web or hosted version.  But it&#039;s time to admit that the *function* provided by a word processor, after five or six turns of Moore&#039;s Law, need not be tethered to the &quot;form factor&quot; of desktop applications, as you say.</description>
		<content:encoded><![CDATA[<p>Indeed Kelly, you&#8217;re absolutely right.  Sharepoint is collaboration done 1995 style, with a thin veneer of web technology to obscure the fact that you&#8217;re still using heavy desktop software.  </p>
<p>Not that heavy desktop apps will go away, in the slightest.  It&#8217;s hard to imagine in the short term anyone paying the performance penalty to run Adobe Photoshop or Illustrator, or Mathematica, in a web or hosted version.  But it&#8217;s time to admit that the *function* provided by a word processor, after five or six turns of Moore&#8217;s Law, need not be tethered to the &#8220;form factor&#8221; of desktop applications, as you say.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kelly Jones</title>
		<link>http://mark.madsenlab.org/2010/01/iwork-for-the-ipad-game-changer-for-the-software-business.html/comment-page-1#comment-5861</link>
		<dc:creator>Kelly Jones</dc:creator>
		<pubDate>Tue, 02 Feb 2010 00:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://mark.madsenlab.org/?p=1029#comment-5861</guid>
		<description>Mark,
Interesting post. One thing the introduction of the iPad clearly shows is that computing for business purposes is being released from its earlier singular PC confines. Notice that I&#039;m not saying a normal PC is unimportant. It also clearly shows that you don&#039;t need to store your entire universe on one device. Office is  a jail. Sure, you can send files around to a bunch of people on a distro list, but who wants to do that??? As limited as Google Docs may be, I can  access it from various mobile apps for various purposes. Surely there&#039;s a business opportunity there. Think of the popularity of Microsoft&#039;s *clunky* Sharepoint software, yet people use it in droves.  The iPad  and the underlying cloud infrastructure is a harbinger of things to come. Anyone who misses that is fooling themselves.</description>
		<content:encoded><![CDATA[<p>Mark,<br />
Interesting post. One thing the introduction of the iPad clearly shows is that computing for business purposes is being released from its earlier singular PC confines. Notice that I&#8217;m not saying a normal PC is unimportant. It also clearly shows that you don&#8217;t need to store your entire universe on one device. Office is  a jail. Sure, you can send files around to a bunch of people on a distro list, but who wants to do that??? As limited as Google Docs may be, I can  access it from various mobile apps for various purposes. Surely there&#8217;s a business opportunity there. Think of the popularity of Microsoft&#8217;s *clunky* Sharepoint software, yet people use it in droves.  The iPad  and the underlying cloud infrastructure is a harbinger of things to come. Anyone who misses that is fooling themselves.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

