UI Best Practices
Posted: Sat Sep 08, 2007 5:38 pm
Reading through forums and reviews, it is not uncommon to see very positive comments about many of the Matrix games, but then some criticisms of UI. As Matrix works with a lot of independent developers who do not have significant resources to devote to advanced UI design and testing, I wonder if it might make sense for Matrix to compile some UI best practices as a "cheat sheet" for their developers. In addition to providing some hopefully helpful hints, it might tend to make the UI across titles more consistent, which seems like it would benefit both Matrix and the its user community.
Even very simple things like a standard reference source for NATO symbols would be helpful. Standard color usage in info windows or on counters would be nice. And more consistent usage of right and left mouse clicks and especially common keyboard shortcuts would be great. Naturally, following the advice would be completely optional. Projects based on an existing board game would likely choose to be faithful to elements that were present in the original game. And we wouldn't want to impose a UI straight jacket as we'd like to see continuing evolution and improvement of interfaces. But hopefully some consistent high-level best practices would prove useful enough to gain acceptance over time and would reduce the number of reviews we're reading about clumbsy and difficult interfaces.
Even very simple things like a standard reference source for NATO symbols would be helpful. Standard color usage in info windows or on counters would be nice. And more consistent usage of right and left mouse clicks and especially common keyboard shortcuts would be great. Naturally, following the advice would be completely optional. Projects based on an existing board game would likely choose to be faithful to elements that were present in the original game. And we wouldn't want to impose a UI straight jacket as we'd like to see continuing evolution and improvement of interfaces. But hopefully some consistent high-level best practices would prove useful enough to gain acceptance over time and would reduce the number of reviews we're reading about clumbsy and difficult interfaces.