<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Why HTML5 won&#8217;t take the wind out of Apple&#8217;s sails</title>
	<atom:link href="http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/feed/" rel="self" type="application/rss+xml" />
	<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/</link>
	<description></description>
	<lastBuildDate>Thu, 23 May 2013 23:49:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Kony Appfan</title>
		<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/#comment-656611</link>
		<dc:creator><![CDATA[Kony Appfan]]></dc:creator>
		<pubDate>Mon, 19 Sep 2011 18:42:04 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=404523#comment-656611</guid>
		<description><![CDATA[It’s apparent that HTML5 and native applications each offer companies with unique advantages. The question is why companies still feel the need to develop for only one of these channels. Since consumers use each channel differently, companies should be developing for both to ensure they are creating a comprehensive offering that maximizes the potential of their mobile strategy. As the article notes, one reason that organizations are choosing to develop mobile websites over native applications is because of the perceived cost of developing the application across multiple platforms. One way to overcome this is to utilize a single application definition, which allows companies to make their offering available across numerous devices and channels at once without sacrificing any device’s powerful native capabilities. This allows companies to provide users across various devices and channels with a unique user experience, resulting in a comprehensive offering that will increase adoption rates and maximize ROI.

John Stewart
Kony]]></description>
		<content:encoded><![CDATA[<p>It’s apparent that HTML5 and native applications each offer companies with unique advantages. The question is why companies still feel the need to develop for only one of these channels. Since consumers use each channel differently, companies should be developing for both to ensure they are creating a comprehensive offering that maximizes the potential of their mobile strategy. As the article notes, one reason that organizations are choosing to develop mobile websites over native applications is because of the perceived cost of developing the application across multiple platforms. One way to overcome this is to utilize a single application definition, which allows companies to make their offering available across numerous devices and channels at once without sacrificing any device’s powerful native capabilities. This allows companies to provide users across various devices and channels with a unique user experience, resulting in a comprehensive offering that will increase adoption rates and maximize ROI.</p>
<p>John Stewart<br />
Kony</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Magnus Jern</title>
		<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/#comment-655946</link>
		<dc:creator><![CDATA[Magnus Jern]]></dc:creator>
		<pubDate>Fri, 16 Sep 2011 10:47:18 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=404523#comment-655946</guid>
		<description><![CDATA[I absolutely agree. One key point that you ignored here is the slow pace of innovation for HTML5 vs apps. Our assignments are currently split 50/50 between apps and mobile web (mostly HTML5) but all the innovation is done through apps. Read our blog post about this here:
http://www.mobilemarketinguniverse.com/?p=522

Magnus Jern
CEO,  Golden Gekko]]></description>
		<content:encoded><![CDATA[<p>I absolutely agree. One key point that you ignored here is the slow pace of innovation for HTML5 vs apps. Our assignments are currently split 50/50 between apps and mobile web (mostly HTML5) but all the innovation is done through apps. Read our blog post about this here:<br />
<a href="http://www.mobilemarketinguniverse.com/?p=522" rel="nofollow">http://www.mobilemarketinguniverse.com/?p=522</a></p>
<p>Magnus Jern<br />
CEO,  Golden Gekko</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shal</title>
		<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/#comment-655831</link>
		<dc:creator><![CDATA[Shal]]></dc:creator>
		<pubDate>Thu, 15 Sep 2011 22:11:09 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=404523#comment-655831</guid>
		<description><![CDATA[Why HTML 5 won&#039;t affect Apple.

Because Apple won&#039;t implement it, because it wasn&#039;t made or developed by apple. And Apple Fans don&#039;t fucking care. These are the same people who will buy the iPhone 5, even though it would be on par with phones that have been released 6 months ago.]]></description>
		<content:encoded><![CDATA[<p>Why HTML 5 won&#8217;t affect Apple.</p>
<p>Because Apple won&#8217;t implement it, because it wasn&#8217;t made or developed by apple. And Apple Fans don&#8217;t fucking care. These are the same people who will buy the iPhone 5, even though it would be on par with phones that have been released 6 months ago.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jeff Snyder</title>
		<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/#comment-655712</link>
		<dc:creator><![CDATA[Jeff Snyder]]></dc:creator>
		<pubDate>Thu, 15 Sep 2011 17:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=404523#comment-655712</guid>
		<description><![CDATA[Excellent comments from you throughout this thread.]]></description>
		<content:encoded><![CDATA[<p>Excellent comments from you throughout this thread.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamranhansenhansen</title>
		<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/#comment-655642</link>
		<dc:creator><![CDATA[Hamranhansenhansen]]></dc:creator>
		<pubDate>Thu, 15 Sep 2011 12:21:11 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=404523#comment-655642</guid>
		<description><![CDATA[Yes, the apps you could write for the original iPhone were HTML5.

HTML5 was started in 2004 and adopted by W3C in January 2007, 6 months before the original iPhone shipped. A key feature of iPhone Web app development was you had the HTML5 canvas to draw an interface on.

HTML5 is just a description of modern HTML, it describes what the browsers do, not some lofty future academic goal that we may never achieve. It is not as new as you think, and what little is new is backwards-compatible. The fact that the original iPhone supported less of the HTML5 spec than today&#039;s iPhone did not stop the apps from running or stop them from being HTML5.

The original iPhone had native apps built with the same tools Apple released a year later. Yes, definitely they were always going to do that. But they were always going to have HTML5 apps as well. They did not make WebKit for OS X so they could leave it out.]]></description>
		<content:encoded><![CDATA[<p>Yes, the apps you could write for the original iPhone were HTML5.</p>
<p>HTML5 was started in 2004 and adopted by W3C in January 2007, 6 months before the original iPhone shipped. A key feature of iPhone Web app development was you had the HTML5 canvas to draw an interface on.</p>
<p>HTML5 is just a description of modern HTML, it describes what the browsers do, not some lofty future academic goal that we may never achieve. It is not as new as you think, and what little is new is backwards-compatible. The fact that the original iPhone supported less of the HTML5 spec than today&#8217;s iPhone did not stop the apps from running or stop them from being HTML5.</p>
<p>The original iPhone had native apps built with the same tools Apple released a year later. Yes, definitely they were always going to do that. But they were always going to have HTML5 apps as well. They did not make WebKit for OS X so they could leave it out.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamranhansenhansen</title>
		<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/#comment-655639</link>
		<dc:creator><![CDATA[Hamranhansenhansen]]></dc:creator>
		<pubDate>Thu, 15 Sep 2011 12:02:19 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=404523#comment-655639</guid>
		<description><![CDATA[There is no walled garden. That is absurd in the extreme. Apple not only put HTML5 in iOS, they did 5 years of WebKit work first and co-writing of HTML5 in order to get it on there. They were the ones who ported the Web to ARM, remember? HTML5 is the most open API ever created. No device that runs HTML5 can be described as a walled garden. Your app can install locally from any server in the world.

App Store is managed 1) as an anti-malware initiative, the only successful one ever, resulting in a 100% malware-free native app platform, and 2) as an alternative to the unmanaged Web, which all users already have access to. These are great reasons. Arguing with success is for losers.

It is fine to create an HTML5 app and deploy on the Web and the Java platforms. App Store, though, offers you native C/C++ and the opportunity to make a much richer app than HTML5. Since user&#039;s baseline expectations are set by the Web, App Store enables you to wow them and that is what people are willing to pay for in an app. So if you give your HTML5 app to an Xcode coder and let him use it as a mock-up and then build on it from there, the money you pay that coder will come back to you 10 times over or more in increased sales because your app will be that much better.

In other words, native iOS app development pays for itself. No reason to avoid it if you want to be in App Store. If an app platform doesn&#039;t pay for itself, then by all means, wrap a Web app.]]></description>
		<content:encoded><![CDATA[<p>There is no walled garden. That is absurd in the extreme. Apple not only put HTML5 in iOS, they did 5 years of WebKit work first and co-writing of HTML5 in order to get it on there. They were the ones who ported the Web to ARM, remember? HTML5 is the most open API ever created. No device that runs HTML5 can be described as a walled garden. Your app can install locally from any server in the world.</p>
<p>App Store is managed 1) as an anti-malware initiative, the only successful one ever, resulting in a 100% malware-free native app platform, and 2) as an alternative to the unmanaged Web, which all users already have access to. These are great reasons. Arguing with success is for losers.</p>
<p>It is fine to create an HTML5 app and deploy on the Web and the Java platforms. App Store, though, offers you native C/C++ and the opportunity to make a much richer app than HTML5. Since user&#8217;s baseline expectations are set by the Web, App Store enables you to wow them and that is what people are willing to pay for in an app. So if you give your HTML5 app to an Xcode coder and let him use it as a mock-up and then build on it from there, the money you pay that coder will come back to you 10 times over or more in increased sales because your app will be that much better.</p>
<p>In other words, native iOS app development pays for itself. No reason to avoid it if you want to be in App Store. If an app platform doesn&#8217;t pay for itself, then by all means, wrap a Web app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamranhansenhansen</title>
		<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/#comment-655638</link>
		<dc:creator><![CDATA[Hamranhansenhansen]]></dc:creator>
		<pubDate>Thu, 15 Sep 2011 11:48:08 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=404523#comment-655638</guid>
		<description><![CDATA[You are misinformed.

iOS runs both native App Store apps and HTML5 Web apps. Both kinds of apps can be installed locally on an iOS device. Apple has no control over which HTML5 Web apps you choose to run, and you can install them from any server anywhere in the world. That is because Web apps run in a sandbox, they don&#039;t have to touch the hardware. App Store apps are managed in order to provide an alternative to unmanaged Web apps, and also because they are native C/C++ apps which run &quot;on the metal,&quot; and therefore require auditing to run safely and 100% malware-free. Native apps have the key to your house, you can&#039;t just let an unaudited app run on there.

Which do you think is the bigger evil: auditing native apps to make sure they are safe and achieving a 100% malware-free native application platform, or what Microsoft has on Windows, a plague of malware that has cost their users billions of dollars?

People who are buying iOS devices appreciate the features of one or the other app platform or both. You can use an iPad and never use App Store and still have access to hundreds of thousands of apps. Or you can use the hell out of App Store. Your choice. Same as the choice either to buy or not buy an iPad.

HTML5 apps were running on iOS 1 year before App Store even launched. The idea that you can&#039;t run whatever you want on your iPhone is crazy. It comes with like 20 apps and then you are on your own. Nothing gets on there that you don&#039;t put on there yourself. There are hundreds of thousands of either kind of app. Use what you like.]]></description>
		<content:encoded><![CDATA[<p>You are misinformed.</p>
<p>iOS runs both native App Store apps and HTML5 Web apps. Both kinds of apps can be installed locally on an iOS device. Apple has no control over which HTML5 Web apps you choose to run, and you can install them from any server anywhere in the world. That is because Web apps run in a sandbox, they don&#8217;t have to touch the hardware. App Store apps are managed in order to provide an alternative to unmanaged Web apps, and also because they are native C/C++ apps which run &#8220;on the metal,&#8221; and therefore require auditing to run safely and 100% malware-free. Native apps have the key to your house, you can&#8217;t just let an unaudited app run on there.</p>
<p>Which do you think is the bigger evil: auditing native apps to make sure they are safe and achieving a 100% malware-free native application platform, or what Microsoft has on Windows, a plague of malware that has cost their users billions of dollars?</p>
<p>People who are buying iOS devices appreciate the features of one or the other app platform or both. You can use an iPad and never use App Store and still have access to hundreds of thousands of apps. Or you can use the hell out of App Store. Your choice. Same as the choice either to buy or not buy an iPad.</p>
<p>HTML5 apps were running on iOS 1 year before App Store even launched. The idea that you can&#8217;t run whatever you want on your iPhone is crazy. It comes with like 20 apps and then you are on your own. Nothing gets on there that you don&#8217;t put on there yourself. There are hundreds of thousands of either kind of app. Use what you like.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamranhansenhansen</title>
		<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/#comment-655636</link>
		<dc:creator><![CDATA[Hamranhansenhansen]]></dc:creator>
		<pubDate>Thu, 15 Sep 2011 11:35:20 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=404523#comment-655636</guid>
		<description><![CDATA[HTML5 is not server-side, it runs on the client, same as native apps. The server is optional in HTML5, you are not supposed to rely on it being there. The first time the user uses the app, it is installed locally, and from then on, only pulls updates from the server.

So what you have in iOS is just 2 kinds of local app: native App Store and HTML5 Web app. They are like a yin yang, the 2 together give you a complete universe of apps. The native apps are iOS only, while the Web apps are universal. Native apps are managed, Web apps are open. Native apps are controlled by Apple, Web apps by W3C. Native apps have a commercial installer (App Store) and Web apps have a non-commercial installer (World Wide Web.) Native apps have Mac-like features (animation, multichannel audio, video, ease of use, refinement) and Web apps have Web-like features (minimalist audio, video, animation.)

Whatever project a developer is working on, one or the other type of app will be ideal, either HTML5 Web app or native App Store. But in both cases, you are making a local app.]]></description>
		<content:encoded><![CDATA[<p>HTML5 is not server-side, it runs on the client, same as native apps. The server is optional in HTML5, you are not supposed to rely on it being there. The first time the user uses the app, it is installed locally, and from then on, only pulls updates from the server.</p>
<p>So what you have in iOS is just 2 kinds of local app: native App Store and HTML5 Web app. They are like a yin yang, the 2 together give you a complete universe of apps. The native apps are iOS only, while the Web apps are universal. Native apps are managed, Web apps are open. Native apps are controlled by Apple, Web apps by W3C. Native apps have a commercial installer (App Store) and Web apps have a non-commercial installer (World Wide Web.) Native apps have Mac-like features (animation, multichannel audio, video, ease of use, refinement) and Web apps have Web-like features (minimalist audio, video, animation.)</p>
<p>Whatever project a developer is working on, one or the other type of app will be ideal, either HTML5 Web app or native App Store. But in both cases, you are making a local app.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Hamranhansenhansen</title>
		<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/#comment-655634</link>
		<dc:creator><![CDATA[Hamranhansenhansen]]></dc:creator>
		<pubDate>Thu, 15 Sep 2011 11:20:03 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=404523#comment-655634</guid>
		<description><![CDATA[How stupid of an Apple analyst do these guys have to be not to know:

• Apple is the biggest promoter of HTML5 — they co-wrote the spec, they created the reference browser, they ported it to ARM and made HTML5 standard on mobiles by sharing that code with all mobile makers, so that if you run an HTML5 app today, you are likely to be running it in Apple&#039;s HTML5 decoder, or that Apple was the first PC vendor to ship an HTML5 browser, and iOS is the best HTML5 app platform

• a key feature of App Store is that the apps do MORE than HTML5 apps — if they did not, App Store would have no reason to exist … but you can&#039;t do iMovie on the Web, you can&#039;t do music and audio

• that Apple only makes 1% on app sales — in other words, less than a penny on a 99 cent app, the other 29% they take is overhead?

The concern trolling for Apple lately is just sad. There is nothing bad that can be said about Apple&#039;s position. They are in a completely unprecedented position of leadership in the industry even for them.

HTML5 is a level playing field. Apple has no problem competing on a level playing field.]]></description>
		<content:encoded><![CDATA[<p>How stupid of an Apple analyst do these guys have to be not to know:</p>
<p>• Apple is the biggest promoter of HTML5 — they co-wrote the spec, they created the reference browser, they ported it to ARM and made HTML5 standard on mobiles by sharing that code with all mobile makers, so that if you run an HTML5 app today, you are likely to be running it in Apple&#8217;s HTML5 decoder, or that Apple was the first PC vendor to ship an HTML5 browser, and iOS is the best HTML5 app platform</p>
<p>• a key feature of App Store is that the apps do MORE than HTML5 apps — if they did not, App Store would have no reason to exist … but you can&#8217;t do iMovie on the Web, you can&#8217;t do music and audio</p>
<p>• that Apple only makes 1% on app sales — in other words, less than a penny on a 99 cent app, the other 29% they take is overhead?</p>
<p>The concern trolling for Apple lately is just sad. There is nothing bad that can be said about Apple&#8217;s position. They are in a completely unprecedented position of leadership in the industry even for them.</p>
<p>HTML5 is a level playing field. Apple has no problem competing on a level playing field.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: AMP</title>
		<link>http://gigaom.com/2011/09/13/why-html5-wont-take-the-wind-out-of-apples-sails/#comment-655485</link>
		<dc:creator><![CDATA[AMP]]></dc:creator>
		<pubDate>Wed, 14 Sep 2011 18:46:20 +0000</pubDate>
		<guid isPermaLink="false">http://gigaom.com/?p=404523#comment-655485</guid>
		<description><![CDATA[What is not fair? Apple created the App Market, they manage the resources, they test the apps and give you process to collect the sale. How is that not different then any store? Most retail markup is 10% to 50%. The Fact that Apple takes 30% is not bad. How much more would it cost small developers creating their own Market, manage all the resources, the payment systems, taxes, technical support and legal claims against them.
Apple might be heavy handed at times, but they manage a stable and reliable Market place to IOS apps.]]></description>
		<content:encoded><![CDATA[<p>What is not fair? Apple created the App Market, they manage the resources, they test the apps and give you process to collect the sale. How is that not different then any store? Most retail markup is 10% to 50%. The Fact that Apple takes 30% is not bad. How much more would it cost small developers creating their own Market, manage all the resources, the payment systems, taxes, technical support and legal claims against them.<br />
Apple might be heavy handed at times, but they manage a stable and reliable Market place to IOS apps.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
