Skip to main content

The Point of No Back Button

My endless trek across the once-barren, now-lush lands of the interwebs have brought me to this point. I realized it just this moment. The feeling sank in my gut, chewed holes at every web usability study I've read, and screamed at my very world view: I don't use the back button. Ever.

Does it surprise you? It surprised me, for a moment.

What does your browsing experience look like? If you're like myself and a growing number of the web surfing public, you've probably hung up your surf board by now. Actually manually browsing around websites is boring, time consuming, and just gosh-darn unproductive in todays where-the-hell-is-Noah flood of information. The ark hasn't been built yet, but we make do, for now, with our dingy-scale feed readers. Heck, Google Reader even comes with an oar!

So as I browse down a single, long list of new gumdrops to read this day, a lot comes up I might want to look into further. Maybe I want to comment, follow up on some links, or just abuse the Firefox browser's tab functionality as a reading queue. A huge heaping majority (I'll guesstimate 95%) of the actual web pages I open actually have their back buttons disabled, because they have nowhere to go back to.

Now, exceptions are abound in the world of software (the monkeys in the audience will laugh in a muttered way and get a depressed feeling of omg-im-a-geek). Yes, I do use the back button. I use it quite rarely and I think the majority of the cases where I actually use it can be attributed to poor and annoying website design. A recent example case would be download links for GIMP for Windows taking me to the annoying SourceForge download pages, and not the file itself. I only used the back button to return to the Win-GIMP website to download the next file. So, if we attribute all the cases where I do but shouldn't have to use the back button, I might guesstimate even 99% of the tabs I have open never get their back buttons exercised.

I understand this is not the norm, but neither are the blog and feed devouring web lovers of the world, yet. Most of the information digesting public do tend to remain on the roaming plains of the network. Their numbers are dwindling, I suspect, in ratio to our own numbers. (Does anyone have numbers about this?)


Paul said…
I use the "Back" button all the time, but then I've been using the Web since around 1993/1994. It wouldn't surprise me if many people hardly ever use it, but it's still probably impossible to navigate effectively without it, and alternative browsing tools such as navigation history trees arguably provide a more intuitive interface that might be more useful even to people who shun the "Back" button. So, I don't think such things are obsolete by any means.
Michael Foord said…
I use the back button quite a lot as well. Often I just want to quickly glance at a page that is linked to, so rather than open it in a new tab I use the link followed by the back button...

Popular posts from this blog

CARDIAC: The Cardboard Computer

I am just so excited about this. CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer.  One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC? It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on

Statement Functions

At a small suggestion in #python, I wrote up a simple module that allows the use of many python statements in places requiring statements. This post serves as the announcement and documentation. You can find the release here . The pattern is the statement's keyword appended with a single underscore, so the first, of course, is print_. The example writes 'some+text' to an IOString for a URL query string. This mostly follows what it seems the print function will be in py3k. print_("some", "text", outfile=query_iostring, sep="+", end="") An obvious second choice was to wrap if statements. They take a condition value, and expect a truth value or callback an an optional else value or callback. Values and callbacks are named if_true, cb_true, if_false, and cb_false. if_(raw_input("Continue?")=="Y", cb_true=play_game, cb_false=quit) Of course, often your else might be an error case, so raising an exception could be u

How To use Sphinx Autodoc on ReadTheDocs with a Django application

Sphinx is awesome for writing documentation. ReadTheDocs is awesome for hosting it. Autodocs are great for covering your entire API easily. Django is a great framework that makes my job easier. Between these four things is an interaction that only brought me pain, however. I'm here to help the next dev avoid this. Autodocs works by importing your modules and walking over the classes and functions to build documentation out of the existing docstrings. It can be used to generate complete API docs quickly and keep them in sync with the libraries existing docstrings, so you won't get conflicts between your docs and your code. Fantastic. This creates a problem when used with Django applications, where many things cannot be imported unless a valid settings module can be found. This can prevent a hurdle in some situations, and requires a little boilerplate to get working properly with Sphinx. It require a little extra to get working on ReadTheDocs. What makes this particularly h