Frameworks

Developers as Designers? It Needs to Happen

It's time to stop thinking of "design" as a dirty word, and UI as the sole domain of the folks at the other end of the cubicle farm.

Most developers I know aren't all that interested in style -- and I'm not just talking about in terms of dress. But the days of completely ignoring how your programs look, concentrating on nothing but function, are gone. It's time to stop thinking of "design" as a dirty word, and UI as the sole domain of the folks at the other end of the cubicle farm.

That's because we're in the era of Windows 8 and mobile computing. As displays get smaller and touchscreens proliferate, you no longer have the option of thinking only about arrays, for loops and refactoring -- in many ways, now, form is function. When I type on a tablet, I expect -- and need -- a different experience. You must keep that thought in mind as you do everything, even if you're mainly a coder.

Fortunately, Visual Studio 2012 is here to help. One of the best new features that produces maximum awesomeness is PowerPoint Storyboarding. Talk about a tool that helps you think visually. The integration with Visual Studio 2012 is remarkable. Even if you don't believe you have an ounce of artistic ability (and I don't), you can still do some amazing things with Storyboarding.

It has tons of built-in templates for things like screen backgrounds, and standard controls such as data grids, calendars and scrollbars -- even animations. It's perfect if you're a one- or two-developer shop, because you can create an attractive program without a design team. If you have a design team, it's even better, because the functionality and flexibility of PowerPoint can be leveraged within Visual Studio 2012 itself to birth a sensational UI/UX. In fact, PowerPoint Storyboarding might be enough reason on its own to justify the expense of the upgrade from Visual Studio 2008 or 2010.

About the Author

Keith Ward is the editor in chief of Visual Studio Magazine.

comments powered by Disqus

Reader Comments:

Thu, Aug 9, 2012 Joe Brinkman

If you think PowerPoint storyboarding is about making things look pretty, then you probably haven't used it. Storyboarding is about understanding your UI layout and functionality BEFORE you start coding. The great thing about PowerPoint Storyboarding is that you can start with a very low fidelity wireframe and then start adding details as you progress until you have a high-fidelity mock-up of the design. This is not about making things look pretty, but about making things useable and doing the design when the cost for changing the design is very low. If you are changing design after you have started coding then the cost of that change is exponentially higher. It is not something you do after the fact if you want a product that users will love.

Wed, Aug 8, 2012 cj

If you think managers were the only ones capable of creating power point hell, just wait till the developers get ahold of this. Death by Power Point comming to an application near you.

Wed, Aug 8, 2012 Jay Stratemeyer

I think that I'm doing just fine without "templates". that is such an evil word. Using tools such as developer express controls and good ol' win forms. I can stamp out some pretty neat stuff. And if i really want it to look good, use jquery UI or Jquery UI Mobile. I'm sorry but if its not broke, don't fix it. I can make shiny looking buggy software. Reminds me of a mythbusters episode, can you shine a turd. yes you can but it is still a turd if its not done right from the inside. i am for functionality and ease of use then comes the prettiness.

Tue, Aug 7, 2012

I'm all for making it easier (for a developer) to create attractive/compelling UI's since I don't have the luxury of having those roles separated at my workplace. Still, I can definately appreciate the difference between a professionally created design and a wanna-be hacker design, ya know?

Tue, Jul 31, 2012

Of course, there's much more to it. Most coders are terrible designers and vice versa. Once functionality is agreed upon, then collaboration between the two is necessary to get to the best UX. Don't expect coders to ever replace designers. I'm reminded of a saying: "Never try to teach a pig to sing. It wastes your time and annoys the pig." ...Unless of course the pig LIKES to sing! :)

Mon, Jul 23, 2012 Zakos

I'm sorry but NO! Design is A Develop is B A & B can not be the same person , why ? cuz its FAIL , u need to combine A & B for max results!

Tue, Jul 3, 2012 Carlos MX

Is very interesting this article to developers who start with early versions of windows, when everything was square, gray and we have a few of fonts and no styles, but in this times where everythig must be beautiful, shine and "innovative", some times forget that the first quality attribute it must be the functionality, so I just have one comment if a developer have to be a little designer, a designer could be a little developer ??

Wed, Jun 27, 2012 Walter Pretell

That's really going to the right direction.

Add Your Comments Now:

Your Name:(optional)
Your Email:(optional)
Your Location:(optional)
Comment:
Please type the letters/numbers you see above
Close this Advertisement