# data[].attributes.body
Has difficulties with finding goals.

Comment from the interviewee:

The sign up button is too small

System Usability Scale [1-10]

1. 8

2. 7

3. 8

4. 6

5. 4

6. 7

7. 9

8. 7

9. 7

10. 8

# data[].attributes.body
Had a hard time pressing the menu button and finding a way to finish goals.

System Usability Scale [1-10]

1. 4

2. 6

3. 8

4. 2

5. 4

6. 10

7. 7

8. 4

9. 9

10. 6

# data[].attributes.body
Input transactions

Try to talk to pro(s)

Find your monthly report

Find your mutation

Try to find the goals page

# data[].attributes.body
2602086652 - Rennard Owen Tan [Project Manager]

2602066695 - Christian Arifin Gouw [Technical Engineer]

2602073290 - Shannie Tannaris [Technical Engineer]

2602075251 - Yoshua Budiawan [UI/UX Designer]

2602076222 – Johanes [UI/UX Designer]

2602073196 – Alwin [UI/UX Designer]

# data[].attributes.body
We can see here that our application provides real-time feedback which gives users information about their recent transactions.

# data[].attributes.headline
#2: Match between System and The Real World

# data[].attributes.subject
#2: Match between System and The Real World

# data[].attributes.body
As you can see, we do not use complicated languages which ease the user's understanding.

# data[].attributes.body
As you can see, we provided a "back button" to close the hamburger menu in case if the user accidentally pressed the hamburger menu.

# data[].attributes.body
We implemented the hamburger menu on every top left corner of our pages.

# data[].attributes.body
- The user will be able to delete or change bank account information.
- The user will be able to change the user's phone number (OVO, GoPay, etc).
- The user will be able to undo or remove the goals feature.

# data[].attributes.body
Using the principles of emotional interaction and used the color green to indicate "good", and red to indicate "bad".

# data[].attributes.body
Income and expenses comparison graph to make it easier for user to see, rather than calculating manually.

# data[].attributes.body
As you can see here, our UI uses very minimalistic design elements that only show what is necessary.

# data[].attributes.headline
#9: Help Users Recognize, Diagnose, and Recover from Errors

# data[].attributes.subject
#9: Help Users Recognize, Diagnose, and Recover from Errors

# data[].attributes.body
Unfortunately, because the application is still in the prototype stage, we can't add logic to it. Later, in the real app, a validation feature will be added on the "Login page". For example, if the user inputs an invalid email, a prompt will pop up.

# data[].attributes.body
His first reaction to opening the application is to explore.

System Usability Scale [1-10]

1. 4

2. 6

3. 4

4. 3

5. 5

6. 7

7. 7

8. 5

9. 6

10. 4

# data[].attributes.body
Took some time to find some of the functions because it is hidden in the hamburger menu instead of the home page.

System Usability Scale [1-10]

1. 6

2. 7

3. 7

4. 6

5. 6

6. 2

7. 8

8. 6

9. 7

10. 6

# data[].attributes.body
Generally the quickest person to finish the task given by the instructor.

System Usability Scale

1. 9

2. 10

3. 10

4. 9

5. 2

6. 1

7. 9

8. 9

9. Yes

10. 9

# data[].attributes.body
Login

Input transaction

View Mutation

Talk to Pro(s)

Add Goals

Finish Goals

# data[].attributes.body
We will provide a FAQ and customer service system on the finished app.

# data[].attributes.body
1. "I found the system easy to learn."

2. "The system's features were logically organized."

3. "I felt confident using the system."

4. "The system provided clear instructions and guidance."

5. "Using the system was a frustrating experience."

6. "I needed assistance to complete tasks on the system."

7. "The system's interface was visually appealing."

8. "I believe that most people would learn to use the system quickly."

9. "I encountered errors or issues while using the system."

10. "Overall, I am satisfied with the usability of the system."