
<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Decision3D &#187; flow apps</title>
	<atom:link href="http://www.decision3d.com/tag/flow-apps/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.decision3d.com</link>
	<description>Connecting the Enterprise</description>
	<lastBuildDate>Tue, 06 Oct 2009 15:43:27 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=abc</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Flow Apps and Information Flow</title>
		<link>http://www.decision3d.com/tech/flow-apps-and-information-flow/</link>
		<comments>http://www.decision3d.com/tech/flow-apps-and-information-flow/#comments</comments>
		<pubDate>Tue, 17 Feb 2009 18:14:30 +0000</pubDate>
		<dc:creator>Lee</dc:creator>
				<category><![CDATA[Tech]]></category>
		<category><![CDATA[flow apps]]></category>
		<category><![CDATA[Social Technology Tools]]></category>
		<category><![CDATA[Stowe Boyd]]></category>

		<guid isPermaLink="false">http://www.decision3d.com/?p=233</guid>
		<description><![CDATA[
Stowe Boyd is a great proponent of the Flow App. He posted a a definition of what a Flow App is by drawing a comparison to Inbox Apps:
Streaming applications are involved in communication, and are displacing the email models that typified Web 1.0. We all known how inboxes (a la email) work: people write an [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.stoweboyd.com/message/stowe-boyd-front-man-for-.html"><img class="alignright" title="Stowe Boyd" src="http://farm1.static.flickr.com/155/437658321_eed614d9b9_t.jpg" alt="437658321_eed614d9b9_t Flow Apps and Information Flow" width="100" height="67" /></a><br />
Stowe Boyd is a great proponent of the Flow App. He <a href="http://www.stoweboyd.com/message/2009/02/the-architecture-of-flow-key-features-of-streaming-applications.html">posted a a definition of what a Flow App</a> is by drawing a comparison to Inbox Apps:</p>
<blockquote><p>Streaming applications are involved in communication, and are displacing the email models that typified Web 1.0. We all known how inboxes (a la email) work: people write an email, address it to one or more people (or groups, in some cases), and then send it off. The email infrastructure delivers the mail to those addressed, who receive it in their respective inboxes:</p>
<ol>
<li>The inbox model is inherently private: the email is only delivered to a select group, and others cannot see it, even if that was desired.</li>
<li>The reach of the email is completely determined by the email&#8217;s author, and it is made on a piece by piece basis.</li>
<li>The ownership of the email shifts to the recipients when it is delivered: they have to delete, or file the email, which is no longer under the control of the author.</li>
</ol>
<p>Flow apps work very differently:</p></blockquote>
<blockquote>
<ol>
<li>Streaming apps are inherently open: the premise is that users create and share information in the open. This is about supporting open discourse.</li>
<li>The recipients opt into &#8217;subscribing&#8217; to certain people&#8217;s streams, so the decision about access to information is made by recipients, and this decision is general, not made on a post by post basis. I call this the &#8216;open following&#8217; feature, meaning anyone can choose who to follow.</li>
<li>The handling of the streamed posts does not transition to the recipients: it is still under the control of the author. Posts can be deleted, for example, or edited. And posts do not have to be &#8216;handled&#8217; by recipients: filed or archived. They simply slide from the top to the bottom of the stream, and march into oblivion, without the recipients having to manage them at all. While an archive exists, it is managed automatically by the streaming application. Collectively, these features add up to an anti-inbox model</li>
</ol>
</blockquote>
<p>He goes on to describe two Flow Apps, Twitter and Staction in some detail.</p>
<p>As I read this post I began wondering if the &#8220;flow&#8221; Stowe is talking about is similar to the &#8220;information flow&#8221; I discuss on this site. My first reaction is that the flow I talk about is different than what Stowe is discussing. Now this in turn makes me realize that I need to be clear about what I mean by &#8220;information flow&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.decision3d.com/tech/flow-apps-and-information-flow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
