CHI-WEB Archives

ACM SIGCHI WWW Human Factors (Open Discussion)


Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Ash Donaldson <[log in to unmask]>
Reply To:
Mon, 30 Jun 2003 08:59:18 +1000
text/plain (37 lines)
Quoting "Batra, Sanjay" <[log in to unmask]>:
> - To make the UI behave more like a client server GUI that the end-users
> currently use for this application.
> Unfortunately, disabling all the browser functions (including right clicking)
> has a number of usability questions:


Indeed it has - and always will.  In my experience (porting many GUI apps to web apps), web
applications should not attempt to mirror client-server GUIs.

Browsers have many different 'design constraints' and 'features'.  If the app works well as a
GUI, keep it that way - don't port it to a web app because it seems to be the fashion.

If however, there is a business requirement to port your GUI app to a web app, (I have found
that) it is best to start from scratch - gather your requirements (including stakeholder
interviews), build personas, perform task analysis, etc, etc.  Engage the whole UCD process
properly and at the end of the project, you'll have a simpler and more friendly app that
requires less training.

The only problem with this approach is convincing the powers-that-be that all that work is
required.  Try scoping around for some disaster stories of GUIs ported to web apps and explain
the need to go through this process in terms they'll understand - ROI.

Best regards,

Ash Donaldson
User Experience Designer

           Tip of the Day: Postings must be in plain text
     CHI-WEB: POSTINGS: mailto:[log in to unmask]
              MODERATORS: mailto:[log in to unmask]