Project #1: &sounds. Presentation.

Presentation Slides.

And the Prototype.

Project#1: &sounds. Design and Prototype.

Next steps after last week's user testings: 

1. Decide on improving either prototype 1 or 2.

2. POP prototype 

I've decided to work on Prototype 2.

Changes: 

1. Added a secondary navigation, so it'll less steps for users to explore new sounds, access their sounds, and check their feed.
2. MY FEED. Changed the square "thumbnail format to a band. This is to reduce the amount of information overload on the feed and sounds are usually presented in a list. (Signal to ration & using elements of the real world into the design principles). 
3. CATEGORY. Colors assigned are now determined by sound category, suggested by computer, to give a bit of a surprise. 
4. SEARCH. "Side Nav" Search function is combined together with "Explore", as it was confusing for users. Instead of 2 search functions with 2 different filters, now it's 1 and users will be able to add categories. 
5. EDIT. This function follows the search filters, to make it more uniform with the rest of the app. And also to minimize confusion. (On hind sight, I think it'll be confusing, as users will need to apply filter & listen to the changes they've made). 
6. SIDE NAV now has lesser options. "My playlist" isn't something that's as important as "my sounds" or discovering new sound. User can access it through "my profile". 

Here's the POP Protoype.

VivaQuest Final

Prototyping: If I were actually making this app I would want to go through this process many more times with many more people, particularly teens, since they are my target audience. I found that many of the critiques I got from testers were consistent from person to person. Some of these were:

• The progress bar looks like it should be interactive
• The number on the star bar is confusing
• Not quite so many confirmations in the confirmation dialogs.
• The stars should be more prominent on the quests

From observation I noticed that testers spent a lot of time on the stats page. They seemed interested, like they wanted it to do more, but also like they didn't completely understand the information they were seeing. I was glad to see that the navigation was pretty intuitive. No one had trouble locating, accepting, or completing quests. They were also able to change the settings without difficulty.

I have not made a final version of every screen yet. I focused on the main views. Most of the ones that are not shown are mostly confirmation dialogs which will be temporary views. An example of a temporary view is shown below.

One bit of feedback which I have not been able to incorporate yet is that the star points should be used for something.

Home view. This is the version of the home view that the user sees after they have accepted their quests for the day. A green check indicates that a quest is complete.

Temporary View. I added a temporary view that pops up when the user taps the progress bar in response to tester feedback that it seemed like it should be interactive.

Quest Detail View (before the quest has been accepted). Each quest has a detail view that provides an image or map as well as any specific instructions for completing the quest. I added the star value of each quest to the detail page in response to tester feedback.

Quest Detail View (after quest has been accepted).

Quest Complete Dialog. This is an example of a temporary view.

Quest Log View. The user can view any completed quests here. One suggestion I got that I have not yet worked in is to have the quests viewable by type as well as date.

Settings View. I made interactive items blue.

Stats View. I reworded and reorganized the text based on tester feedback.