<?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: Google grabs HP webOS Enyo HTML5 team</title>
	<atom:link href="http://www.slashgear.com/google-grabs-hp-webos-enyo-html5-team-25229995/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.slashgear.com/google-grabs-hp-webos-enyo-html5-team-25229995/</link>
	<description>Feeding Your Gadget and Tech Obsessions</description>
	<lastBuildDate>Thu, 21 Jun 2012 12:21:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: gmaninvan</title>
		<link>http://www.slashgear.com/google-grabs-hp-webos-enyo-html5-team-25229995/#comment-213202</link>
		<dc:creator>gmaninvan</dc:creator>
		<pubDate>Fri, 25 May 2012 14:22:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.slashgear.com/?p=229995#comment-213202</guid>
		<description><![CDATA[This kind of confirms what I have suspected for a long time. Chrome OS and Android will eventually share web apps. It makes sense. Think about it.


The hold back on web apps is that people want to feel they are using a native app and not on a website. If the enyo framework is bridged into android, you will be able to run web apps natively. In addition, the same framework could be used to improve development tools for the chrome web store.


Eventually, when networks are fast and reliable enough, java based android apps will begin to be phased out in favor of web apps that have the ability to also run offline. The average user won&#039;t even know, nor will they care.


At this point, chrome OS and Android will begin to merge into one OS. As of right now, chrome OS in my opinion, is just for testing out web apps and learning capabilities for things such as offline use. It is also to try and push google apps and capture the educational market.


Everyone knows it doesn&#039;t make sense for google to offer two different OS&#039;s so this makes sense going forward. The first step is that chrome is now available on android. I suspect in a few versions, possibly key lime pie, you will see google announce HTML5 development tools for building android apps. Then google will succeed in what they wanted in the first place, the open web in your hand.]]></description>
		<content:encoded><![CDATA[<p>This kind of confirms what I have suspected for a long time. Chrome OS and Android will eventually share web apps. It makes sense. Think about it.</p>
<p>The hold back on web apps is that people want to feel they are using a native app and not on a website. If the enyo framework is bridged into android, you will be able to run web apps natively. In addition, the same framework could be used to improve development tools for the chrome web store.</p>
<p>Eventually, when networks are fast and reliable enough, java based android apps will begin to be phased out in favor of web apps that have the ability to also run offline. The average user won&#8217;t even know, nor will they care.</p>
<p>At this point, chrome OS and Android will begin to merge into one OS. As of right now, chrome OS in my opinion, is just for testing out web apps and learning capabilities for things such as offline use. It is also to try and push google apps and capture the educational market.</p>
<p>Everyone knows it doesn&#8217;t make sense for google to offer two different OS&#8217;s so this makes sense going forward. The first step is that chrome is now available on android. I suspect in a few versions, possibly key lime pie, you will see google announce HTML5 development tools for building android apps. Then google will succeed in what they wanted in the first place, the open web in your hand.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
