Terry Bleizeffer — Thu, 31 May 2007 11:27:47 GMT

Agile development and UX is an intriguing subject. On the one hand, for those of us working on products that have two-year release cycles, the ability to make incremental improvements over relatively short intervals is very appealing. On the other hand, I’ve heard from UXers working in Agile teams that they can ONLY make incremental improvements… that it’s extremely difficult to get any changes accepted that require more than a single iteration to complete.

Regarding Google, it sounds like they were using a “brute force” style of UX on this project. As Max says, it’s hard to know whether that translates well to the rest of the world, where every UX decision from process to design is intimately tied to limited resources. I wonder how Google has justified their UX expense internally… or whether they haven’t needed to on the grounds that Google has more money than they can spend anyway. A nice problem to have. =)

Wayne Pan — Tue, 22 May 2007 21:12:34 GMT

“Designing a good mobile web user experience requires seemingly endless device, location, and use-specific hacks.”
To minimize the affects of the use-specific hacks everybody should check out WURFL – http://wurfl.sourceforge.net/

Comments on Lessons From Google Mobile