<?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: What should the future of Web App Stores be?</title>
	<atom:link href="http://almaer.com/blog/what-should-the-future-of-web-app-stores-be/feed" rel="self" type="application/rss+xml" />
	<link>http://almaer.com/blog/what-should-the-future-of-web-app-stores-be</link>
	<description>blogging about life, the universe, and everything tech</description>
	<lastBuildDate>Sat, 08 Sep 2012 07:06:53 -0700</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: André Schraner</title>
		<link>http://almaer.com/blog/what-should-the-future-of-web-app-stores-be/comment-page-1#comment-46627</link>
		<dc:creator>André Schraner</dc:creator>
		<pubDate>Fri, 21 May 2010 09:17:52 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/?p=2703#comment-46627</guid>
		<description>I fully agree that the Chrome Web Store is a big step forward as developers will be able to monetize their WEB applications. As I wrote in my recent blog post (http://linkingthoughts.com/2010/04/21/evolution-of-the-social-business-web-part-1/), I would as well favor a system where the user could e.g. choose the payment provider of his choice when logging into the browser. 

I wish that the industry would agree on standards for your other above mentioned levels of the stack. Google or Mozilla are the most potent actors in this area.

In addition, I even think that the simplest form of packaging is a single piece of content (html page or file) and the web should even offer the same possibilities for monetization even for those. This would of course imply that discoverability, distribution etc would definitely need to be open because pieces of content and web applications would just be identical to today&#039;s free websites and web applications, discoverable by search engines, typing in a url and sharable via social media.</description>
		<content:encoded><![CDATA[<p>I fully agree that the Chrome Web Store is a big step forward as developers will be able to monetize their WEB applications. As I wrote in my recent blog post (<a href="http://linkingthoughts.com/2010/04/21/evolution-of-the-social-business-web-part-1/)" rel="nofollow">http://linkingthoughts.com/2010/04/21/evolution-of-the-social-business-web-part-1/)</a>, I would as well favor a system where the user could e.g. choose the payment provider of his choice when logging into the browser. </p>
<p>I wish that the industry would agree on standards for your other above mentioned levels of the stack. Google or Mozilla are the most potent actors in this area.</p>
<p>In addition, I even think that the simplest form of packaging is a single piece of content (html page or file) and the web should even offer the same possibilities for monetization even for those. This would of course imply that discoverability, distribution etc would definitely need to be open because pieces of content and web applications would just be identical to today&#8217;s free websites and web applications, discoverable by search engines, typing in a url and sharable via social media.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Holton</title>
		<link>http://almaer.com/blog/what-should-the-future-of-web-app-stores-be/comment-page-1#comment-46624</link>
		<dc:creator>Mark Holton</dc:creator>
		<pubDate>Thu, 20 May 2010 04:10:50 +0000</pubDate>
		<guid isPermaLink="false">http://almaer.com/blog/?p=2703#comment-46624</guid>
		<description>I&#039;m in.  

...somewhere in that paragraph of discoverability is an XMPP implementation.</description>
		<content:encoded><![CDATA[<p>I&#8217;m in.  </p>
<p>&#8230;somewhere in that paragraph of discoverability is an XMPP implementation.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
