In my last blog post I wrote about the final presentation seminar sessions in the master level HCI course that Mohammad Obaid and I have been running this autumn. Based on the scores that were given to each group (from fellow students and teachers) during those sessions, I was able to select the finalists. See the blog post linked above for an explanation of e.g. the voting. In this, and the upcoming three blog posts, I will briefly introduce the finalists. The finalists will be presented in no specific order and pictures from their project blogs will be used only if it’s ok by the respective groups.
Today’s finalist is the group “Ace that Interface”, consisting of the students Joosep Alviste, Imad Collin, Hassan Odimi, Iosif Kakalelis and Mauro José Pappaterra. They came up with the idea shown in the image above – an augmented reality solution for cyclists. The view has different components, providing information to the user, which are placed in a way so that they should not interfere too much with the cyclist’s field of view. General status information, like temperature, time and heartrate, is placed in the upper left part. In the lower left part you find a map showing the surrounding and your current position and beside the map is a presentation of e.g. your speed. If you have chosen a specific route (in an accompanying app) there are also indicators showing where to turn and the distance you need to move on a specific part of the route (compare with usual GPS solutions in cars or Google maps on phones). The navigation arrow blinks when it changes direction, in order to make sure that the cyclist notes when it’s time to e.g. make a turn. In the accompanying app you can choose which information items you want to show (toggle on/off) in the augmented reality interface, select routes, etc.
This is a somewhat futuristic idea, but it is great and has a lot of potential. It presents (customizable) information which is relevant for the cyclist, without forcing him/her to take the hands off the handles or shifting focus to another device. There is a lot more I can say about this idea and the process the students followed, but since the main documentation medium used in this course is a project blog, I think it’s better that you go there for more detailed information. In this blog you can read more about the project members and the group’s whole process from requirements elicitation to the final design.