Designing inside the browser

I picked this up on garrettc’s delicious (always a good source of interesting and useful stuff to read, thanks Garrett) and found it very interesting. It’s Andy Clarke’s presentation from @media 2009, Walls ComeTumbling Down.

He suggests that one way to combat the ‘hard times’ we’re in is to reduce the web design cycle by designing in the browser rather than producing flat designs then coding them up. It’s a nice idea and I think it could be particularly appropriate for short cycle, agile style projects – the design part of such projects we’ve been trying still seems a bit waterfall-y at the moment. It’s definitely one for discussion.

The post is also noteworthy for the excellent way Andy presents each slide with a transcript of what he was saying. It must have been hard work to put together but it works really well for the reader – better than trying to juggle video/audio and slideshare.

http://forabeautifulweb.com/blog/about/walls_come_tumbling_down_presentation_slides_and_transcript

On web engineering

This post has been growling away at me for a while now. I turned another year older today and that’s spurred me on to finally get my old man of web development rant out into the wild.

When I studied Computer Science years back, we’d repeatedly have the message that some high percentage of software development work (there wasn’t really much web development per se back then) would be code maintenance and changes. So not building cool new ground breaking stuff but fixing problems and making changes to code which could be your own, could be someone else’s, could be beautifully crafted or could be – likely as not – a complete dogs dinner. I don’t remember what that percentage was but it was high – 80 maybe?

Things have changed an awful lot since then of course. Now, with back and front-end frameworks of every variety, we can have an idea for an app, and get it up on the web where it can be accesed worldwide within hours. With this ease, there’s less cost and less risk with trying out new stuff so the pace of change is fast.

But arguably, the ability to work with what’s there is as important as ever. As ideas for features or improvements come through for the apps and sites which have taken off, developers need to be able to open the project, find and understand the code and get the change done. It’s engineering, pure and simple. [Stretched, clichéd metaphor alert] If I took my car to the garage because it was leaking oil and the mechanic told me they didn’t understand how the engine worked so they’d ripped it out and put a new one in and that had taken 6 hours and here’s the invoice, I’d be pretty narked. But some developers will do just that when they don’t get how an object works or feel that their way of doing it is better.

I’m not suggesting that we shouldn’t refactor, improve, optimise and bring new techniques into our code, but the ability to read, understand and work with what’s already there remains as important today as it was when the term software engineering was coined several decades ago.

That’s it, I’ll get my aged anorak.

UXLondon

I started my week at a three day user experience conference called UXLondon organised by the nice people over at Clearleft. What an inspirational few days.

Monday was a whole set of keynotes from some of the big names in user experience – the rock stars if you will. Eric Reiss from fatDUX (and author of one of the books that got me started in this stuff) talked about e-service (sometimes called service design) – thinking about all the touch points between an organisation and customers, not just websites. Luke Wroblewski brought some architectural thinking to interaction design projects in his talk titled Parti and the Design Sandwich. Dan Saffer made us think about how behaviour and function should drive the design of products and services rather than getting hooked up on form or mechanics (how often do we think/hear “we should build an ajax site for this”?). Jared Spool entertained after lunch with his take on making things intuitive, Jeffrey Veen shared insights from his work on the information design for Google Analytics and (the) Don Norman wrapped things up by reviewing the day and arguing how complexity is a good thing.

Then we had two days of smaller, more practical focused workshops. I spent Tuesday morning in Donna Spencer’s session on Information Architecture. Billed as “No filler, no fluff, just pure IA”, it was just that. For me it was helpful in reassuring me that we’d been doing some of the right things (e.g. card sorting) but that we need to think a little more holistically. For example, you can’t just take the results of a card sort and build a site structure from it, it’s a tool to help you think about tricky parts of a site or get some initial ideas. In the afternoon, I stayed with Donna for a session called Designing for People. Again a fairly introductory session, for me this reinforced some of the things I learnt about people in HCI modules of my computer science degree and put them in the context of the web (which barely existed when I studied them the first time around). So we learnt to think about and leverage things like human memory and visual attention in the web design and development work which we do day-to-day.

Wednesday morning saw me plumping at the last minute for a session on sketching. Not something I’d have normally picked, but I’d heard such good things from those who’d attended it the day before that I decided to give it a go. The session was called Quick Sketching for Interaction Design and was run by two really nice chaps called Mark Baskinger and William Bardel. They took us back to basics with pencil and paper sketching. We drew lines, we drew squares, we drew circles, we added perspective, then we drew arrows. We brought these things together to illustrate problems and sketch process flows and design ideas to address them. My drawing was terrible – it was  pretty embarrassing having my squares corrected in red by NatBat – but I’m going to buy a sketch book and test Mark’s assertion that we can all get better with practice. The session concluded with a group sketching exercise where we explained the many pains of laundering a duvet visually (where are the pictures, Al? Not good enough for your portfolio?!). The chaps are working on a book on sketching and I’m definitely going to keep an eye out for that one coming out.

Finally on Wednesday afternoon I went along to Leisa Reichelt’s session on design research. Leisa discussed the range of techniques which can be used to bring users into the design process and focused particularly on user interviewing. For me this was great as it’s something we’ve been trying out at White October to try to get useful user insights for little cost. It was reassuring to see that the process I’d pretty much made up for interviewing was close to that which Leisa has been practicing for ages.  I wish she’d had more time to go through the analysis side of things, but I’ve got some good pointers of what to think about and where to learn more. Leisa is a prolific live tweeter and the dumps of her tweets on her blog give some good insight into the various sessions she made it along to – well worth a scan through.

