This is a second attempt at articulating this issue, and was inspired by a conversation with @psd who also pointed me at a TEDx talk entitled A time traveller’s primer. The first attempt is here.

It took 4 or 5 years of ajax / XMLHTTP being a thing for it to change almost everything about the sort of things that were built on the web. That was 4 or 5 years when lots of amazing things didn’t get built, not because it wasn’t possible, but because people just, didn’t. There were probably lots of transient reasons - browser support, users might not understand it yet, hard justifying it to co-workers, lack of examples - but fundamentally, there was lots of potential that was not realised until later in time. When that potentual was finally realised everything that went before suddenly felt dated.

This is faster than the 700 year example of pasteurisation that Ryan North gives in his TEDx talk A Time Traveller’s Primer (and yes, ajax is significantly less significant than pasteurisation) but the principle is the same:

If you want to design for the future, look for unrealised but present potential, look for what people could be making right now but are not. Design what is lacking.

The web is going though an Ajax moment right now, and it is happening (or rather has the potentual to) for 2 reasons:

1. The things browsers can do The web browser on your phone has access to sensors, outputs and offline storage to make proper contextual design a reality. It can:

• capture a screen
• check if a tab has been backgrounded
• check the battery
• check orientation of the device in 3 dimensions
• check and lock the orientation of the screen
• detect the pitch of a sound
• listen to you
• record video and audio
• respond to ambient light
• share all or part of your screen
• show notifications
• talk to you
• talk, type or video conference someone
• use your camera
• vibrate
• work offline Most of those won’t work if you try them on a laptop browser, but they will on your phone or tablet if you use chrome or firefox. This is partly the point, the technology is here, but not in the tools that we use to design things for the web (laptop browsers), but is in the place where users are spending more time.

Designing in a laptop web browser and testing with a mouse rather than fingers may come to look very out of date soon.

1. Stable mobile design patterns The 7 years of the Apple App Store and the android equivalents have, in effect, been mass, micro funded experiments in UI design for small, touch sensitive devices with lots of sensors and outputs. They have generated winning patterns like:

• Checkboxes replaced by switches
• Check-ins
• Edit without save button
• Everything can be contextual, any bit of UI can disappear between pages
• Everything has it’s own settings page
• Floating buttons
• Keeping primary navigation off canvas (hidden behind the page)
• Minimal or zero page header (the context an old school page header / nav gives seems less important when you are holding the app in your hand.)
• Multiple, focused apps for the same service
• Offline by default
• Overscroll to refresh
• Reserving dropdown menus for actions on the current context
• Search scoped to their current context (the app) These are patterns that people use day in day out on facebook, Gmail and WhatsApp. These are the new normal, what people expect.

But with a few notable exceptions - eg the mobile versions of Wikipedia and Forecast - these are not patterns that are making their way on to the web.

So, here is the challenge for anyone designing and building for the web in 2015. There are a set of technologies and design patterns that are here, right now, not experiments in an innovation lab, but things you can use to design better tools for people. Today.

At some point in the next few years, some of these will become as widespread on the web as ajax and responsive design, so why wait 5 years? Design what is lacking.