After working all this week on a Flex demo I decided to take today and take a look at the competition – Microsoft’s “Avalon” (Or, as the creative team at Microsoft now call it, the “Windows Presentation Foundation”). Unfortunately it isn’t running on my machine. When I try to open the XAMLPad the program crashes. I may need to uninstall everything and reinstall it but it takes a long time to install on my machine.
In lieu of actually being able to create some Avalon examples, I’ve been doing some research and I’m not sure what to make of it. In a lot of ways, I think that Avalon and Flex are on a collision course. Flex can become what Avalon will be – a way to bring rich internet functionality seamlessly to the desktop space. The goal with Avalon and Indigo seems to be allowing developers to easily create rich interfaces for Windows. Those interfaces could (in theory) be run without installers, access data over the web, and in make life in general very nice for the user. This is essentially what Flex does.
By leveraging the ubiquitous power of the web and the flash player, Flex has a big head start. In the argument of rich vs. reach, Flex really has the best of both worlds. Everyone with FlashPlayer 7 can use Flex applications and the developers/designers know it’s going to behave the same way for everyone regardless of their browser or operating system.
I’m a little curious as to why the Macromedia blogsphere doesn’t talk about Avalon more. I don’t think it’s a Flash-killer, but I think a discussion of the possible impact of Avalon on Flex would be worthwhile. Maybe as we find out more about Avalon people will start talking about it.
Tweet