Comments on: Good Game GUI Design – What Do You Use? http://www.doolwind.com/blog/good-game-gui-design-what-do-you-use/ Pragmatic Thoughts On Game Development Thu, 29 Jul 2010 11:00:29 +0000 hourly 1 http://wordpress.org/?v=3.0 By: Wes http://www.doolwind.com/blog/good-game-gui-design-what-do-you-use/comment-page-1/#comment-686 Wes Wed, 17 Jun 2009 10:45:49 +0000 http://www.doolwind.com/blog/?p=109#comment-686 A lot of the time I still use photoshop or some other graphical tool for a mock up, or good old pen and paper. That is, strictly speaking for a "mock up" and not a prototype. I consider a prototype to be functional on some level. When targeting games specifically I think one of the biggest problems is that quite a few games have non-standard GUI elements, either via layout or controls - whether this is a good thing or not is wholly debatable. Some non-standard GUI elements will be good examples of lateral thinking, others will be tragic examples of oversight. I think a problem with a mock up tool targeted at games is going to be related to this. How to give the designer the ability to innovate without going too far left of the field? With regards to your previous article, I'd agree, that too many interface elements results in confusion. Another problem is friction. Poor positioning of those elements can result in a sore wrist/fingers/arms and head. :P I think for the first iteration of such a tool some good features would be: 1.) The standard GUI elements. Buttons, Windows, Drop down lists etc. 2.) Some support for context sensitive controls. Though this could be quite a troublesome one. Many of these elements could be basic shell items with minimal functionality etc. In fact, for a strict "mock up" program, many of the elements could be generalized to basic shapes with parent/child relationships. This would allow the tool to target speed and allow quick iteration. Generally, a mock up tool should be fast, easy to use and lite on the details. A lot of the time I still use photoshop or some other graphical tool for a mock up, or good old pen and paper. That is, strictly speaking for a “mock up” and not a prototype. I consider a prototype to be functional on some level. When targeting games specifically I think one of the biggest problems is that quite a few games have non-standard GUI elements, either via layout or controls – whether this is a good thing or not is wholly debatable. Some non-standard GUI elements will be good examples of lateral thinking, others will be tragic examples of oversight. I think a problem with a mock up tool targeted at games is going to be related to this. How to give the designer the ability to innovate without going too far left of the field?

With regards to your previous article, I’d agree, that too many interface elements results in confusion. Another problem is friction. Poor positioning of those elements can result in a sore wrist/fingers/arms and head. :P

I think for the first iteration of such a tool some good features would be:

1.) The standard GUI elements. Buttons, Windows, Drop down lists etc.
2.) Some support for context sensitive controls. Though this could be quite a troublesome one.

Many of these elements could be basic shell items with minimal functionality etc. In fact, for a strict “mock up” program, many of the elements could be generalized to basic shapes with parent/child relationships. This would allow the tool to target speed and allow quick iteration. Generally, a mock up tool should be fast, easy to use and lite on the details.

]]> By: bleevo http://www.doolwind.com/blog/good-game-gui-design-what-do-you-use/comment-page-1/#comment-685 bleevo Wed, 10 Jun 2009 23:08:52 +0000 http://www.doolwind.com/blog/?p=109#comment-685 http://www.balsamiq.com/ http://www.balsamiq.com/

]]>