Having said that good design and bad design; No body pre-dominantly like do a design which is good or bad. Over a period of time people did their design chores knowingly or unknowingly at the given time and space of requirements with their so called class room expertise or by their domain expertise.
I would like to put this way of the GUI Evaluation in a funny way:
• Developers who vissioned the GUI themselves were the designers.
• Creative people peeked in to see, how they can maneuver the GUI and add value in terms of aesthetics.
• Forums evolved: where developers wannabe and designers wannabe debated and asked too many questions to settle for their career.
• Clients / Half baked who wanted good returns, by mixing a domain of all the above mentioned three categories.
Nice logic indeed in a business perspective. But really it is not that simple of a GUI development.
The need for the GUI comes in first place arises only when something needs to be automated, make it easily operable and eliminate traditional hassles. Given the scenario the R&D has its own sweet time
which do a evaluation and gives a workflow which again by passes the awesome 4 some points which we discussed earlier. Then only the actual development starts.
Having done all the homework and started developing a GUI and ended in nightmare is punishable at the maximum possible.
Let’s see how the end user marked them good and bad.
More to come…
