Sans Browser

Prism: Install Story?

October 29th, 2007 by enefekt

Wow, a lot of writing and discussion over Prism lately! And to think, all from a new name, logo, and a Labs post. (And I guess some weight from being an officially sanctioned experiment too.)

Of course, I’ll follow suit. Partly because I am interested in the technology, and partly because I am interested in how this relates to Adobe AIR, and Mozilla’s own technologies, like XUL. How is it integrated? How can some important features and functionality be integrated with HTML/JavaScript only?

I thought I would start by comparing the installation story with Adobe AIR. A lot has been made of how easy it is (or will be?) to make a web app into a desktop app. (A simple menu command from Firefox, and voila!) But that’s not the whole story. How does Prism get installed in the first place?

With Adobe AIR (which runs web apps as well on the desktop, built with HTML/CSS and JavaScript), there is a really cool installation story. You can create a special badge that a user can install your app (with permission of course) from a web page. The cool part though, is if they don’t have the Adobe AIR runtime, it will be installed auto-magically (with permission of course) along with your app! No need to direct them to a different website, instruct them to download something, then come back and get your app.

So how will Prism get installed? Sure, after it’s installed it’s somewhat smooth sailing. But getting software installed is a hurdle which should not be ignored. Adobe has excellent experience with this. Heck, installs of Firefox are dwarfed by Flash Player. So what’s Prism’s installation story?

Filed under: AIR, Adobe, IDA, Mozilla, Mozpad, Prism

Comments are closed.

ok2