protot

WHO: After our research and the feedback we got, we were asked to question whether our user (for the interface) is the first responders themselves or people, because we wanted to tackle the issue of stereotyping of the first responders. So, I've decided to represent our chosen user group in my interface through poems, but the people who use the app don't haeve to necessarily be first responders.

CONCLUSION: From these results, it seemed that people were somewhat positive about the design. However, from the written feedback there seem to be some stuff that could be improved.

SUMMARY OF WRITTEN FEEDBACKS:
- starting menu was laggy for some people
- the prototype felt "empty" or "bare" of content
- they were interested about the artworks, wants to add information about the artworks
- they were able to navigate and find the arrows just find
- awkward navigation between the start menu and the walking route (one way)

From this, I went and made improvements on some pages, while also adding extra steps between some pages.

So for the prototype, I started with making a paper prototype. This is mostly for myself though to see how I could possibly design the app. Plus, at this point I didn't have enough content to to test to a user.

In the conceptualizing phase, I planned to make a prototype with AdobeXD. Considering I've never worked with Adobe XD, the amount of time and work I had left, I decided to skip some steps and jumped straight to Adobe XD, because I figured I need some time to learn the mechanics.

HOW: I made a post on some websites and groupchats asking for people who live in Rotterdam to give feedback to my prototype. I sent them a linkt to my prototype and a google forms with questions regarding their experience testing the prototype.

So for this first round of testing, I wanted to focus more on the design and less on the content. I gave the testers the task to navigate themselves through map by finding the arrows and reaching the end.

It seemed that some people weren't aware of the fact that you could scroll the text in the main menu. I animated the eyes to look down and up, hinting the user to scroll up, but based on the feedback they either found it accidentally or not at all.

So in the second design, I've decided to make a clickable scroll

I've made a major improvements in the buttons. In the screen on the left, you can barely see the button to BKOR page. In the second design, I made sure to design a clear button.

I've also made major changes in the BKOR info page. In the first design it very boring and I've even asked the participants if they've read it and all of them said no

So in the second design, I split the text in three and made in scrollable to add interactivity.

There was also a comment about how the map overview was kind of useless.

So in the second design, I made waypoints for the user to jump to other areas, plus an indicator to show where they are.

I also gave the info pages this light blue color, to distinguish them from the "main" direction of navigating.

Ofcourse I've added scrollable information for each artworks. I made sure the margin for the text cut the bottom a little bit, to suggest that it's scrollable.

So after that first round, I've changed and added a lot of content and tested the interface for the second (last) time. The methods and objective are still the same. But now with more kind strangers that wanted to help me :)

CONCLUSION: Comparing these results with the previous one, it was definitely an improvement. Though, I've noted that some people had trouble with the poems that keep appearing accidentally on some pages, but that seem to caused by the hitbox.

Overall, they were able to navigate better through the app and the same people that tested the previous one commented that they liked how they're given more interaction possibilities.

Though, I'm a bit concerned about the amount of people that voted "maybe" whether they could locate the artworks in the streets. But then again, it's up to them to look for those ;)