Evaluation of Affective Interactive Applications

Abstract

Methods are developed for different audiences and purposes. HCI researchers develop methods to shape the future through pure, applied and blue sky research – as is still the case with most affective interactive applications. Unsurprisingly, practitioners will be more concerned that the methods they use not only are tractable but produce better and more innovative results in terms of the systems they ultimately release into the world. Researchers, on the other hand, may have other concerns, such as the novelty of their techniques. Up until recently, most HCI methods (both for researchers and practitioners) were developed for work applications and desktop situations. They focused on efficiency, learnability, transparency, control and other work-related values. They were developed in response to a theoretical orientation which viewed the user as an information processing system not so dissimilar to the computer itself. But now that HCI is concerned with technologies that enter all aspects of life, our methods have begun to change and will need to continue to change. In keeping with our changing conception of what a “user” is and a wider concern with their experience of use of new technologies, a key challenge will be to develop and expand methods for analyzing not just what people do with the technology but how it makes them feel, and not just how people understand technology but how they make sense of it as part of their lives. Methods must be concerned, not only with issues of usefulness and usability, but also with issues of aesthetics, expression, and emotion. In addition we need to focus on evaluating technology not just in the short term under controlled conditions but also in the longer term and in broader social and cultural contexts. In this section, we will therefore provide two strands of evaluation methods. The first concerns what we might see as more traditional usability evaluation: is my system usable for the purpose it was designed for? The second strand tries to get at what we have named “third wave of HCI” in the previous chapters: does my system provide for the kind of (emotional) experience that it aimed to do?