<?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: Would You Still Use AIR if Most of the Features Were Available in the Browser?</title>
	<atom:link href="http://blog.digitalbackcountry.com/2007/11/would-you-still-use-air-if-most-of-the-features-were-available-in-the-browser/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.digitalbackcountry.com/2007/11/would-you-still-use-air-if-most-of-the-features-were-available-in-the-browser/</link>
	<description>Ryan Stewart on the Flash Platform</description>
	<lastBuildDate>Sat, 04 Sep 2010 00:03:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: Tony MacDonell</title>
		<link>http://blog.digitalbackcountry.com/2007/11/would-you-still-use-air-if-most-of-the-features-were-available-in-the-browser/comment-page-1/#comment-4401</link>
		<dc:creator>Tony MacDonell</dc:creator>
		<pubDate>Tue, 20 Nov 2007 14:50:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digitalbackcountry.com/?p=1154#comment-4401</guid>
		<description>I think we are very early on with AIR in terms of it&#039;s proliferation. I wrote this awhile back:

http://blog.teknision.com/?p=27

Danny might be right that building desktop apps may not really be that compelling to some, but AIR looks a little different, when you look at it as a delivery model as opposed to a runtime for deploying &quot;Desktop Apps&quot; to.

I use the terms:

Destinational and Sanctuary, as opposed to web app and desktop app. I like this terminology, because it focuses on the fact that &quot;I have installed this app, and I am giving it special privedges&quot;, as opposed to &quot;This app runs on the desktop instead of the browser&quot;


A key thing, I think, is seeing an AIR runtime on a mobile device. That is where it could hit it&#039;s real sweet spot. While Flash Lite 3 is great, it may not be the best application runtime to deploy to. You have to distribute your content as raw SWF files as opposed to a packaged application.

