Week 7 - Experience with Paper Prototyping

Paper Prototype:

This week in the contact session the team created and demonstrated paper prototypes for Guesstoric. The paper prototype was largely based on the wireframes that were created by Anuki, based on the sitemap sketches from last week’s meeting:

Guesstoric wireframes

The aim of the paper prototype is to demonstrate the basic functionality/interactivity of the game without having it being fully implemented. The basic format consisted of the printed out wireframes, and an ‘input’ field which was made out of a paper keyboard that users can use to formulate the answer. This prototype used only one monument for an example question - the Sydney Opera House:

Example question used

The paper prototype including a paper keyboard

The team had received some feedback upon demonstrating the paper prototype. The main criticism received was that the user did not know what question was being asked, so a further clarification (i.e Question: What is this monument?) needed to be added. Some suggestions included having the letters jumbled and the game become about re-constructing the words, maximum number of skips and deciding on the the monuments (rather than getting Trove to generate a list of monuments from a particular continent). Other suggestions talked about how the UI should be colourful to attract children (this also depends on the target audience, as we may want to be targeting older students rather than young children) and accommodating for multiple ways to answer a question e.g ‘Uluru’ and ‘Ayers Rock’ would both be counted as the correct answer, as would ‘The Sydney Harbour Bridge’ and ‘sydney harbour bridge’ etc.

Feedback was received upon testing with our paper prototype

Next steps:

The feedback received has given the team a lot to work with, and the coming week will be about continuing to implement features of the game as well as coming up with 10 monuments each to use for the questions. Unfortunately the Trove implementation is behind schedule, and it looks more and more difficult to be able to extract appropriately formatted and relevant text from Trove, although extracting images should not be as big of an issue. Here is an example (taken from Facebook) of team communication and delegating tasks for the week ahead:

“Hey guys, here's a list of things we should focus on this week. Basically we want an outline of the game up on the zone with 1 question and 1 image to start off with. I'm happy to do the html/css template. Just comment with which part you're happy to work on - there are 5 parts so 1 for each person, I've tried to make them as equal as possible in terms of workload but they can overlap if you feel you can do more/is too much:

• (Izzy) HTML/CSS template for all the pages, make sure it all links to each other, some styling
• Content for Welcome, name and location pages. Content for question page (input box, output boxes etc, look at mockup/wireframe).
• Instructions overlay - display description of what each element does, can be done once question page and nav bar is done. Maybe it appears in a separate div on top
• Question page - come up with 1 monument and get and display first image from Trove results
• Final score - content (name, score etc), navigation bar for question, maybe start thinking about scoring system and how to store the player’s score after each question”