We designed an app to accompany visitors to the bi-annual exhibition at the HfG. The app uses Beacons to allow collect additional information while walking through the exhibition.
We rethought the process of how people interested in studying at the HfG can be encouraged to actually apply: We identified the exhibition that is held at the end of every term as a major selling point. When an interested person can see actual projects, visit the campus and get in touch with students they are likely to apply. As of right now when they leave the exhibition they have nothing to take home with them and are likely to forget what they saw. To change this we created an app that allows users to collect information that is spread across the campus and take it home with them.
We wanted users to focus on the exhibition, not the app – our goal was to keep them from looking at there phone all the time. To pull this off all interactions and notifications had to be timed precisely and the amount of information had to be well balanced.
Process at the Exhibition
We present every piece of information as a card, which can be expanded to show more detail. When the user launches the app for the first time there is only one card. It explains the process of applying and is steadily updated to inform the user about the next due dates.
Each card is assigned to a specific place in the building. It only becomes visible in the app when the user approaches this place. That way, when the user scrolls through the cards he can revisit his personal path through the exhibition.
Design of the App
We tried to keep the structure for the app as simple as possible: There is no time to learn about the app, users need to be able to use it instantly when they arrive.
It was extremely important to us to be able to actually test the location based idea of the app. I therefore got into iOS Development with Swift and coded an actual native prototype of the app. We used iBeacons from Estimate and learned a lot about how precise they are (less than you think) and how easy it to work with them (very).
Coding an actual iOS app is quite challenge, but nothing beats the speed and precision of a native prototype. Especially being able to access all native APIs is great. Writing a native prototype is not something that I would do for any project, but it’s definitely great if you want to use new technologies and be sure you are using them right.
My focus in this project was on concept development, process design and prototyping.
This is a student project created during summer semester 2015 as part of a course in Interactive Communication Systems by Prof. Jens Döring and Julia Stäbler.
Prototype on GitHub