Skip to main content

Usable Usability Across Virtual and Physical Spaces

Books on usability often focus on either software and web usability or usability in the physical world. In many cases services people use span the two. Physical objects often have a software component and many interactions span physical and virtual spaces. You need to consider usability not only in the context of the thing you are working on, but in the context of the system the person is interacting with. In other words, rather than thinking about the user experience for an application, it's worth thinking about the user experience for a service. Eric Reiss's book, Usable Usability: Simple Steps for Making Stuff Better provides you information to understand usability implications of web design, physical design, situations when the two intersect.

While any one book can't fully cover everything you need to know about usability across these spaces, Reiss does a great job job giving an overview of the issues, and pointers for more information Usable Usability: Simple Steps for Making Stuff Better reminds me of Donald Norman's Psychology of Everyday Things (newer editions being called The Design of Everyday Things).

The principles of good web design are not that different from good design of physical objects. There are many cases when a user experience spans the two; you may start a transaction online, ask for help on a phone call, and complete the transaction is a physical store.

This is a very readable, entertaining, book which weaves stories of his experiences with both bad and good usability, with actionable advice to help you understand both general principles of usability and specific guideline to employ when designing interfaces. The humorous stories of the effects of poor design will help you to remember what not to do, and the simplicity of the examples of good design will inspire you to aim higher in your projects. This book is especially worth a read if you are building
 software applications or services that have both a software and concrete component.


Popular posts from this blog

Continuous Integration of Python Code with Unit Tests and Maven

My main development language is Java, but I also some work in Python for deployment and related tools. Being a big fan of unit testing I write unit tests in Python using PyUnit. Being a big fan of Maven and Continuous Integration, I really want the  Python unit tests to run as part of the build. I wanted to have a solution that met the following criteria:
Used commonly available pluginsKeep the maven structure of test and src files in the appropriate directories.Have the tests run in the test phase and fail the build when the tests fail.
The simplest approach I came up with to do this was to use the Exec Maven Plugin by adding the following configuration to your (python) project's POM.

<plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <executions> <execution> <configuration> <executable>python</executable> <workingDirectory>src/test/python</workingDirect…

Displaying Build Numbers in Grails Apps

Being a fan of Continuous Delivery, identifiable builds, and Continuous Integration: I like to deploy web apps with a visible build number, or some other way of identifying the version. For example, having the build number on the login screen for example. In the Maven/Java world, this is straightforward. Or at least I know the idioms. I struggled with this a bit while working on a Grails app,  and wanted to share my solution. There may be other, better, solutions, but the ones I found approaches that didn't quite work they way that I'd hoped.

My requirements were:
To display a build number from my CI tool, where the number was passed in on the command line. In Bamboo, for example you might configure a grails build as
-Dbuild.number=${bamboo.buildNumber} warTo only change build artifacts and not any source files.To not misuse the app version, or change the names of any artifacts.To be simple and idiomatic.I realized that that Grails itself changes the application metadata (appl…

Motivation Visibility, and Unit Testing

I've always been interested in organizational patterns (such as those in Organizational Patterns of Agile Software Development). I've recently found myself thinking a lot about motivation. I'm now reading Drive: The Surprising Truth About What Motivates Us and just finished Rob Austin's book on performance measurement. Being the parent of a three year old, I'm finding more and more that "because I said so, and I'm right" isn't too effective at home. My interests in motivation are closely related to my interest in writing software effectively. Writing software is partially a technical problem about frameworks, coding, and the like, but the harder (and perhaps more interesting) problem is how to get a group of people working together towards a common goal. Agile practices, both technical and organizational, build a framework which makes having the right amount of collaboration and feedback possible. But there's a bootstrapping process: How do yo…