Changing topic: Do you need to explain system interaction in a web app? Example: The user's goal is to change a previuosly processed invoice. The first task to perform this task is to search to see whether someone has already updated this record. If the record has not yet been ammended, the user can proceed. So the user must enter search terms, then perform a query check. Then they can continue. Since the first task is to see if the payment can be ammended, would it make sense to describe the task, then tell the user the search shows no payments have been ammended so they can proceed? Seems like if you dont describe the action it isnt communicating the behind scenes.
. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=31923 ________________________________________________________________ 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
