RE: [agile-usability] Interaction design rules of thumb - do they exist?
Message! was mostly expressing my high level of frustration about Web apps in general which I believe are much worse than traditional non web applications (and that’s not much to say).-- Alain:Obviously you haven't used NRC's time tracking system, which is not a web-based app (it's SAP based) ;-).But I agree with you that web apps in general seem less usable than their offline counterparts. That COULD be due to what you mention, i.e. the fact that you need to have to go through complex hoops in order to achieve basic levels of interaction that are a lot easier to implement in non Web applications. But I'm not sure. Many offline apps are written in C/C++ and we all know the hoops you have to jump through to make those work! Most web apps are implemented using languages that don't require you to spend half your time chasing pointer bugs ;-).-----
- For me, I found sequence diagrams work well. Buy it may just be my style.
From: "Desilets, Alain" <alain.desilets@...>
Date: Fri, 14 Jul 2006 07:20:27
Subject: RE: [agile-usability] Interaction design rules of thumb - do they exist?
BTW, one of the things that doesn't work often enough is asking the users to report what they were doing. Many times I have seen users do one thing and then tell me that they did it differently. I would have doubted my sanity if I hadn't had co-observers with me.
Does this happen even in talk-aloud situations?