Printable View
Hi,
We are developing a .NET based client application containing a number of controls and states.
We are unsure if we should go in for a menu based application or a dialog based one.
Are there any rules that help determine if an application should be menu based or pure dialog based ?
Consider the number/complexity of available commands/states and your own UI design preferences, then decide.
The main goal is to make the end users feel comfortable using the app. Better yet, if possible, go and give them [the end users (target audience)] some introduction and then ask them what they would prefer, then take that into consideration.
(It helps to familiarize with the way your target audience works, what workflow they use, what's important in the line of work, what they think is wrong with the existing software, what improvements could be made...)
Menus do invoke dialogs right?? Usually buttons and menus are given to do the same operations liek New, Edit, Delete. Menus are a good space saving technique as well.