Tag Archives: app

DR Codes

This is a thought that’d been rattling around in my head for a few years, which I want to try and crack this year.

Each agency I’ve worked in, there has been some form of tea making culture. Every day, at varying times during the day, someone will offer to make a brew.
Small teams of good friends know how to make each others drinks, but larger teams struggle to remember, and if you’re offering to make a large round, you have to remember quite a few permutations of the basic bases: Drink Type, Sugar Count, Strength/Milk Ratio, Foam, Steep Time, and so on.

At de-construct, we had a number of solutions to remind brewers how the team liked their drink. These were pieces of beautiful design which presented the instructions to make the drink in a graphical format, printed as a large poster in the kitchen area. The first one, I think was done by Alex Griffin, mostly in response to me accidentally putting salt in a cup of tea instead of sugar (they look the same, it wasn’t my fault).

There are so many combinations though, and people change their desires frequently – I’m drinking more tea than I used to for instance, and some times I need sugar, other times I don’t. If you’re making me coffee though, its simple – freshly ground black filter coffee please.

So posters only work so far, and don’t solve the problem of remember who wanted a drink either.
How often have you scribbled down some hieroglyphs like MK: T2S, SB: C1SB, KL: C2 to keep track of who asked for what?

So the idea of a DR code came to me a few years back when looking to create a new poster for a space: A graphical marker which explains how someone wants their drink, that can be read by both humans and machines. A QR code for drinks.

A human looking at the code could easily see the drink’s make up: drink type, sugars, milk, etc. A computer could read even more information, and build that into applications. A mobile app could easily capture what drinks people wanted, and who wanted them – perhaps the DR codes are stored against the address book entry, and the app logs the ratio of making the drink to receiving the drink (to catch out people who never step up to the kettle), and that data could be aggregated to show the consumption habits of a business, and improve stock ordering accordingly.

So I’ve started work on creating the code itself, a human and machine readable visual device which holds information on a drink’s make up.

There are TR Codes (Tea Requirement codes) and CR Codes (Coffee Requirement) so far, and I’m still tweaking the meanings (for instance, subtleties between ristrettos and espressos, or milk/foam ratios for drinks like a latte vs a capp’).

There’s potentially colour to explore too, to expand the drink types. I’m pretty sure it could extend to drinks beyond the office, cocktails for instance might work based upon ratios.

Once the DR Code works, I’ll look at how we can use some simple Javascript to recognise the icon, and act upon it in some way.
I’d also love to look at non square / non digital looking versions, using perhaps pie chart type visuals and colour.

There are bunch of references which have influenced this so far:
The work Mat and I did on CLARITY*
The espresso field guide (and versions of that)
Tea over IP