Adobe’s Apollo to Ease Desktop Development?
In early 2005, when Adobe announced an agreement to acquire Macromedia, creative professionals released a collective gasp. Many worried about a creative software monopoly, others pondered the fate of competing applications (GoLive versus Dreamweaver, Freehand versus Illustrator, etc), and some dreamed of what offspring may come of this union.
Like many, I’ve ever pined for a way to link the joys of dynamic online content with a desktop application. Widgets feel too “disconnected” and “tacked on,” Java’s GUI customization is daunting, complexity in building native applications (for any OS) is a turnoff for the uninitiated, and cross compatibility remains the bane of most existing methods. Thus, Apollo sounds great on paper!
Our laziness is also cause, in large part, for excitement. Web developers shouldn’t have to learn anything new in order to build an Apollo app. Retaining (and practicing) our general web-coding knowledge whilst working on desktop projects is also very appealing. As with widgets, bringing existing content out of browsers should be a mere afternoon endeavor.
Yet, all is not perfect.
Unfortunately, the 2007 pre-release will only be available for Windows and OS X. Though Linux support is in the schedule, there’s no word on where it falls in the development cycle.
Additionally, few have yet to dabble in Apollo so little is to be said outside of demos and announcements. So, let us be wary; remembering that the Greek’s Apollo was both a god of healing and of plague.
Charlie is a videographer, web developer and occasional correspondent for the WebProNews Video Blog.