Don’t Make Me Think, Revisited a common Sense Approach to Web Usability Steve Krug

Not present at time of photo
Just so you don’t waste your time looking for them, here are a few things
you won’t find in this book:
Hard and fast usability rules.
I’ve been at this for a long time, long
enough to know that there is no one “right” answer to most usability
questions. Design is a complicated process and the real answer to most
of the questions people ask me is “It depends.” But I do think that
there are a few useful guiding principles it always helps to have in
mind, and those are what I’m trying to convey.
Predictions about the future of technology and the Web.
Honestly,
your guess is as good as mine. The only thing I’m sure of is that (a)
most of the predictions I hear are almost certainly wrong, and (b) the
things that will turn out to be important will come as a surprise, even
though in hindsight they’ll seem perfectly obvious.

---

Bad-mouthing of poorly designed sites and apps.
If you enjoy
people poking fun at things with obvious flaws, you’re reading the
wrong book. Designing, building, and maintaining a great Web site or
app isn’t easy. It’s like golf: a handful of ways to get the ball in the
hole, a million ways not to. Anyone who gets it even half right has my
admiration.
As a result, you’ll find that the examples I use tend to be from
excellent products with minor flaws. I think you can learn more from
looking at good designs than bad ones.
Now with Mobile!
One of the dilemmas I faced when updating this book was that it’s always
been a book about designing usable Web sites. Even though the principles
apply to the design of anything people have to interact with (including things
like election ballots and voting booths, and even PowerPoint presentations),
its focus was clearly on Web design, and all the examples were from Web
sites. Until recently, that’s what most people were working on.
But now there are a lot of people designing mobile apps, and even the people
working on Web sites have to create versions of them that work well on
mobile devices. I know they’re very interested in how all of this applies to
them.
So I did three things:
Included mobile examples wherever it made sense
Added a new chapter about some mobile-specific usability issues
And the most important one: Added “and Mobile” to the subtitle on
the cover
And as you’ll see, in some places where it made things clearer, instead of
“Web site” I’ve written “Web site or mobile app.” In most cases, though, I
used the Web-centric wording to keep things from getting cumbersome and
distracting.