Search code examples
.netwpfexpression-blendapplication-design

WPF Designers : What is your design process?


I am going to totally re-ask this question. So this is one big edit

I was looking for a little feedback from WPF professionals, about their design process. For example, when I design a website, before I write any HTML, CSS, JavaScript, I design the interface in Photoshop so I can I show the client a proof of what their site is going to look like. Before I write any code, I choose the style, the color scheme, most if not all third-party graphics (stock photography) Once the client approves the design, I then start building it.

I was wondering what the equivalent would be for designing a WPF desktop application. When it comes time to design the interface, select the color scheme, select the button styles, select any images that might go into it, is it common to create a mockup first? Do you simply create all the graphics on the fly, at the same as building it. Or is it more common to simply find a theme/skin online and employ it in your app?

And again, I know there is no right answer, I was just looking to hear what you all do.

Thanks

p.s. - I have Expression Blend 4, I am ok at hand-writing XAML (not just using Design View in Blend). MY question is not about what tool I should use to build WPF applications, but about the design process.


Solution

  • I would recommend doing your screens and assets in Illustrator, since you can import the vector assets later on. However, no miracle, and Blend is surely the tool to do the visual stuff (and esp. animations and screen behaviours).

    Here's my method so far:

    • Functional requirements and Information architecture on FreeMind (or Visio if you prefer)
    • Wireframes and composites on Illustrator
    • "Assets Board" on Illustrator (All what you want to import: Brushes (Colours and gradients), icons, complex shapes)
    • Creation of images library (similar to web, with a pref for PNGs)
    • Creation of Resource dictionaries (like CSS): Styles (esp. for fonts), Templates, Brushes and images, etc.

    There is also the possibility to mock up a Proof of Concept or basic interactive mock up in Blend using Sketchflow. I'm not familiar with this but I heard it can be handy.

    Illustrator can be replaced by Photoshop of course, I just think Illustrator is closer to what you should have in mind when you create XAML: there are Graphic Styles and Symbols tools that can be taken as equivalent XAML assets. You then know better how you will organise your production.