First off, thanks to everyone who came to Brent and my sessions at MAX. We had a great time doing them. It was a blast to meet so many people I’ve only known from email lists and blogs. People seemed really interested and excited in Apollo. Judging from the great questions, a lot of people had put some hard thought into what it’ll take to make Apollo successful.
I’m sure the final slides will get posted somewhere central, but I’d like now to summarize the key points of our presentation.
- Apollo applications are cross-platform bundles of files. A ZIP file plus a metadata file (application.xml)
- Once installed, Apollo applications are indistinguishable from other native applications. The Apollo runtime handles this install and makes the magic happen.
- A command-line toolchain will be freely availably (like the Flex SDK), and the integration with IDEs will be super-sweet. I’ve moved to an internal build of Apollo support in Flex Builder, and there’s no way I’m moving back…
- Control over native windows will be very simple, but also very powerful. No windows, multiple windows. System chrome, custom chrome. Transparent moving windows. Etc, etc, etc!
- HTML is a fully-integrated content type in Apollo. Display of HTML is entirely controllable via normal Flash/Flex APIs (which will also be exposed to JS). Scripting between Flash and JS will be trivial.