W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > October to December 1997

conservation of complexity in UI?

From: Jim Davis <jdavis@parc.xerox.com>
Date: Fri, 24 Oct 1997 08:38:33 PDT
Message-Id: <3.0.3.32.19971024083833.0096aaa0@mailback.parc.xerox.com>
To: Paul Leach <paulle@microsoft.com>, w3c-dist-auth@w3.org, "'Larry Masinter'" <masinter@parc.xerox.com>
At 07:04 PM 10/23/97 PDT, Paul Leach wrote:
>If you can show me at least one UI design that hides this complexity,
>I'll buy it. Until then, it will be true that I've never seen a UI that
>can make anything simpler than the underlying intrinsic complexity --
>it's the law of conservation of complexity.

I can name two right off the top of my head.

Numerous Windows applications provide means to set properties and defaults
for the application.   Aren't these stored in the Windows Registry?  I
consider that complex.  Certainly the interface abstraction is simpler, if
by nothing else than hiding much detail.

The Z39.50 search protocol is a nightmare of complexity but most search UIs
by contrast are simple.  One way they gain simplicity is by providing a
higher level abstraction.  You will the form, it displays the results.  The
other is by hiding  rarely used but powerful features, e.g. Boolean
operations.  These confuse naive users.  The really good UIs have
progressive disclosure, so that if you actually need the advanced features
you can get to them, bit by bit.

In my opinion you won't be able to resolve the debate on access control
models by appeal to complexity baffling users.   There are doubtless other
reasons 

We'll find them.
Jim


------------------------------------
http://www.parc.xerox.com/jdavis/
650-812-4301
Received on Friday, 24 October 1997 15:02:46 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:43:44 GMT