Making Designer/Developer Collaboration a Reality

Historically, Microsoft's strength has been in the area of developer support, as illustrated by its flagship product Microsoft® Visual Studio® 2008. Even evangelists for Microsoft's rival, Adobe, speak highly of Microsoft's record supporting developers. And of course, the impressive size of the Microsoft® .NET developer community itself is proof of this premise.

By contrast Adobe's strength has historically been in the field of designers with its industry-leading products, Photoshop and Illustrator. Adobe further strengthened its position in this area with its 2005 acquisition of Macromedia and designer-oriented products Flash and Fireworks.

These facts have led to the rather interesting phenomenon that these two companies appear like inverse mirror images of each other with Microsoft being strong with developers and much weaker with designers and Adobe being strong with designers and much weaker with developers. Ironically, both companies are now pursuing a strategy to attract followers from the other company's camp. Although coming at this from different starting points, both companies agree on the importance of improving the designer/developer workflow in achieving this goal. Recently, Microsoft has made some significant further steps along this road.

Contributions of the Expression Studio to the Designer Developer Workflow
Over the past several years Microsoft has been working hard to become more designer oriented by offering products that are tightly integrated to its existing developer products. The primary fruits of this effort are the various products which make up Expression® Studio currently in its second edition.

A major goal of Expression Studio was to facilitate designer/developer collaboration to reduce overall project time to market while simultaneously achieving a better final result. The key element of this strategy is the new UI tool Expression Blend™ which designers can use to create rich user interfaces for both Microsoft® Windows® Presentation Foundation (WPF) and Microsoft Silverlight™ applications. What makes this possible is that the underlying language of Expression Blend is XAML, a variant of human readable yet highly toolable XML. Designers can therefore build the actual user interface using either a WYSIWYG designer or in code (the XAML). When done, this XAML is immediately usable without modification (not counting, of course, subsequent design improvements) by a developer who can open up the same project in Visual Studio 2008.

By contrast, if a designer creates a mockup of the user interface with Photoshop (as is often the case for those not targeting WPF and/or Silverlight), the developer needed to convert this vision into his best approximation using Visual C#® (or Visual Basic® .NET). Of course, not only did this typically require a significant amount of time and effort, but also the user interface (UI) actually produced by the developer was only a reasonably close approximation of the designer's original vision. This oftentimes resulted in a final product that is not a high-fidelity reproduction of the original design.

Like any complex application, Expression Blend has a learning curve but any competent designer should be able to master it without too much difficulty. Microsoft has intentionally made the Expression Blend UI similar to the UI with which Adobe-based designers are already familiar. For example, many of the Expression Blend (and other Expression products as well) keyboard shortcuts match their Adobe (and industry standard) equivalents. Microsoft also has an extensive collection of free training materials including Quick Start Guides and training videos. Often for designers new to Expression Blend, it is easiest to begin by using the visual design surface and then studying the XAML output before graduating to hand coding the XAML.