Seattle.BloggersPub

I caught this job posting over at the Adobe jobs site. The Kiwi team is looking for a Computer Scientist and here’s the job description:

Adobe is seeking a Computer Scientist to join the Kiwi Project, to be responsible for Flex application development on projects related to emerging web 2.0 publishing standards designed to showcase the new Apollo runtime still under development. The role includes work related to emerging standards in blogging, RSS and Atom. The Kiwi Project maintains a public blog at: http://blogs.adobe.com/kiwi/

It sounds like this position is specifically for building Flex applications on the Apollo runtime. If you are a Flex developer and want to build some cutting edge applications, this would be a great way to go.

Knowledge@Wharton, the newsletter of the Wharton School has two great articles that are worth reading for anyone interested in the future of software. The first is a good summary of a panel at Supernova which discussed specifically how desktop software will look in the future. The panel got into some of the most important issues that need to be worked out, privacy being first and foremost. It’s an excellent summary and rounds out the issues nicely.

The second is more fun because it is an interview with Kevin Lynch (where’s the podcast?!). It is always interesting to hear Kevin’s take on things as he’s ‘behind the lines’ and one of the major factors directing the vision at Adobe. In the interview he talks about Microsoft, WPF, Apollo, and where Adobe is headed with the Engagement Platform.

It’s a big day for Apollo information. Mike Chambers posted the Apollo FAQ on labs today which is chock full of Apollo information. In addition, the Apollo page is undergoing a bit of a revamp now that it’s a permanent fixture on the site.

Between Mike’s podcasts, the information on labs, and the team blogs, we’re going to be getting a lot of info coming down the pipeline.

This week’s podcast by Mike Chambers gave us some information about the Apollo runtime which I think people will be interested in. The full podcast is well worth a listen, but here’s the summary of runtime deployment.

- They’re going to work “very hard” to get Apollo on every machine. (Let’s hope so).

- Leverage ubiquity of Flash to prompt people to download the Apollo runtime if they don’t have it (pretty standard). Using Flash, you’ll be able to detect if Apollo is installed and then if not, it will be very easy for users to download it.

- The Apollo runtime can actually be bundled in something like an .msi file with your Apollo app, so that you can both deploy the app and the runtime at the same time. This is going to be very, very helpful for the enterprise.

Great stuff, and Mike’s podcasts are becoming a veritable smorgasbord of Apollo tidbits.

Okay, forgive me, that’s probably the most misleading title ever. But it’s still true - http://labs.adobe.com/wiki/index.php/Apollo.

Labs is a wiki, right? So I added an Apollo page. It has links to some of the press articles about Apollo, which I think is a good start. Is this page going to last 5 minutes? Probably not, but Adobe really should put something about Apollo on labs.

After a week at CFUnited and my Mt. Rainier summit climb, I’ve been pretty much exhausted both mentally and physically, so the updates have been slow. I can barely write a coherent sentence let alone an entire post, but this was too newsworthy to pass up.

Mike Chambers posted on his blog that he’s starting an Apollo FAQ and is soliciting the community for questions to add to it. Hopefully this is a first step towards getting something official about Apollo on Adobe Labs, so head over and tell Mike what you want to know.

Part one of what will become a series in “Building RIAs” is up on my ZDNet blog. Part one covers OpenLaszlo, which if you’ve never seen before is worth checking out. And for another 6 days, it’s the only option that is commercially available. A big thanks to the OpenLaszlo team for answering all of my questions and working with me on the piece.

It’s been really informative for me to have a dialogue with all of the people creating RIA solutions, so I hope this first article is a success. My plan is to follow up with Flex, WPF/E, WPF and end with Apollo. If you have any suggestions, or want to see anyone else covered, drop me a line.

Ted Patrick posted that the developer week sessions from last week are posted online (seriously, how many times can I use ‘posted’ in one sentence), so if you didn’t get to check out the Apollo session, it’s now up for you. The demos don’t show a whole lot, but there is a ton of information in the questions and you do get to see a few apps running on Luis’ computer. There are also a ton of other good sessions that are worth looking into. I found the LiveCycle one to be very informative.

I took a quick break from my Sunday night to update the Unofficial Apollo FAQ with more information. I added the SiliconValley.com article I mentioned on Friday as well as some of the questions that Ikezi Kamanu pulled from the Adobe week session (big thanks Ikezi!). If you have anything you think I need to add, drop me a line. Until Adobe has an Apollo section up on Labs, I want to make sure that I have all the info anyone could want on Apollo.

I blogged about this article over on my ZDNet blog but I also wanted to mention it here because I think it’s very significant.

Adobe is starting to push back. They’re putting their mouth where their money is (I realize that seems backwards) and talking up both Apollo and their view of the future of software. As my readers know, I’m very excited about Apollo. At first I didn’t get it, and it’s clear from this thread that there are a lot of unanswered questions. I think this is the first step in answering those questions for you. Adobe is finally talking about Apollo, and hopefully the specifics will follow.