This is a first try at using TSL230R to measure HRV (Heart Rate Variability) levels. It will be used as part of a larger project to collect users’ heart rates and translate this data onto a mobile (potentially wearable) screen as a non-verbal messaging system that reveals a somewhat hidden state of ‘being’. The messages will be set to be sent according to the value range of the heart beats as dynamic visualizations (for the time being I will be using Processing). In addition to this, each message will have a specific time span and a specific ‘mood’ or ’emotion’ attached to it. To do this I will be using a second variable EEG: Electroencephalography. HRV and EEG are interesting values to juxtapose as they symbolically represent the physical, biological, and social connections existing between the heart and the brain. This second variable will add a level of randomness to the system, which will enable messages to have a wider visual scope.
more articles |
How to Plan, Design, and Conduct Effective Tests – Jeffrey Rubin & Dana Chisnell
Testing has two main objectives: on the marketing level, it aims at improving sales; on a user-centered level, it aims at minimizing user frustrations and maximizing a product's usability. As the authors point out, testing goals inform the design of a product; those work in terms of the usefulness or relevance, learnability, efficiency, effectiveness, and satisfaction factors.
Don’t Make Me Think! A Common Sense Approach to Web Usability. – Steve Krug
Steve Krug explains how we can create better Websites if we just stop wasting time on useless debates within teams and engage in 'usability testing' early on in the development process. His book provides the antidote.
He distinguishes between designers and developers in what they consider to be a 'good' website design. Designers prefer pleasant layouts, whereas developers enjoy a good amount of features. This is also compared to the duality between commercial culture and craft culture. Which is a question of aesthetics versus usability. Ideally, we would want to have both.
“Conducting a Usability Evaluation” – Patrick Jordan
After having listed various evaluation methods, Jordan provides a guideline for choosing the most appropriate method(s) depending on the level at which a prototype is developed and shows an example of how such testing might be conducted.
The Backtalk of Self-Generated Sketches – Gabriela Goldschmidt
"The inventive process" is an iterative process of jotting down ideas in the form of language or graphic drawings and of modifying them, reevaluating them, editing them, and so on, to transform or perfect an initial concept or solution.
Paper Prototyping: The Fast and Easy Way to Design and Refine User Interfaces – Carolyn Snyder
Carolyn Snyder proposes a definition of paper prototyping as 'a variation of usability testing where representative users [...] [interact] with a paper version of the interface that is manipulated by a person "playing computer" ' (italicized in original, p.4).
The aim of her book is to extend the practice of paper prototyping to a variety of HCI platforms for non-expert users to adopt as a practical tool for creating and testing their products during the development process.
The Simplicity Shift – Scott Jenson
Scott Jenson defines 'feature blindness' as users being blinded by a feature list. He identifies the bottom-up approach of creating a user persona and a task scenario as more efficient than the top-down approach, in terms of organizing a commonsensical hierarchy of a product's features. The ideal visualization would be to 'tame' the feature list and prioritize features in accordance to a set of usage requirements and subsequent usage frequency.

