Primary prototype's features

We decided that Audio Guide would be our prototype's main functionality. This decision was mainly based on the fact that The Medieval Museum's Audio Guide was very expensive and not working according to interviews with the staff. Furthermore, an Audio Guide would help us solve many of the problems we identified in the problem space regarding our target group and contemporary technology.

We also decided that the audio guide should be available on smartphones and tablets in an application since they are cheap to maintain and easy to download. Moreover, through our interviews, we found out that many elders do have smartphones, however, they did not use it for any advanced tasks often.
It is also easy for the museum to buy a few cheap tablets to lend out to people if they do not have a smartphone.

For the next session, Parallel Design, we needed to decide upon the most basic features, a.k.a the visibility of our prototype.

The features our low fidelity prototypes should have are:

• A scanning screen: We decided that the Audio Guide function should be initiated by scanning a QR-code. Thus, we need to have a camera/scanning screen.

• Play/Pause screen: When the code has been scanned, the users need to be able to pause or play the tape again. We wanted some kind of play/pause screen that managed this.