There is an opportunity to take ideas from desktop applications and apply then to the web. All user interface design is information visualization. We can blur the distinction between dynamic content and transactions. In designing desktop UI in the ’90s, it was wonderful to see context-sensitive panels and toolbars gradually replace the modal dialog. Why make the user ask a question when we can provide the answer? Some of today’s web sites are already applying this principle in creating dynamic data-driven sites.

I’m not convinced that today’s desktop applications are the best we can do in terms of user experience, nor do I believe that most web applications benefit from the same designs that work well on the desktop. We can borrow ideas and design principles, but the graphical user interface elements and layout don’t always translate well. Most desktop apps were created to let you create and modify documents: word processor, spreadsheet, graphic design tools, etc. Most web apps let you ask questions, find information and perform transactions.

Unlike a desktop app, a web site is a place. I find this metaphor of travel oddly intuitive. It takes time to go from one place to another in real life, so it feels okay to wait when you ‘go’ to another page on the web. We design multiple web pages with a consistent design and user interface elements to create the illusion that a web site, these multiple pages, are a single place. Nevertheless as you troll for information or finalize a transaction, a conversation takes place. You ask questions, fill out forms, click links, and the landscape changes. It’s a completely different experience than the one you have on your solitary desktop, and provides fertile ground for innovative design.

4 thoughts on “beyond desktop ui

  1. Fun with metaphors:
    Another metaphor for the desktop apps. The desktop apps are similar to a workshop. We have tools in the workshop. We work with them to produce an object. The object on the desktop is the file we save. It takes time to learn the skill of using the tools in the workshop. Similarly we learn desktop apps and put them on our resume.

    Searching for a new metaphor for the new interfaces? Playing a game, Shopping, Learning, etc. Lots of different types of metaphors can be listed.

    Amazon uses the learning UI to make people shop. Learning involves asking questions and finding out answers. Amazon asks simple questions about their products and gives people a dime for answering it.

    Thw classic typing tutor game uses the game metaphor to teach typing. Letters fall from the top and the player tries to type as fast as possibe to win.

    I don’t know of any game which uses the shopping metaphor, but maybe the next sims game will be to shop for the best product by sifiting through lots of object properties.

    Enough fun for today :)

  2. Hm. A “web site” is a “site”, in other words, a “place”. Is a “web site” an application like word.exe? Is Word a place? It certainly seems like a labyrinth, and that’s why I think a lot of web and traditional GUI designers have a distaste apps like Word.

    Too much complexity. Even Larry Ellison said so.

    But we live in transitional times. There are traditional CNN-like static sites and there are semi-dynamic sites like blogs. Then there are sites which look a lot like desktop apps. I work at an email marketing company (some call it “spamming”, which in most cases is not entirely accurate but anyway…) which allows marketing materials to be developed via the web, including the html content.

    The back-and-forth nature of form-based web apps is extremely painful for complex tasks. It’s interesting how most web designers and implementers turn a complex task into a multi-stage workflow-like process with lots of little transactions all maintained on the server, and (usually) all persistent. We’re all familiar with losing our work when word.exe crashes. This just doesn’t happen on the web, typically.

    This fascet of web-based applications is more the result of the limitations of standard web browser capabilities than intentional design. For example, you tend to see traditional long-lasting transactions with Java applets (not many sites actually employ applets for several reasons, the main one being the lack of decent Java support in IE, but there are others — complexity, clunkyness, and slow downloads), because applets have comparable functionality of traditional desktop applications.

    Do complex tasks require a complex interface?

    Is the workflow mini-transaction metaphor preferable to a canvas-style metahor?

    The workflow metaphor actually appeared on the desktop as “wizards” well before web browsers were mainstream. Wizards are for beginners. Because the web is still relatively new, most users are beginners and need a wizard-like interface. Most web applications still don’t address the power user.

    And we’re all quite aware that most desktop apps are made for power users first and begineers second.

    However, I think that complex tasks could benefit from “complex” interfaces which are sufficiently crafted for the task at hand. For example, I think FrontPage, if you’ve used it, is a heck of a lot better than the crapola edit box that your blogging software provides. I think that FrontPage is intuitive for the most part, especially in Office 2003.

    But anyway, it seems to me that some web sites are becoming like desktop apps with toolbars and menus, and some desktop apps are becoming like web sites, with hypertext links, animated gifs, and wizards. So in that sense we are living in transitional times.

    I don’t think Flash is the answer, but I do think that its competition, SVG, will have an impact in two areas:

    1. Advertising
    2. Complex tasks involving creativity

    But SVG is not for the masses. Simple requirements like a home page, a catalog, and a shopping cart are well served by HTML.

    More complex tasks like constructing a flowchart require a coarse-grained usage model. By coarse grained, I mean that the web application sucks down a large XML document, uses a complex GUI to manipulate it, and posts the XML document back to the server. The get and commit transactions occur via web services. But newbies need wizards for even these types of tasks.

    Thanks for the interesting content.

  3. Well described
    and quite serious without getting overindulgent like some others I have come
    across, but I am still a little bit confused but that is ok, as I was very
    entertained and that means a lot to me. Thanks so very much for the inspiration.
    I can only hope I take away 5% of the creativity I have seen and can apply
    it to my own blog. I like you to see my favorite dance
    which I am trying to match in terms of design and esthetics.
    It is so good that will be difficult but mine does come loaded with many pictures
    of dance people
    . Maybe I do good too? I am big on dance and hope you
    appreciate as much as I do. If you can please comment and make suggestions
    how to improve.
    I will do the same to you. Much success and admiration to all lovely internet

  4. Pingback: #2: Blogging is a Technical Skill | The Tectonic Podcast

Leave a reply

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>