Also, letâ€™s face it, anyone could drag and drop a control onto a design surface and the only modification from there was pretty much little things like background colour etc and no one really thought they needed a designer to do that.
But what about todays development practices?
The tools are now here, designers have thier tools and developers can use them as well - all outputting an understood syntax that .Net eats up. XAML.
Windows applications can finally be built along the same winning processes that game studios work with - a proven method of collaborative design and development.
What ever the reasons may be, there certainly is very little excuse to let it continue. The tools are now here, so I guess it is just the attitudes that need to change.
So what do you need to do?
Get an interactive designer and graphic designer involved in your development lifecycle (preferably one that has an understanding of WPF) even if it is just for a pilot. Work out the process of delivery of inception through implementation.
If itâ€™s done right, your application(s) will
Sound like good enough reasons to try it?
Yes I know what you are going to say nextâ€¦ â€œItâ€™s easier said then doneâ€ and you would be right, so the next few blog posts are going to be about how I go about implementing the process into development teams of any size.