Why is it that so far no web application platform, framework or content management “solution” seems to care about the UX of the applications they are responsible for creating? Systems such as React, node.js, Zend, Drupal, Rails, etc. allow for the debugging of code, the optimisation of resources, ease of configuration and deployment. But they […]
A few months ago, the New York Times wrote about “Scoop”, their new publishing system. Scoop, they point out, is more than just a means of facilitating their editorial processes. They see it as “…central to our ambitions to innovate on all platforms”. They also point out that the capabilities, ease of use, and competitive edge of content management systems is an […]
When multiple designers work on multiple assets or across multiple projects, it gets very difficult to manage files over time. Which files are the latest versions? Which files are even relevant any more? Which files contain things that may be affected by the contents of other files? Yet with a few short-term exceptions, I have yet […]
There’s some debate about the utility of “high-fidelity wireframes” at work at the moment. It’s a reasonably common topic in the UX chattersphere too, so I thought I’d expand on it here. Firstly, to avoid some potential misunderstandings – let’s make some assumptions about the domain we’re in:
Data visualisation (“dataviz” or more broadly, “infoviz”) appears to serve two main purposes. The first is to show data to people who are not analysts or experts. This is so that they can understand some or all of something that has already been identified in that data. The assumption here is that raw tables, or perhaps bunches of charts […]
It seems like not too long ago, many IA/UX designers fought endless battles on mailing lists and Usenet about whether Visio was better than Freehand which was better than Omnigraffle which was better than Excel (no, really, I’ve seen people use Excel to express UI ideas). There was always some software or other that totally […]
At Hotels.com we’ve been doing multi-variate testing (“MVT”, or sometimes “A/B testing” if you’re variant challenged) for a while. This means we typically build a number of different designs, then let them duke it out on the live site to see which one performs the best. Recently, however, I’ve been increasingly aware that while we […]
With my Kindle’s free worldwide 3G connection (which I’m hoping to make some use of when I’m travelling to the Americas next month), I thought I’d investigate options for reading RSS feeds. Being the geek I am, I liked the sound of Daniel Choi’s kindle-feeds, a neat little Ruby script that gets RSS feeds from […]
While I’m obviously rather late on the uptake here, I recently (and rather reluctantly) upgraded to Office 2007 on my work laptop. The “ribbon” UI is now sapping my will to live – I had to resort of Googling to work out where the “Links” dialogue had gone in Word, and many functions in Excel […]
It’s that time again, when my fragile designs need to be encased in a sturdy barrel of documentation and set off down the rapids of implementation. All I can do is hope that they end up at the bottom in one piece. If there’s one thing that’s constant about documentation, it’s the maddening inconstancy of […]
I must have followed (and contributed to) dozens of conversations about web prototyping tools over the years. Having skimmed through yet another thread on the topic this week (this time on one of the LinkedIn UX groups), pretty much the same pattern repeats itself. Some swear by Visio, others Axure. Some say Fireworks has no […]
With the advent of Thermo “some time next year” things are at last hotting up in the RIA design space. Regular readers of this blog (if there are any such people) will know that I have been wondering for a long time in a somewhat Pooh-bearish way about the future of “The Designer” in the […]
I’m a bit late with this, but last weekend’s Slashdot discussion of this article on the ZDnet blog was interesting, if somewhat awe-inspiring in so far as some of the opinions expressed about designers (and the software development process in general) were breathtaking stupid. Ever since I got preview of Expression and the wonders of […]
One of Microsoft Word’s biggest time-wasting functions is auto-numbering. This feature is actually an option which (of course!) is turned on by default. Hardly anyone knows this though, so most people struggle needlessly as auto-numbering rudely kicks in when they start a paragraph with “1.” It then usually refuses to actually number the other lines properly according to what the user wants, or to stop numbering when they want it to; or re-starts not from 1, but from 5 next time, or whatever. The behaviour of auto-numbering is not in fact the bugfest that it appears to be. It’s just follows a logic too complex to actually understand.
So you’d think that the OpenOffice developers would see this, laugh, and either avoid it or implement something better. But no. This is a visual bug report (3.1Mb MPEG) of why the OpenOffice designers should not attempt to follow Microsoft’s “lead” here.
I was in Dallas last week. It’s a big place – it has the second largest airport in the world in terms of square mileage. Even the city is so big it gives you a feeling that hardly anyone’s there. We went there to observe some user testing of a prototype I’d created, and to conduct some marathon meetings with the client. We discussed, amongst other things, the juicy subject of how we’re to engage with the build team, etc.
For as long as I can remember, I’ve been trying to find a better way of documenting designs. I’ve posted about this before, and I still think that Axure looks promising, but most of my IA life’s been based around Visio, some occasional PowerPoint – and on joining Oyster/Framfab – FreehandMX. None of these tools has really baked my cake when it comes to combining text with annotated graphics though. This is a shame because that’s what I’ve been doing a hell of a lot of in the last couple of years. However, after a chance realisation abut MS Word a couple of months ago, the arrival of a Fireworks guru on my project and some good teamwork, things are looking up and I want to tell you about it.
I went to the Microsoft Campus yesterday to have an informal preview of some of the new Windows UI things to be announced next week (technically under NDA – so sue me).
There’s been a great thread on SIGIA this last week or so on the good old subject of documentation. It’s incredible how diverse the approaches are. Some people are plugging away with ye olde Visio, while others are pioneering with things like Dreamweaver and even Together.
I find myself doing what I think might be an unhealthy amount of thinking about the tools I use to do stuff, and regular readers of this blog will know that one of my ambitions is to discover – or better still help to make – an Information Architecture IDE. So one of the things I’ve been meaning to blog about is the latest release of what was called Ubiquity RP, now Axure RP, by a company called Axure. Peter van Dijck published an interview on his blog with the creator, Victor Hsu, when the first version went golden. I had a look at that and corresponded with the creators about a few things. My verdict at that point was that it wasn’t ready for industrial use, and sure enough, the IA world hasn’t exactly buzzing about it. But version 3.0 shipped a couple of months ago – so is it a quantum leap or an incremental change?
As part of some recently expansive thinking, I’ve been jamming on the following theme recently as follows. So far, I’ve got some thoughts, but no good solutions, on streamlining the experience and graphic design process overall.
It’s been nose-to-the-grindstone this last week working towards an insane deadline to write up the findings (and think up some suggestions going forward) from a large card-sort being done while I was in Milan the week before. Planning and analysing the results of a 30-user card sort is actually rather fun. It’s rare you get the chance to do one – I only regret not having the time to facilitate more than a couple of sessions. And of course it’s more than just a pity it ended up crashing into such a short deadline, but such is life. At least, I say it’s just life. But I have a sneaking suspicion it’s something else as well.