Practices
  Home arrow Practices arrow Page 4 - A User-Friend Interface: The DOs and DO NOTs of UI Design
Dev Shed Forums  
Administration  
AJAX  
Apache  
BrainDump  
DHTML  
Flash  
Java  
JavaScript  
Multimedia  
MySQL  
Oracle  
Perl  
PHP  
Practices  
Python  
Reviews  
Security  
Smartphone Development  
Style-Sheets  
Web Services  
XML  
Zend  
Zope  
Mobile Linux  
App Generation ROI  
IBM® developerWorks  
Forums Sitemap  
E-Commerce Hosting  
Linux Web Hosting  
Managed Hosting  
Small Business Hosting  
VPS Hosting  
Weekly Newsletter

 
Developer Updates  
Free Website Content 
 RSS  Articles
 RSS  Forums
 RSS  All Feeds
Write For Us Get Paid  
Request Media Kit
Contact Us  
Site Map  
Privacy Policy  
Support  
 USERNAME
 
 PASSWORD
 
 
  >>> SIGN UP!  
  Lost Password? 
Google.com  
PRACTICES

A User-Friend Interface: The DOs and DO NOTs of UI Design
By: Justin Cook
  • Search For More Articles!
  • Disclaimer
  • Author Terms
  • Rating: starstarstarstarstar / 61
    2004-04-19


    Table of Contents:
  • A User-Friend Interface: The DOs and DO NOTs of UI Design
  • Guideline #1
  • Lost in Space
  • We Need Textual Healing

  • Rate this Article: Poor Best 
      ADD THIS ARTICLE TO:
      error-file:tidyout.log Del.ici.ous error-file:tidyout.log Digg
      error-file:tidyout.log Blink error-file:tidyout.log Simpy
      error-file:tidyout.log Google error-file:tidyout.log Spurl
      error-file:tidyout.log Y! MyWeb error-file:tidyout.log Furl
    Email Me Similar Content When Posted
    Add Developer Shed Article Feed To Your Site
    Email Article To Friend
    Print Version Of Article
    PDF Version Of Article

     
     
    ADVERTISEMENT


    A User-Friend Interface: The DOs and DO NOTs of UI Design - We Need Textual Healing
    ( Page 4 of 4 )

    The guidelines around decorating kind of lead nicely to an understanding of how to treat text. Do not clutter! Learning a "for" loop in server-side programming is the only time we should use 10 different font sizes! Fight that tendency to use h1 through to h5!

    To accomplish this, we should set some standards for ourselves at the outset. In our stylesheet, define the body font size, maybe redefine h1 (and maybe h2 if critical), and then perhaps a smaller font for footer and photo captions. Then leave it at that. If at all possible, keep them all the same color, and make sure it's a nicely contrasting color with the background you've chosen.

    Don't forget though, that more important than the look of the text is the actual content itself. We should be writing the content around the users. This will aid in both search engine positioning, and in users actually understanding what the heck is going on! Always explain things in plain English (or your language of choice, just keep it plain). Remember, most of your users are not programmers, so they don't all understand geek-talk. This is a good thing! I mean, think about it, if they were all programmers, we'd be out of work!

    One last guideline around avoiding text clutter, is just to omit needless text. For example, take the sentence "if you want to see pictures of the vacation we took in Timbuktu, click here to proceed to the photo album," and shorten it too "here are some pictures of our Timbuktu vacation." Feels as refreshing as a nice haircut, doesn't it!

    I read some research done by one firm, and they found that the pages with the highest retention rate never exceeded 600 words of content. Keep that in mind!

    Conclusion

    This is not necessarily an exhaustive list of to-do's in website design and usability. These are however, a list of some of the more common mistakes people make. This is especially the case when the programmer is given the additional responsibility of doing the UI design.

    Remember, these are tried and true, and you will reap the rewards of a user-friendly website if you implement them! No salmonella here, just people begging for the recipe!



     
     
    >>> More Practices Articles          >>> More By Justin Cook
     

       

    PRACTICES ARTICLES

    - More Techniques for Finding Things
    - Finding Things
    - Finishing the System`s Outlines
    - The System in So Many Words
    - Basic Data Types and Calculations
    - What`s the Address? Pointers
    - Design with ArgoUML
    - Pragmatic Guidelines: Diagrams That Work
    - Five-Step UML: OOAD for Short Attention Span...
    - Five-Step UML: OOAD for Short Attention Span...
    - Introducing UML: Object-Oriented Analysis an...
    - Class and Object Diagrams
    - Class Relationships
    - Classes
    - Basic Ideas





    © 2003-2009 by Developer Shed. All rights reserved. DS Cluster 4 Hosted by Hostway
    For more Enterprise Application Development news, visit eWeek