---
# System prepended metadata

title: 'Team ARLANDAR: DP3 Low-fidelity Prototyping'

---

# Team ARLANDAR: DP3 Low-fidelity Prototyping

## Table of contents

- [POV](#POV)
- [Tasks](#Tasks)
- [Prototype](#Prototype)
    - [Link to](#Link-to)
    - [Protoyping tool](#Protoyping-tool)
    - [Design choices](#Design-choices)
    - [Representative screenshots](#Representative-screenshots)
    - [Instructions](#Instructions)
- [Observations](#Observations)
    - [Participants information](#Participants-information)
    - [Usability problems](#Usability-problems)
        - [Task 1](#Task-1)
        - [Task 2](#Task-2)
        - [Task 3](#Task-3)
        - [Plans for improvement](#Plans-for-improvement)
- [Studio Reflection](#Studio-Reflection)
    - [Summary](#Summary)
    - [Addressing](#Addressing)

## POV

**Musicians** who are willing to showcase their talent **need** an effective method of reaching out to nearby people **because** that could ultimately promote their music, help communicate with their potential fans, and enable collaboration with other musicians as well

## Tasks
1. Create a new live performance with some description and location
1. Check out the music suggestions from others and update the playlist for future (upcoming) performance
1. Search for existing performances of other musicians and select one, and then ask the creator of event to collaborate

## Prototype

 ### Link to
- Prototype before the presentation: https://www.figma.com/proto/Sy4nHOqibM1g55HgNks8Bo/DP3?node-id=50%3A10&scaling=min-zoom

- Prototype after the presentation (fixed some issues): https://www.figma.com/proto/Sy4nHOqibM1g55HgNks8Bo/DP3?node-id=191%3A161&scaling=contain&page-id=186%3A160

 ### Protoyping tool
- Figma: Because every team member are familiar to it, in addition, in Figma you can create many functionalities such as buttons, check mark, which works same as real website's functions. Creating Buttons, check mark and making good interactions between different pages worked well
- Using overlay tool works as alert function, so you can not use it all the time, because it blocks other functions. So it didnt work well for making easy and effective interaction between different artboards
 ### Design choices
- We have decided not to implement these functionalities:
    - User registration and login
        - Because it is not really necessary to complete our tasks
    - Get Started Button
        - As we decided not to implement login and registration pages, **Get Started** button navigates directly to **My Upcoming Events** page. In future, when we will implement login and registration pages, **Get Started** button will navigate to login or registration page.
    - User profile settings
        - Changing name/profile photo also doesn't necessarily affect the flow the actions
    - Not all of the events are expandable (without detailed view)
        - We showed the event detail view for one or two events and those are the same as the others
    - Inputs
        - Text, Image, Location and Date inputs are all hardcoded and generated when user clicks to the appropriate field
        - This was due to Figma's limitation and the low importance of these features
    - Dialog boxes are not closable
        - In real prototype they will be closed after few seconds
        - Also we didn't want to copy+paste many additional pages in Figma
    - Search bar is not working
        - Because of Figma limitation and the irrelevance to our tasks
    - Seeing the full playlist of others is not available
        - Because the UI is the same as when you see the list in your event
    - Adding songs to your playlist is not available
        - Dialog box is the same as suggesting song to others
    - Removing songs from your playlist
        - We though it was redundant because the only thing changes is that an entry gets disappeared

 ### Representative screenshots
![](https://i.imgur.com/vlltytc.png)
*Figure 1: Homepage of Aeuen*

![](https://i.imgur.com/ufKAhGO.png)
*Figure 2: Process of creating a new event*

![](https://i.imgur.com/Rqkhq01.png)
*Figure 3: Choosing music suggestions from others*

![](https://i.imgur.com/C0cI71o.png)
*Figure 4: Sending a collaboration request to other performances*


 ### Instructions
- After finishing each task go to the homepage by clicking "Aeuen" button on the top left corner, and start next task
- Task 1: Create a new live performance with some description and location
  1) Go to "My Events" page or either click "Get Started button" in the homepage
  2) Click "Create" button on the left side
  3) Fill out the form by clicking on the input fields
  4) End of the Task 1, go to homepage
  
- Task 2: Check out the music suggestions from others and update the playlist for future(upcoming) performance
  1) First go to "My Events" page and you should see the list of your upcoming events
  2) Click on the "Radiant Guitar" event
  3) Check out the suggested music, and update your playlist for this future event
  4) See your playlist 
  5) End of the Task 2, go to homepage
 
- Task 3: Search for existing performances of other musicians and select one, and then ask the creator of event to collaborate
  1. Click "Other Events" button and you should see events list of other musicians 
  2. See detailed view of "Big Concert" event
  3. Ask for collaboration. Now you will be waiting for the request to be accepted
  4. You can also try to suggest some songs to this event
  5. End of the last task!
  

## Observations
 ### Participants information
- Participant A
    - Guitar player from Daejeon, 25 y.o
    - She wants to collect audience for her performances but hesitates to advertise her events in a traditional way (posters, media) because of extra costs

- Participant B
    - Pianist from Seoul, 34 y.o
    - He was interested in performing in front of people, but never knew how to create performance and gather people
- Participant C
    - Street singer from Almaty, Kazakhstan 20 y.o.
    - This singer used to make street performances, however he quited doing it, because it seemed impossible for him to find his fans and become popular.
    

 
 ### Usability problems
Problem [severity, user/s]

#### Task 1
1. No brief description for website purpose [minor, user A]
2. Upcoming events are ambiguous. No clear distinction between your and others’ events [critical, users A, B, C]
3. Event info doesn't have time and contacts, max # of people, performer, instruments, music or singing song [critical, user B]
4. Unclear what text fields mean (description, name, etc) [medium, user B]
5. There is no option to add posters in create event [critical, user B]
6. Selecting calendar or map is confusing (full screen map appears immediately/calendar is also confusing) [medium, user A]

#### Task 2
7. See playlist and suggestions are not distinct [critical, user A]
8. The buttons are disappearing or change their function [medium, user A]
9. Song suggestions could be useless as the organizers usually make plan before creation of event [critical, user B]
10. The event cannot be updated after creation [critical, user C]

#### Task 3
11. Confusing statuses (“Attending” and “Pending request") and buttons ("Requested", "Join", "Collaborate") [critical, users A, B, C]
12. Didn't notice that he joined event [medium, user A]	
13. The user couldn't suggest music to other musician's event [medium, user B]
14. 

 ### Plans for improvement
- We tackle problem 1 by adding information about the website on the homepage
- We tackle problem 2 by showing "my upcoming events" into user's events
- We tackle problem 3 by adding more information for the event regarding time and contacts, max # of people, instruments, and etc
- We tackle problem 4 by giving examples on how to fill the text fields and explaining what the text fields mean
- We tackle problem 5 by enabling to add pictures (posters, musician info) while creating an event
- We tackle problem 6 by showing pop-up for calendar and map rather than opening into full-screen
- We tackle problem 7 by creating different buttons for "see playlist" and "see suggestions"
- We tackle problem 8 by making static/non-disappearing buttons
- We tackle problem 9 by dividing events into fixed and undecided playlist when create event
- We tackle problem 10 by enabling different types of events (fixed, modifiable) and enabling modification
- We tackle problem 11 by showing explanation of the buttons when user points to it (tips) and changing some names into more proper ones
- We tackle problem 12 by showing pop-up message when user joined event
    - Or we might remove the joining functionality at all
- We tackle problem 13 by adding "suggest music" button

## Studio Reflection

### Summary
Overall, studio members liked that our prototype is user centered and not function centered. Furthermore, they complimented our prototype for being simple and easy to grasp due to provided live demo. Because we did not choose colors properly, studio members struggled to read texts in our prototype. Studio members asked several questions on feedback form and below we are addressing some of those questions.
 - I would like to use a different color on the homepage. It is difficult to concentrate because of the large number of fluorescent colors, and especially white text in green text box and green text on yellow background is difficult to see.
 - Showing upcoming other event is more accessible for audiences.
 - Design seems more close to mobile, I wish you utilize with features of web, also some bigger size of screen, make it scrollable is good for tester too.
 - I wish some images that can show the concept or mood of events.
 - I wish the info about participants were a bit more specified. Explanations about such unique features of participants may be interesting.
 - I wonder if the recommending playlist part is necessary for your target users.
 
 ### Addressing
 - We would definitely update our styles to make it easier for audience to use our prototype.
 - Since our main user target are musicians, we have decided not to allow any interaction for general audience.
 - Due to simplicity of our prototype, it might seem that we are developing a mobile app. But when we will design high-fidelity prototype, we will implement our web app to achieve high-fidelity in depth with web specific designs.
 - Good point. We will consider it when implementing our web app to have classifications for performances.
 - Due to privacy policy, we will not be able to provide such information.
 - Our target users are musicians. By using recommended playlist, they will be able to select musics for their next performance such that audience would be more willing to come to hear musics they want to listen to.