Hi Amihay I'm of the opinion that if I find myself having to write copy for a UI there's room for improvement with the design of the UI itself. Many make the argument that the best UI is >blank< i.e. the system just 'does'. While thats an ideal, its fair to say the inverse of this is an overly copy laden interface.
To that end, a small amount of root cause analysis cant hurt.. why am I writing copy? why does the UI need inline help? why does the architecture mandate that UI structure? etc etc... While you might not be able to fix everything, you might be able to find room for improvement.. reduce the copy and increase flow. regards - pauric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=30365 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