However, could you imagine a mobile device that used AIR as it&#039;s native application runtime! That would be very compelling indeed!</description>
		<content:encoded><![CDATA[<p>I think we are very early on with AIR in terms of it&#8217;s proliferation. I wrote this awhile back:</p>
<p><a href="http://blog.teknision.com/?p=27" rel="nofollow">http://blog.teknision.com/?p=27</a></p>
<p>Danny might be right that building desktop apps may not really be that compelling to some, but AIR looks a little different, when you look at it as a delivery model as opposed to a runtime for deploying &#8220;Desktop Apps&#8221; to.</p>
<p>I use the terms:</p>
<p>Destinational and Sanctuary, as opposed to web app and desktop app. I like this terminology, because it focuses on the fact that &#8220;I have installed this app, and I am giving it special privedges&#8221;, as opposed to &#8220;This app runs on the desktop instead of the browser&#8221;</p>
<p>A key thing, I think, is seeing an AIR runtime on a mobile device. That is where it could hit it&#8217;s real sweet spot. While Flash Lite 3 is great, it may not be the best application runtime to deploy to. You have to distribute your content as raw SWF files as opposed to a packaged application.</p>
<p>However, could you imagine a mobile device that used AIR as it&#8217;s native application runtime! That would be very compelling indeed!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ryan Stewart</title>
		<link>http://blog.digitalbackcountry.com/2007/11/would-you-still-use-air-if-most-of-the-features-were-available-in-the-browser/comment-page-1/#comment-4400</link>
		<dc:creator>Ryan Stewart</dc:creator>
		<pubDate>Tue, 20 Nov 2007 14:10:32 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digitalbackcountry.com/?p=1154#comment-4400</guid>
		<description>@theklue Lee&#039;s point is a great one. As the size of our applications increase the desktop is a good delivery model. I don&#039;t wholly buy that because of the ever-increasing bandwidth, but right now it&#039;s good.

I think Rachel sums it up really well. That&#039;s actually what I tell a lot of customers. AIR isn&#039;t about replacing your websites, it&#039;s about augmenting them.</description>
		<content:encoded><![CDATA[<p>@theklue Lee&#8217;s point is a great one. As the size of our applications increase the desktop is a good delivery model. I don&#8217;t wholly buy that because of the ever-increasing bandwidth, but right now it&#8217;s good.</p>
<p>I think Rachel sums it up really well. That&#8217;s actually what I tell a lot of customers. AIR isn&#8217;t about replacing your websites, it&#8217;s about augmenting them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: theklue</title>
		<link>http://blog.digitalbackcountry.com/2007/11/would-you-still-use-air-if-most-of-the-features-were-available-in-the-browser/comment-page-1/#comment-4399</link>
		<dc:creator>theklue</dc:creator>
		<pubDate>Tue, 20 Nov 2007 09:03:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digitalbackcountry.com/?p=1154#comment-4399</guid>
		<description>Lee Brimelow points out the other day (@ Barcelona Bus Tour stop) one thing that is obvious but sometimes passes by. As online applications evolve, they&#039;re getting bigger (and much more richer). Downloading 1,2Mb web-app everyday can be very annoying. Having exactly the same app moved to the desktop can make sense in such cases.

But I also agree with Rachel statement; I think AIR should be a browser complement, at least in early stages of evangelization.</description>
		<content:encoded><![CDATA[<p>Lee Brimelow points out the other day (@ Barcelona Bus Tour stop) one thing that is obvious but sometimes passes by. As online applications evolve, they&#8217;re getting bigger (and much more richer). Downloading 1,2Mb web-app everyday can be very annoying. Having exactly the same app moved to the desktop can make sense in such cases.</p>
<p>But I also agree with Rachel statement; I think AIR should be a browser complement, at least in early stages of evangelization.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DannyT</title>
		<link>http://blog.digitalbackcountry.com/2007/11/would-you-still-use-air-if-most-of-the-features-were-available-in-the-browser/comment-page-1/#comment-4398</link>
		<dc:creator>DannyT</dc:creator>
		<pubDate>Tue, 20 Nov 2007 08:07:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digitalbackcountry.com/?p=1154#comment-4398</guid>
		<description>&quot;I hate internet radio in my browser&quot; - aw c&#039;mon, what&#039;s different about running finetune as an installed app Vs running it in it&#039;s own browser window (or even popup as I&#039;ve just noticed it allows) :P.

&quot;AIR represents a true hybrid approach to application development. It uses web technologies and development trends but allows developers to create real desktop applications&quot; - actually yes, I do agree. Specifically when we throw the cross-platform card in. That is a point that I&#039;d not given much thought to of late and for specifically creating desktop applications (regardless of an online equivilent) I agree that is very cool and a very real, sustainable use case. However, I do think AIR will need to evolve a little more to become a serious software application development platform with things such as devices IO.

Rachel also makes a very good point about AIR apps complimenting not replacing. I&#039;d even add &quot;and not duplicating&quot; to that too. Having a different tool to *support* your overall service is another great use-case for AIR and the flickr uploadr is a perfect example.

But for RIAs I still think having some of these features in browser will be the best approach.</description>
		<content:encoded><![CDATA[<p>&#8220;I hate internet radio in my browser&#8221; &#8211; aw c&#8217;mon, what&#8217;s different about running finetune as an installed app Vs running it in it&#8217;s own browser window (or even popup as I&#8217;ve just noticed it allows) <img src='http://blog.digitalbackcountry.com/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> .</p>
<p>&#8220;AIR represents a true hybrid approach to application development. It uses web technologies and development trends but allows developers to create real desktop applications&#8221; &#8211; actually yes, I do agree. Specifically when we throw the cross-platform card in. That is a point that I&#8217;d not given much thought to of late and for specifically creating desktop applications (regardless of an online equivilent) I agree that is very cool and a very real, sustainable use case. However, I do think AIR will need to evolve a little more to become a serious software application development platform with things such as devices IO.</p>
<p>Rachel also makes a very good point about AIR apps complimenting not replacing. I&#8217;d even add &#8220;and not duplicating&#8221; to that too. Having a different tool to *support* your overall service is another great use-case for AIR and the flickr uploadr is a perfect example.</p>
<p>But for RIAs I still think having some of these features in browser will be the best approach.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael</title>
		<link>http://blog.digitalbackcountry.com/2007/11/would-you-still-use-air-if-most-of-the-features-were-available-in-the-browser/comment-page-1/#comment-4397</link>
		<dc:creator>Michael</dc:creator>
		<pubDate>Tue, 20 Nov 2007 04:56:08 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digitalbackcountry.com/?p=1154#comment-4397</guid>
		<description>One thing to keep in mind, browsers will have a hard time adding AIR features. To add a feature to a browser, you need Mozilla and Microsoft to agree on it. Then you need all of their users to upgrade their browsers to the new version that has said feature. Then, and only then, will popular websites be able to use the new feature.

AIR on the other hand gives a simpler route. If a user wants the extra functionality provided by the desktop version of the website, then they download the app. Nobody is involved in this equation besides the site and the end users. The site is saddled with the responsibility of developing and maintaining two versions of their application. They also have to figure out how to monetize both versions...</description>
		<content:encoded><![CDATA[<p>One thing to keep in mind, browsers will have a hard time adding AIR features. To add a feature to a browser, you need Mozilla and Microsoft to agree on it. Then you need all of their users to upgrade their browsers to the new version that has said feature. Then, and only then, will popular websites be able to use the new feature.</p>
<p>AIR on the other hand gives a simpler route. If a user wants the extra functionality provided by the desktop version of the website, then they download the app. Nobody is involved in this equation besides the site and the end users. The site is saddled with the responsibility of developing and maintaining two versions of their application. They also have to figure out how to monetize both versions&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rahsun McAfee</title>
		<link>http://blog.digitalbackcountry.com/2007/11/would-you-still-use-air-if-most-of-the-features-were-available-in-the-browser/comment-page-1/#comment-4396</link>
		<dc:creator>Rahsun McAfee</dc:creator>
		<pubDate>Tue, 20 Nov 2007 02:10:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digitalbackcountry.com/?p=1154#comment-4396</guid>
		<description>I&#039;m with Rachel on this one. I like having a Twitter page, but I really like the Twitterific desktop app that keeps me up to date in real time instead of me going to a page to see what has happened.

AIR seems to act as a real practical way to compliment most existing web applications or services. Finetunes is a great AIR app. And where AIR seems to really shine is when you want to create a better experience for the user through a desktop uploader, or maybe manage your online photo album from your desktop, etc.</description>
		<content:encoded><![CDATA[<p>I&#8217;m with Rachel on this one. I like having a Twitter page, but I really like the Twitterific desktop app that keeps me up to date in real time instead of me going to a page to see what has happened.</p>
<p>AIR seems to act as a real practical way to compliment most existing web applications or services. Finetunes is a great AIR app. And where AIR seems to really shine is when you want to create a better experience for the user through a desktop uploader, or maybe manage your online photo album from your desktop, etc.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rachel</title>
		<link>http://blog.digitalbackcountry.com/2007/11/would-you-still-use-air-if-most-of-the-features-were-available-in-the-browser/comment-page-1/#comment-4395</link>
		<dc:creator>Rachel</dc:creator>
		<pubDate>Tue, 20 Nov 2007 00:30:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.digitalbackcountry.com/?p=1154#comment-4395</guid>
		<description>I think the most successful AIR apps will be those that complement their browser counterparts, and not replace them. An example application would be the Flickr Uploadr - it only exists to help you upload images from your desktop to Flickr, but it makes it a lot easier than it could be from the browser. Same type of idea for occasional connectivity - having an offline version to complement the online version.</description>
		<content:encoded><![CDATA[<p>I think the most successful AIR apps will be those that complement their browser counterparts, and not replace them. An example application would be the Flickr Uploadr &#8211; it only exists to help you upload images from your desktop to Flickr, but it makes it a lot easier than it could be from the browser. Same type of idea for occasional connectivity &#8211; having an offline version to complement the online version.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
