About Me

Hi. I'm John Eckman.

John Eckman

I'm a Sr. Director at Optaros, a professional services firm offering strategy, design, development, and consulting services to enterprises interested in leveraging free and open source software.

More about me

About Open Parenthesis

Contact Me

Optaros

Travel

 

Upcoming Conferences

Web 2.0 Kongress, Hamburg

Web Content 2009

SXSW Interactive, 2009

My Tweets
  • @jennbarnett I've actually seen travelers arguing with security about wanting to bring their sno-globes. They lose, every time. 23 hrs ago
  • or maybe I'm just following too many of thw wrong people - I have not bee cultivating (or weeding) my twitter garden enough . . . 1 day ago
  • feels like it's become just another channel for spam and self-promotion. is it just the arrival of the mainstream? like when aol hit usenet? 1 day ago
  • Twitter's shine is officially gone for me. maybe I'm just tired, or its the global economic collapse, bit I'm finding it hard to tweet. 1 day ago
  • Thinking of writing a song about conference rooms and how much alike they all are. Sort of like "homeward bound" by S&G but not as good 2 days ago
  • More updates...

Posting tweet...

Powered by Twitter Tools.

Optaros Blogs
Affiliations

[FSF Associate Member]

Creative Commons
Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.
January 27, 2007
« Previous Post: You got your REST in my SOA
Next Post: digital.life »

Is Apollo the future or RIAs?

Tagged with: , , , , , , — John @ 4:03 pm

Apollo Mike Chambers recently posted an updated Apollo presentation on his blog.

If you’re not familiar with Apollo, it is a cross-platform (purportedly Windows, Mac OS X, and Linux) application which will run applications developed using HTML & Ajax as well as Flex/Flash applications: a rich internet application container of sorts. It’ll also understand the PDF format and be able to open PDF documents.

The interesting challenge, I think, is whether Apollo, or something like it, could replace the web browser as the fundamental container for internet applications. (A corollary question: if it could, would that be a good thing?)
As a desktop application, the Apollo container can add access to the local file system, as well as a mature model for online/offline connectivity (for applications to function in partially connected mode). Apollo could also offer the application developer more control over the “chrome” or “skin,” which browsers have traditionally kept under user control.

However, it seems like a step backward to revert to the application container model when the web browser has been doing quite well, thank you. Installing the Flash plugin is one thing, but having in essence a flash-plugin-on-steroids that can also do HTML and Ajax starts to seem like a web browser replacement. Do we need another?

Will users find the additional functionality of Apollo apps compelling enough to run them alongside the browser?

Unfortunately the beta release is now said to be early 2007 - they used to say late 2006. So we’ll have to wait and see. (Maybe they need to open source the whole thing so we can get it on schedule - it is using WebKit already).
You can sign up to be notified when the beta is released, or get more info about Apollo at Adobe Labs.

(Kevin Lynch was also on Talk Crunch December 16 2006: Here Comes Apollo - at which point he said Apollo would run first on Windows and Mac, then they would work on Linux after Flash Player 9 was done.)

Trackback url for this post: http://www.openparenthesis.org/2007/01/27/apollo/trackback

2 Comments for this post
Cloudy Thinking » Blog Archive » Adobe’s Apollo — the Next Generation Browser? Says:

[...] John Eckman writes asks if the ADobe Apollo platform might one day replace your browser. [...]

steinarcarlsen Says:

Open Parenthesis » Is Apollo the future or RIAs?

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

« Previous Post: You got your REST in my SOA
Next Post: digital.life »