Today we posted the first public prerelease builds of Apollo on Adobe Labs—the result of over a year and a half of development. While we are very excited to finally get Apollo into your hands, we still have a lot of work to do.
The Apollo site on Adobe Labs covers what Apollo is—and why you might want it—in quite some depth. But here's a quick definition of what Apollo is from the official FAQ:
Apollo is the code name for a cross-operating system runtime being developed by Adobe that allows developers to leverage their existing web development skills (Flash, Flex, HTML, JavaScript, Ajax) to build and deploy rich Internet applications (RIAs) to the desktop.
As I mentioned, you can find several articles about Apollo on Adobe Labs that provide a more thorough discussion of what Apollo is. In particular, read Chapter 1, "Introduction to Apollo," of Apollo for Adobe Flex Developers Pocket Guide published by O'Reilly Media and available for download from Labs. This chapter explains in depth what Apollo is and the problems it aims to solve.
Not only did we release an alpha version of the Apollo runtime today, but we also released other tools and resources that make it possible for you to build Apollo applications:
Notice that we did not release new versions of Flex Builder or the Flex SDK. You can just use the current release versions (2.0.1) when developing Apollo application.
Have I mentioned alpha enough times already? What exactly do we mean by saying that this is an alpha release of Apollo?
It's pretty simple; an alpha release is a very first release, which means the following:
Here are some of the main features in this alpha build:
Even though that is a pretty decent list, there is still a ton of stuff we need to implement—and that will not be not included in the first alpha:
This is not a complete list but it should give you a pretty good idea of what the Apollo team is working on. You can expect to see these features in future builds on Adobe Labs, as well as in the Apollo 1.0 release later this year.
I have worked at Adobe (and Macromedia before the merger) for nearly seven years. During that time, one thing has remained constant: developers always take our technologies in directions that we never expect. While this is still an early build of Apollo, we can't wait to see what you do with it.
Check out theses articles and resources for more information about Apollo:
Mike Chambers has spent the last eight years building applications that target the Flash runtime. During that time, he has worked with numerous technologies, including Flash, Generator, .NET, Central, Flex, and Ajax. He is currently the Principal Product Manager for developer relations for Adobe AIR. He has written and spoken extensively on Flash and rich Internet application development and is coauthor of the Apollo for Adobe Flex Developers Pocket Guide, Adobe Integrated Runtime (AIR) for JavaScript Developers Pocketguide, Flash Enabled: Flash Design and Development for Devices as well as Generator and Flash Demystified. Mike received his Masters in International Economics and European Studies from the John Hopkins School of Advanced International Studies (SAIS) in 1998. When he is not programming, Mike can be found playing Halo 2, trying to recover from his World of Warcraft addiction, or playing with his two daughters.