<?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: The iPhone will Never be an Enterprise Device</title>
	<atom:link href="http://davidgalbraith.org/business/the-iphone-will-never-be-an-enterprise-device/1320/feed/" rel="self" type="application/rss+xml" />
	<link>http://davidgalbraith.org/business/the-iphone-will-never-be-an-enterprise-device/1320/</link>
	<description>Just another WordPress weblog</description>
	<pubDate>Tue, 06 Jan 2009 09:55:22 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Tom Plunkett</title>
		<link>http://davidgalbraith.org/business/the-iphone-will-never-be-an-enterprise-device/1320/comment-page-1/#comment-4796</link>
		<dc:creator>Tom Plunkett</dc:creator>
		<pubDate>Sun, 14 Sep 2008 17:46:50 +0000</pubDate>
		<guid isPermaLink="false">http://davidgalbraith.org/business/the-iphone-will-never-be-an-enterprise-device/1320/#comment-4796</guid>
		<description>As we have discussed, I do not agree with this argument -- though I would not stick with a single product (the iPhone), but rather the change in the landscape of the class of devices that include Blackberrys and iPhones. The Blackberry will change because it must to compete with the potential the iPhone presents. Also, the current gen iPhone is not the device that will open the corporate world to Apple.

As to correlating early 80s lack of corporate adoption of the Mac to this --  it is incorrect. Corporate unwillingness to adopt Apple computers had more to do with existing technology commitments and the future of distributing that technology to the desktop. IBM (and competitors) ruled this world of centralized computing, and from that the distribution of the tools to the desktop. Apple either had to develop the technologies to integrate to with this pre-existing model/investment (providing 3270 terminal emulation is not integration) *and* convince corporations that they would continue to improve the technologies that were defined by IBM, or stick with their enormous investments and grow within the world dominated by IBM and similar class technologies.

Note, too, that no corporation adopted PCs as PCs, per se. They implemented them as "smart" 3270 terminals (actually, they were not very smart) and ultimately as business document production systems that replaced typewriters or mainframe connected word processing systems. Wasting mainframe power on a word processor for 100s or 1000s of document producers is not an efficient investment in mainframe technology. Add to this the fact that these systems connected to the mainframe (not each other via appletalk) -- the decision was a no-brainer.

One technology fit the existing eco-system. The other did not.</description>
		<content:encoded><![CDATA[<p>As we have discussed, I do not agree with this argument &#8212; though I would not stick with a single product (the iPhone), but rather the change in the landscape of the class of devices that include Blackberrys and iPhones. The Blackberry will change because it must to compete with the potential the iPhone presents. Also, the current gen iPhone is not the device that will open the corporate world to Apple.</p>
<p>As to correlating early 80s lack of corporate adoption of the Mac to this &#8212;  it is incorrect. Corporate unwillingness to adopt Apple computers had more to do with existing technology commitments and the future of distributing that technology to the desktop. IBM (and competitors) ruled this world of centralized computing, and from that the distribution of the tools to the desktop. Apple either had to develop the technologies to integrate to with this pre-existing model/investment (providing 3270 terminal emulation is not integration) *and* convince corporations that they would continue to improve the technologies that were defined by IBM, or stick with their enormous investments and grow within the world dominated by IBM and similar class technologies.</p>
<p>Note, too, that no corporation adopted PCs as PCs, per se. They implemented them as &#8220;smart&#8221; 3270 terminals (actually, they were not very smart) and ultimately as business document production systems that replaced typewriters or mainframe connected word processing systems. Wasting mainframe power on a word processor for 100s or 1000s of document producers is not an efficient investment in mainframe technology. Add to this the fact that these systems connected to the mainframe (not each other via appletalk) &#8212; the decision was a no-brainer.</p>
<p>One technology fit the existing eco-system. The other did not.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is the iPhone ready for business use? - Top Stocks Blog: Talk about the most noteworthy stocks in the market each day – MSN Money</title>
		<link>http://davidgalbraith.org/business/the-iphone-will-never-be-an-enterprise-device/1320/comment-page-1/#comment-4701</link>
		<dc:creator>Is the iPhone ready for business use? - Top Stocks Blog: Talk about the most noteworthy stocks in the market each day – MSN Money</dc:creator>
		<pubDate>Tue, 05 Aug 2008 17:28:10 +0000</pubDate>
		<guid isPermaLink="false">http://davidgalbraith.org/business/the-iphone-will-never-be-an-enterprise-device/1320/#comment-4701</guid>
		<description>[...] in Motion should be handing out the report to everyone. Web veteran David Galbraith says the iPhone will never be an enterprise product. "Businesses do not buy groundbreaking, beautifully designed products that give the impression they [...]</description>
		<content:encoded><![CDATA[<p>[...] in Motion should be handing out the report to everyone. Web veteran David Galbraith says the iPhone will never be an enterprise product. &#8220;Businesses do not buy groundbreaking, beautifully designed products that give the impression they [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
