top of page
User Persona
Screen Shot 2020-05-06 at 9.31.17 AM.png
Screen Shot 2020-05-06 at 9.35.20 AM.png

Scenario 1:

Sam is a naturally curious learner! Ahead of his science class field trip to Los Angeles, he wants to get ahead by studying a bit about the places he will be visiting so that he can share with his parents! Upon surfing the web, he realizes that there are a lot of science museums around Los Angeles! Overwhelmed by the abundance of information, he looks for an app that will summarize all this information in a concise and personalized way. Now, he can use the 'Explore' tab on the app to see all important science landmarks in one place. In addition, he appreciates that he can now filter by a specific interest, such as astronomy! The app curates recommendations for his specific interest. Each page provides information and highlights about the place, as well as the option to save the location for future reference and quick access.

Scenario 2:

Due to his limited time in LA, he wants to maximize his time by planning his itinerary beforehand. He knows LA is notorious for the traffic. He is also afraid that many museums have limited hours. He needs assistance planning his trip. He opens the "Plan" feature on the app, where he has the option to create a tour using his saved locations or search an existing tour that will automatically recommend tours based on Sam's known interests, which he can further sort based on interest, total time needed, and other factors. He decides to use the recommend tour feature, and filter by his specific interest, Astronomy.

​

Scenario 3:

Sam wants to utilize the "Experience" feature during his trip. The "Experience" feature will allow him to explore the museums at his own pace with the help of the location-prompted audio tours. He will also have a more interactive experience, as he can us the camera feature to overly a historic scene over the area he captured.

Low Fidelity Wireframe

IMG_6512.jpg
IMG_6511.jpg
IMG_6513.jpg
Wireframe
User Feedback

User Feedback

Introduction to Low Fidelity Prototype Testing

 

I invited my roommate to test my low fidelity wireframe and wireflow. For the first two scenarios, she was able to give insightful feedback on the user experience. Specifically for the third scenario when testing the location-based service feature, she gave me realistic feedback as a user and proposed adding additional components, such as an AR feature that would allow the user to discover a hidden feature around their surroundings. 

 

For this wireframe, I focused on three main scenarios. 

  1. Research points of interest by location.

  2. Finding an itinerary that fits the user’s interests and needs.

  3. Using the AR feature to discover hidden photo spots around the user’s location.

 

Overview

 

The user’s main suggestion was to include navigation to other tabs whenever possible. Because the live location-based experience is a main feature of this app, the feature should be easily accessible and reminded to the user whenever relevant, rather than only having it accessible through the main tab.

 

She also mentioned that the text within the app should be concise in order to reduce clutter on the screen. Overall, she really enjoyed the idea of the app but was worried about how realistic the AR feature is. 

IMG_6543.jpg
IMG_6545.jpg
IMG_6542.jpg

Scenario 1

​

On the first main page, Cydney proposed that there should be a differentiation between a search bar and a filter option. She thought that it would make more sense to include a search bar at the top of the screen that would allow the user to quickly search on the map. The filter by category text link should be replaced with an icon that would direct to the next page. This would declutter the screen with less text and allow for more visualization. For the filter page, I should alphabetize the categories so that it is easier to find. The user liked that it was categorized and visually differentiable with symbols rather than a simple drop down menu. She suggested adding a “Take a Virtual Tour” option on the location info page that would direct back to the location-based feature. She was confused on whether the text box below the map was an adjustable size and whether it can fully cover the screen and the map.

Scenario 2

 

The user was confused between “Custom Tour” and “Search Tours”. She suggested changing the categories into “Custom Itinerary” and “Find Tours”. For the purpose of this prototype, I asked the user to use the “Find Itinerary” feature. The user was confused in the transition from the first screen to the next screen. She proposed adding an additional screen with options to filter by Location, Time Required or Category. Once the user inputs these options, he/she will see the next screen with the map and list of tours. From a user’s perspective, she also wants to know the travel time between locations in addition to the time spent at the location.

​

Scenario 3

 

The user liked the location-based camera feature. However, she said that it will be more engaging and interactive to utilize the AR camera feature to discover hidden photo spots around the user’s location. This can encourage the users to interact with their surroundings. The placement of the audio tour at the bottom of the screen was awkward. The user mentioned that it would be nice to receive a notification and have the choice to skip a part of the tour if she wanted to. The user said that there should be a camera icon next to the attraction/exhibition to indicate whether there is an AR feature or not. Once the user clicks on the camera icon, there should be an explanation on the AR feature for new users who are unfamiliar with the technology.

 

​

bottom of page