Microsoft Expression Design and Blend not ready for prime time

The last two days I attended Microsoft Expression Design and Blend training with several colleagues from Falafel and my overwhelming take away was, these tools aren’t ready for prime time. My only guess is that Microsoft is trying to get these early beta quality tools out there to try and build mind share. Not only are these tools lacking in many major areas, a point made abundantly clear by the instructor’s constant stream of workaround and head scratchers, the high level strategy of where this product line is headed and how it’s going to enable designers and developers to work better together seems to have been left on the cutting room floor. Granted, I understand these are 1.0 products but XAML has been under development at MS for many years now and these products are lacking in some of the very basics.

Missing Workflow

In my mind the first and major flaw is the lack of support for iterative development. This is perhaps best illustrated by the fact Blend can’t open .design files produced by Design nor can Design open XAML files directly. In fact, to get from Design to Blend you actually have to export from Design to XAML. How this makes sense is simply beyond me. There doesn’t seem be to any real work flow from Design -> Blend -> VS.NET so I’m not entirely sure how you would incorporate these tools into a development process.

Flawed UI

Microsoft Expression Blend UI controls

The UI of these products as compared to VS.NET 2005 is severely flawed. From the non-standard UI controls and menus to the almost complete lack of keyboard support make using these products tiresome. Many elements of the UI are tiny glyphs some of which have function (circled in red) where others serve as labels (circled in yellow).

Microsoft Expression Blend UI

Microsoft Expression Blend UI

Another sore point for me is docking, it’s not implemented. Seriously, you float the various property windows but you can’t dock then in anything but their predetermined location. Oh yeah, and they always float on top.

The UI has a number of confusing aspects, one being the difference between a tab and a button. Pictured to the left is an example of where “Event” is a button and “Project” is a tab where the glyph will cause the window to float.

Btw, what’s with the Gothic styling?

Poor Quality

With VS.NET 2003 Microsoft had some major quality issues and with 2005 they left the product in beta for a very long time to work out the kinks which I think really paid off. The Expression products are tied to a completely different quality metric that seems unrelated to Microsoft’s developer tools. While I didn’t experience crashes there were plenty of times where I was left wondering exactly what had happened and how I got the design surface into a particular state. I’ve already mentioned the keyboard issue but it’s so bad it’s worth repeating. The property editors are largely mouse only including Blend’s hierarchical view of your UI layout. Additionally, the selection logic is totally flawed with both a highlight rect and a selected item at the same time. Expression also brings to the table a context menu style I’ve never seen before in Windows where clicking and holding causes a context menu to appear though you can also right click as well. 


First, if you I’ll add that Joshua (didn’t catch his last name) from IT Mentor was a great instructor and very knowledgeable about the Expression products so kudos there.

While there is lots of promise in XAML for UI design and development this first cut for these tools isn’t up to par in my book. I think there are some nice concepts embodied here but they have a lot of maturing to do before they can be considered widely useful for day-to-day design and development of Windows applications. I do find it rather ironic that these tools which are designed to help you create high quality UI’s have so many seemingly obvious UI problems. Bottom line, if you’re considering Design and Blend be sure to take full advantage of the trial period!

2 thoughts on “Microsoft Expression Design and Blend not ready for prime time

  1. Steve, I agree. WPF has great potential, but Blend is only useful for small things right now. For example, if you change XML persistence to custom written binding using assemblies, you lose design-time capabilities. Furthermore, even though the new approach to build dialog is nice, it is nothing to quickly ("RAD") write a small tool etc. That might be not a use case for WPF, but I think it should be easier. VS 2008 beta 2 also has the issue with WPF that you have like 300 properties for every "thing" you drop on a form and the IDE does not help you to design that properly. So, as you said, I still prefer good ol’ VCL – in the .NET space:-)

  2. I am sitting in a Essential SilverLight 2 training course right now ( Course is really good and the trainers are doing a great job. I was doing some Internet searching for what are the real differences between Design and Blend, and why? (’cause we had already mentioned the export from Design, and we have focused attention on VS.NET 2008 and Blend).
    Seems to me Microsoft would be better to merge Design and Blend, and really get behind this XAML stuff…. in my opinion… XAML has too much WPF concepts and not enough HTML/DHTML/CSS or even ASP.NET Controls, at least for the concepts and the behavior of the user interface mark up language. This is all interesting, but it is very difficult to get my mind around…. coming from a deep rooted Internet background, lots of HTML/DHTML/CSS, and ASP.NET Controls.

Comments are closed.