XAML Authoring in Blend and VS: Workflow, tools, and tasks

On the Blend team we believe that deeper integration of design into software product planning and implementation will enable developers and designers to create great UX across desktop, web, and devices at a lower cost and with better productivity.

Common app workflows

Not everyone builds apps the same way and our tools must provide the flexibility to support a variety of workflows. Here are a couple of examples of common workflows.

Design first

UX Designer/Developer produces a comp, prototype or starting application.

Code first

Developer provides a model which the UX Designer/Developer then uses to create the UX.

Design & Code

The same user is creating the application end-to-end, or the UX Designer and Developer work hand-in-hand throughout the project.

The right tools for the user and the task

In order to best support all app developers and designers and workflows we now provide XAML authoring support in both Blend and Visual Studio, providing the right tools in the environment each user wants to work.

Visual Studio provides a great development tool with some design features that domain/enterprise and entrepreneurial developers will feel most at home. It is a code-centric environment but still provides the ability to edit app elements visually where it makes sense.

For a design-centric experience—for interaction designers, RIA developers, and the elusive “hybrid”—Blend provides even richer support for visual authoring that allows fine tuning and greater control over the styling and animation of their apps.

Of course, some tasks that are simply core to creating a XAML app must be available in both products, as illustrated in the image below.

Design and Dev Tasks in XAML authoring tools Blend and VS

Feature Comparison

The following table shows how these tasks map to the tools offered in each product for this release.

Feature comparison between XAML authoring tools Blend and VS

For Blend we focused on providing a richer toolset around styling and animation through the States pane and the Timeline while only providing a more limited support for Code and XAML editing which is provided at full fidelity in Visual Studio.

This is just the first release of both products leveraging some shared designer components. We plan to take this base and evolve each product based on feedback and targeted at each products unique users, workflow, and tasks.

Joanna Mason
Lead Program Manager
Blend

 

  • Brandon Collins

    Why must you limit each product? Why would blend only have basic editors? Currently the way intellisense for example works across environments is inconsistent and a huge pain. No intellisense for xaml namespaces in blend is another massive annoyance.

  • http://blogs.southworks.net/geoff Geoff Cox

    I love both VS and Blend. Blend lets me put my designer hat on and focus on style and interactivity, while VS lets me put on my developer hat and focus on bindings and data presentation.  I hope as Blend and VS “blend” (pun?), this wonderful transition won’t get lost.  Yes, the two have a lot in common and should probably share that infrastructure, but each should keep their presentation and workflow tuned to their respective audience.  Designers want faster turnaround and in-place visualization.  Developers want IntelliSense and structure.  Many of us live in both worlds.  Blend will always be the middle child between Design and VS, but it is serving a great purpose – it connects the visual design with the code in ways that are impractical for either Design or VS.  While VS will be forced to be better because of Blend, I hope it won’t assimilate it and destroy a great tool.

  • Pingback: XAML Authoring in Blend and VS: Workflow, tools, and tasks

  • Pingback: Dew Drop – April 3, 2012 (#1,298) | Alvin Ashcraft's Morning Dew

  • Lars Heinrich

    I don´t mind having a basic editor, as long as it is a fast editor. Right now Blend for Metro Style Apps takes ages to display xaml. Now it realy feels like VS… Sorry, but right now this version is not useable. Right now i´m feeling like using Interaction Designer again. What happend?

  • http://www.facebook.com/gbirbilis George Birbilis

    it was time for MS to do some code reuse (what do we have components for after all?). Hope they put RAD into VS again cause in recent years there’s been too much focus to Linux etc. programmer camps turning the clock back ages instead of going to next generation programming tools

  • Aleksandr SonicFlare

    Why do i have to use Blend? Why not add animations and visual states inside VS, so that i can forget the blend at all!