Other sessions I would like to have made it along to include Richard Rutter and James Box’s session on wireframing. I heard good stuff from developer-y folks who went along to that to learn how Clearleft use jquery and other tools to produce rapid prototypes for demonstration, discussion and testing.

Just a quick story which I think sums up my overall feelings for the event. At the beginning of Leisa’s session, she asked us to introduce and tag ourselves BarCamp style (no mean feat with 30-40 people in the workshop). The most common tag by far was ‘inspired’. We were nearing the end of a packed three days so the fact that so many were inspired rather than tired has got to be good news for the attendees, the speakers and Clearleft alike. I met lots of friendly, interesting and helpful people and learnt so much so a big thanks to all those involved. The UK UX scene is really picking up now and it’s an exciting time.

Great work for charidee

Several of us are involved in charities / community projects of one kind or another. I’m a member of Camel Community Supported Agriculture (CSA).

CSA is about building a mutual relationship between food growers and food consumers so that the risks and responsibilities of food production are shared. There’s loads more info on this on the soil association site.

I joined the group because I’m a bit of a right on eco worrier, because I quite enjoy planting stuff and because I like eating tasty locally grown produce. Perhaps inevitably, I also volunteered to help with the techy side of the website. That meant getting Wordpress up and running so that they quickly had a web presence and then working on a customised template for them so that it looked good. White October have also kindly donated the small amount of hosting space required to host the site (thanks Dave).

A bit like the CSA concept, spending a bit of time doing some work for groups like this is mutually beneficial. The group gets a much better looking website than the standard (often shockingly bad) community group fare and I get to expand my skills and knowledge too – in this case I learnt all about how important it is that Wordpress templates deal properly with images which are too big. Righton!

Sour Australian grapes

London advertising agencies have been made the butt of the joke in a new viral created by an Australian digital marketing strategist.

The Melbourne-based strategist, known on YouTube as “Simontsmall” posted the clip in reaction to losing the account for the New Zealand vodka brand 42Below, to an unspecified London agency.

With all the gloom and doom in the news, it’s nice to be reminded that we lead the World in the creative industries.

Thanks to Nick Clement via Facebook.

Get down on it…

If only their customer service was as good as their adverts.

t-mobile advert

Customer service: a bit of thought always helps

I’m in two minds about posting a customer service rant here, it tends to feel as if someone is venting their spleen. Ah well, maybe that’s what I’m doing. But there’s a point relevant to working in web development here somewhere. Probably.

My phone stopped sending texts last week, giving a fairly terse error. My phone is a Palm Centro, so it’s unusual. The first place I turn for help with it are always forums on the interweb. That’s what I did. The error code it gives, it turns out, is a carrier/network error. That signalled bad news to me: I was going to have to phone T-Mobile and ask for their help. I knew that this would be a nightmare: I’d have to wait a long time, they would want to ask me lots of questions about the error and the phone but they wouldn’t know anything about the Palm Centro since they don’t sell it (I bought it sim free for use on any network).

Lo, I had to wait about half an hour, the chap started asking me all about my Nokia N61 (an awful phone I’d ditched within about 2 days of getting it from them) and didn’t know anything about the Palm. He wasn’t interested in the fact that I’d done the research on the error which had concluded it was a network problem. He said that the network where I was was working fine and suggested that since the phone wasn’t one they sold or supported, I’d have to find another phone to test my sim in and/or try another sim in my phone. I’d have to do all the work in other words.

Well, fair enough I guess. I haven’t done anything more yet (apart from continue to have to phone people who send me texts to explain that I can’t reply). But then, the kicker. Today, T-Mobile sent me a text. It was a survey asking me how I rated the help I got from the support call. A text, yes. I had to reply…by text.  So whilst I desperately wanted to reply “1. Not at all” I couldn’t of course. Brilliant. Clearly it’s an automated system which would happen for every support call. But then, wouldn’t a lot of support calls tend to be about problems with texts or the phone generally? Wouldn’t it make sense for the customer service dude to be able to set a flag to say: “Don’t send this person a text to survey their satisfaction with my call – it won’t work”?

sms-survey-doh

For me, T-Mobile have added insult to injury. They’ve failed to help me and then rubbed my face in it. My contract is long over. Maybe the quickest way to sort my problem would be just to jump ship…

Google Latitude : getting it almost right

Google Latitude is a new service from Google that allows you to broadcast your location to friends and family from your mobile phone or laptop device. I’ve set it up on my phone to see how well it works and it’s been surprisingly accurate considering I don’t have GPS in my phone (it uses mobile phone masts to triangulate my position).

It also managed to pin-point, to a few metres, the location of my girlfriend from me logging her into the service from a laptop in her house. I haven’t figured out how it managed to do this yet, and I find it a bit alarming.  Any ideas?  Can your IP address be that accurate?

Given all that I was pleased to discover that even Google gets it wrong sometimes when I looked at the Google Latitude widget on my home page this morning:

Google Latitude widget

There I am, on the map at Hyde Park corner, correct, but I’ve never been to Finland.