Prototype, evaluation and feedback

For critique session 7, we decided on the project scope and merged the three different design ideas into one concept with the prototype tool "Invision".

We also decided on some limitations e.g. you cannot comment on a picture since these pictures/stories are memories that you want to share with other people and it is a gift by the user to other users. Also, you can only unlock a particular area when you are in that location. Only when you have unlocked that area can you seen the pictures that other users have uploaded. When creating an account, you have to use your real name and contact information because the purpose is that you should share real memories. Other users will not be able to see these personal information, therefore when you share a picture, only your first name will be announced.

Despite that, an heuristics evaluation based on the Nielsen’s heuristics was performed:

• Number of steps. Too many somewhere?

We thought through it when designing, not having too many steps to get anywhere. Longest depth 3

• Lack of explanation?

Need explanation of the choices of categories, how it works.

Show if nothing is preferred, tell user to have something otherwise blank map.

A story around the app, what it is about. A gift of sharing memories and stories.

• What just happened?

When editing a picture, have a feedback of “updated”, showing the result of edited picture.

• Did anything just happen?

Above

• Hidden features and functions?

Filter for pictures are quite hidden, but they are more user oriented, than picture and truth oriented.

Filters to make it real, not to make everything pretty.

• Lost. Can the user get lost in the system?

When looking at a picture on a place, return to map and want to go back to that picture. The dot on that place needs to be pressed and the user is returned to the picture it was on last. (App remembering last accessed picture, but only for some restricted amount of time).

• Where is my data?

Remembers last accessed picture. User info added when getting the app.

Temporary filtering and preference filtering. Onboarding or storytelling way of informing about the temporary settings (in the map).

Have suggestions of categories to choose, depending on what others on that place often has chosen.

• What happens if click certain button?

Unsure if red is locked and what to do. Could have a picture of lock and information of some kind. (number of pictures, name of area). (might get annoying if many dots in smaller area?)

• I did not see the button.

Dots on map, might not feel as buttons.

Places — add text: “places you’ve been on”

The timeline might not be apparent.

The tips of a route of pictures done by user is unclear that it gets new rout to other place. Now it could be that more text of the picture is going to be shown.

Have a headline “temporary settings” on the map filtering part. Have an arrow showing that you can remove it.

Save button on the edit-page

When viewing pictures at a place the back should get the user back to the map instead of back in the line of pictures. To flip the pictures have small arrows to right and left of picture.

• Dead ends?

Have the discard reachable from viewing own picture instead of within edit mode??

While doing the evaluation, we noticed on some lacking functions or design features that could be improved on the prototype, such as the ”add a new picture/story” button, if the red dots outside the ranged are clicked, inform that it is outside of range to unlock etc.

During critique session 7, we received some feedback on the prototype. Most of the feedback was on the design (rather than functions), such as how the timetable should look like, that the range on the map should be smaller/ be removed etc.