Good Game GUI Design – What Do You Use?

June 10, 2009
Tags: ,

I’ve previously talk about creating a good game GUI design.  Today I’d like to hear from you.  I’m interested in what people are currently using to mock up their in-game GUI’s and what they would like to see from a product to help them.  Please add a comment to this blog, or email me directly with your thoughts.  Below are some specific questions:

  1. What do you currently use for mocking up your GUI designs?
  2. If there was a tool created specifically for mocking up game GUI’s, would you be interested in using it?
  3. What core features would you like to see to help you mock up your GUI’s?
Share:
  • Digg
  • Reddit
  • Facebook
  • del.icio.us
  • DZone
  • LinkedIn
  • email

Find Us On Facebook

Filed under:
Game Development by Doolwind

  • No Related Post
  • http://www.bleevo.com/ bleevo
  • Wes

    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.