This is our final project video! Enjoy!
Besides doing the Weeks 6 task (see post below) each of us was also coding hard for the protoype. See one of our results in this video:
We will present the other new features at the next lecture on Tuesday!
While the others are still coding hard for the next version, I asked two of my kind flat mates to test the latest version and here are the results.
Date/Time: Sunday, 01-29-2012, 2pm
Place: our kitchen
Recording Technique: pen & paper, photos
- How intuitive is the user interface?
- How fast does the user recognize the idea behind the application?
Since we were not sure, if people would get the idea behind our application immediately, we tested if our probands would intuitively interact with the clothes and if they would pay attention to the event-information. So the task for the users was simple:
Try out the application and try to understand the functionality . Think aloud while testing and tell us afterwards, which benefits of our application offers to you.
Person 1: Maria, 25
– is already experienced with Natural User Interfaces through Nintento Wii
Person 2: Silke, 30
– has no experience with NUIs
It turned out that both probands did not notice, that there was a gesture-control for changing the clothes. Nevertheless the arrows at each side were used immediately by Maria and Silke.
Another problem was that the closes changed randomnly or by accident. The arrows were considered too big by Maria, because she touched them too often by accident and the clothes changed, although this was not intended by the probands. Also the gestures are leading to accidental changing, which effects the user experience in a negative way.
The third major issue was that the event-information were noticed, but not really catched the users attention.
It is also to mention, that Silke played quite a long time with the application to find out if there are more features. Unfortunately she could not find any more (yet).
Here is a quick overview ordered by severity (most important problem on top):
- No attention on event-information
- Less interaction
- Users did not notice gesture control
- Clothes changing by accident
We need to emphasize the event-information. This could be done visually with colors or animations.
Otherwise it could also be done with sounds, which are played when changing the event. The sounds could be corresponding to the event.
As we already learned from our heuristic evaluation, we need to give the user the oppurtunity to interact more. Therefore we are working on mini-games.
Since the user did not notice the gesture control, we are thinking about removing this function again. Since the arrows are sufficient to control the application, we won’t loose functionality when removing the gestures. Another problem is, that the gesture and the mini-game could “bug” each other.
The last issue on our list should be easy to solve, if we remove the gesture control and make the arrows a little bit smaller. Furthermore we will add some color changing to the arrows, if they are touched. In that way, the user gets a feedback and knows, why and when the clothes/event are changing.
Be prepared for our next awesome prototype.
After testing our application prototype individually, using heuristic evaluation (according to Ten Usability Heuristics by Nielsen), we came up with the following conclusion:
Visibility of system status:
Given at the moment, since each user gets the clothes directly projected on the body. Still: We’re going to improve the design of the arrows for emhasizing their function and thus ease the understanding about their function.
Match between system and real world
Still room for improvement here. The user might expect the usage of swiping gestures for switching the screens. Thus, we’re going to implement it.
User control and freedom
At the moment, we just provide the opportunity to switch screens by using the arrows. Again, obviously we need to implement swiping gestures. Additionally, the user cannot change clothes individually, meaning switching solely pants or shirt. We don’t consider this as a weakness, since this won’t match our concept of the public display. A user can quit the application, whenever they want just by leaving the scope of the camera.
Consistency and standards
Currently we’re using arrows for stating that it is possible to switch screens, thus we’re matching a current standard. Moreover, our UI is consistent: On every screen the user gains exactly one new set of clothes and may switch to another one by using the arrows. For further improvement we’re going to include screen transistions and allowing user gestures for making the experience feeling more natural.
Recognition rather than recall
We’re using common symbols such as arrows. Furthermore, having the clothes projected on the body is pretty much self-explanatory.
Flexibility and efficiency of use
Shortcuts for experienced users are not part of our concept.
Aesthetic and minimalistic design
Already minimalistic, not yet aesthetic (consider it’s still a prototype!).
Help users recognize, diagnose, and recover from errors
Not yet implemented, so currently our prototype is lacking that feature. Further versions are likely to have a timeout implemented; when the users don’t move for a certain time, a popup or banner is going to appear for giving further hints.
Own project-specific heuristics:
Motivation for participation:
Participation requires less affordance and since the clothes are projected instantly an people that are passing by we consider the motivation of our application pretty well.
Entertainmeint value / information value
Our application does not provide event-specific information yet. Furthermore there’s room for improvement for increasing the entertainment value. An appropriate measure would be including event-specific mini-games, such as a ball the user can interact with, if the currently-displayed event is a soccer game.
To sum it all up, our next steps are:
– Including swipe gestures and thus giving the user the opportunity to switch screens through gestures.
– Including helping popup.
– Including event information.
– Including event-specific mini games.
…Whereas we consider the the popup and the event information the most important ones (basic functions!). Closely followed by the gestures and the mini games.
Yesterday we tested our user interface with two people. After a short introduction what they should do they were a little bit confused. Of course, they never interacted with paper before. The initial screen contained the football game event with the jersey shirt. As the first user recognized the arrows which our interface provides, he chose the left one for the first event-change. For this, he put the paper hand on the arrow.
Sebastian acted as computer and put the corresponding paper elements (event information box and clothes) on the paper screen. Now our prototype showed the second event: the opera ball with smoking. Then the user changed to the St. Patricks Day event with green clothes.
After this the user understood quite well what our application is all about. The arrows where easy to understand, just the way how to interact was not so clear.
What we learned from this experiment is, that we have to take care that our application provides an explanation on how to control the arrows with gestures.
Today we developed our paper prototype for our user test. Here are some pictures of the work in progress:
We created three events: a football game, St. Patricks day and an opera ball. UI elements are basically the two arrows on the right and left. We have an information panel at the top displaying event data. We also created a Post-It representing the user’s hand (the “cursor”) to be able to explain the interaction better to the user.
All the four of us have worked on the prototype together. I took the pictures that’s why I’m not present on them. We will continue with the user tests on monday.
- The user must be able to change events in both directions.
- Switching events should either be caused by swiping gesture or touching arrows at the edge of the display.
- The user must be able to switch between at least 5 events.
- Event data will be displayed at the top edge and contains date, time and location.
- The user that is recognized by the system first gets the clothes projected on his body immediately.
- When the user’s projection leaves the display completely the display waits for the next user to track.
- Switching between top 5-events and location-based events via a toggle-button at the bottom edge.
- Manipulate the background to display the event’s location.