Skip to main content

Don't Make Me Thing


Useful: Does it do something people need done?
Learnable: Can people figure out how to use it?
Memorable: Do they have to relearn it each time they use it?
Effective: Does it get the job done?
Efficient: Does it do it with a reasonable amount of time and effort?
Desirable: Do people want it?
and recently even
Delightful: Is using it enjoyable, or even fun?

Chapter 1. Don’t make me think!

KRUG’S FIRST LAW OF USABILITY

Michael, why are the drapes open?
—KAY CORLEONE IN THE GODFATHER, PART II

first law of usability.
“Nothing important should ever be more than
two clicks away” or “Speak the user’s language” or “Be consistent.”

Chapter 2. How we really use the Web

SCANNING, SATISFICING, AND MUDDLING THROUGH
Why are things always in the last place you look for them? Because you stop
looking when you find them!
—CHILDREN’S RIDDLE

FACT OF LIFE #1: We don’t read pages. We scan them.
FACT OF LIFE #2: We don’t make optimal choices. We
satisfice.
FACT OF LIFE #3: We don’t figure out how things work. We
muddle through.
If we find something that works, we stick to it.

Chapter 3. Billboard Design 101

DESIGNING FOR SCANNING, NOT READING
If you / Don’t know / Whose signs / These are You can’t have / Driven very far
/ Burma-Shave!


Chapter 4. Animal, Vegetable, or Mineral?

WHY USERS LIKE MINDLESS CHOICES
It doesn’t matter how many times I have to click, as long as each click is a
mindless, unambiguous choice.
—KRUG’S SECOND LAW OF USABILITY


Chapter 5. Omit needless words

THE ART OF NOT WRITING FOR THE WEB
Get rid of half the words on each page, then get rid of half of what’s left.
—KRUG’S THIRD LAW OF USABILITY

Instructions must die

Chapter 6. Street signs and Breadcrumbs

DESIGNING NAVIGATION
And you may find yourself | in a beautiful house | with a beautiful wife And
you may ask yourself | Well... | How did I get here?!
—TALKING HEADS, “ONCE IN A LIFETIME”


Chapter 8. “The Farmer and the Cowman Should
Be Friends”

WHY MOST ARGUMENTS ABOUT USABILITY ARE A WASTE OF
TIME, AND HOW TO AVOID THEM
One man likes to push a plough The other likes to chase a cow But that’s no
reason why they can’t be friends!
—OKLAHOMA!, OSCAR HAMMERSTEIN II

The antidote for religious debates
The point is, it’s not productive to ask questions like “Do most people like
pull-down menus?” The right kind of question to ask is “Does this pull-down,
with these items and this wording in this context on this page create a good
experience for most people who are likely to use this site?”
















Comments

Post a Comment

Popular posts from this blog

Access multiple Databases in JPA

According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl {     @PersistenceContext(unitName="PolarPU")     protected EntityManager entityManager; -- } public class BearDaoImpl {     @PersistenceContext(unitName="BearPU")     protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">     <!-- Database 1 -->     <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL">         <
3 comments
Read more

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co
21 comments
Read more

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc
11 comments
Read more