Feeling Out Apollo

Posted on by

I had a couple of posts that caught my eyes enough to prompt a quick post. One was by Danny who has been doing a good thinking about Apollo. He asks who the Apollo developers are and whether they will be traditional desktop developer or web developers. I like the question he poses:

This is of course assuming there is any form of distinction between a desktop app developer and an internet application developer?

Apollo is a technology that is going to appeal to a wide range of people, but I see it less as something that will bring desktop developers to the web than as something that will open up the desktop to web developers. We’re starting to see the limits of the browser. A quick look at the Mozilla roadmap shows that they realize regular DHTML and JavaScript aren’t cutting it when it comes to delivering web-centric applications that are becoming popular. Regular users are tapping into this new, richer web, but as developers hit the bounds of what’s possible in a web browser, they need to move to a more robust platform.

The beauty of Apollo is that it gives them that robust platform while allowing them to use the development skillsets they already have. First and foremost this is an opportunity for web application developers to extend a presence to the desktop and add more functionality than is available to them in the browser. This should become a much more popular distribution model for the heavier applications.

The other post that caught my eye was one by Wayne Smallman who sums up Apollo in 15 points. It’s a good summary from someone who is outside the Adobe community and an indication of just how widespread Apollo interest really is. He also touches in Widgets in point 12, which is something I want to explore a lot more. I think widgets and RIAs have a lot in common and espouse a lot of the same ideals.

[tags]Apollo, Adobe, Rich Internet Applications, RIA[/tags]

Related posts:

  1. What Is Apollo For?
  2. Ajax, Not Flash, Will Drive Apollo Adoption
  3. Apollo – Revitalizing the Desktop
  4. What is the Audience for Apollo?
  5. Why Apollo is So Important
  • http://www.riapedia.com/ Mike Potter

    One point that a lot of people forget is that web developers are, in general, a group that likes to continue pushing boundaries, and learn new things.

    A lot of people started building out HTML websites, then added dynamic scripting about a decade ago, then learned CSS style sheets, and are now learning Ajax.

    As you correctly point out, as they realize the limitations of the browser, they’ll want to move past them. I also think most web developers have looked at real desktop applications and said “Man, I wish I could build something like that, as opposed to just a website.” That’s why they’ve added scripting and programming on the backend etc…

    Apollo is going to allow them to do what they’ve always wanted to do: create real, desktop applications, while leveraging their existing skill set and allowing them to learn new things (like creating desktop applications) without having to learn entire new programming languages or models.

    Mike

  • http://polyGeek.com oz

    I’m a Flash Web Developer and I can’t wait to get onto the desktop. About a year ago I started using an ActiveDesktop in XP that was essentially a Flash App that covered my desktop. With that I created a PostIt Notes app that was nice enough but I had to rely on SharedObjects to store data. Of course there are many limitations to that method. With Apollo I’ll be able to extend that app and add tons more functionality to it.

    And since I want to get paid to learn and work with Apollo I’m hoping that, and this is a long shot, I can work on some support apps for Zune – I work for the Xbox team. Wish me luck.

  • http://danny-t.co.uk DannyT

    hmmm, I think I foolishly took it as a given that Apollo will undoubtedly trigger an influx of web developers to move to desktop, and forgot to state that clearer in the post. Certainly far, far more than the other way around (desktop developers to web).

    But it will be interesting to watch the rediscovery of existing, discovery of new and re-definition of desktop development practices as the web crowd flock in. Also interesting to see how the traditional desktop devs take to the new boys on their territory :P

  • Marlon Smith

    I am a developer of web and desktop apps, mostly 3-tier desktop apps for my line-of-business. My only concern is that some webdevs/designers have no clue about good application architecture and OOAD.

    Overall I look forward to it maybe can clip some good ui concepts. :)

  • http://blog.digitalbackcountry.com Ryan Stewart

    @Mike – I like the thought about web developers pushing boundaries. You’re absolutely right. How many of us picked up an HTML book and started from there. That should mean good things.

    @oz – I’m sorry I haven’t subscribed to your blog sooner. That has been fixed. Keep up the good work dude!

    @Danny – It was a great post, and I used it as more an excuse to talk more about Apollo than anything else. Hopefully you and I can do some more back and forth.

    @Marlon – Haha, I laughed out loud at your comment on webdevs and good application architecture. That’s an EXCELLENT point. I hope we can come up with some good Apollo best practices to help ease the web folks into the desktop.

  • http://myblah-blah-tech.blogspot.com Wayne Smallman

    Hi Ryan and thanks for linking to my article. Much appreciated.

    What interests me is how are Microsoft going to respond to all of this.

    It’s clear that Microsoft are now moving into Adobe’s backyard, so is this to be proprietary versus openness, or are Microsoft going to play nice?

    Stuff that just works from a bunch of open technologies pulls people down roads that don’t necessarily lead to .Net, which is where Microsoft will want people to be.

    The coming year should be a interesting spectacle…

  • http://www.hkqd99.com/registration-company.htm 注册公司

    bei jing is very good

  • http://www.51bvi.com 歼击机