Design Reviews - joeriBouwman25/bubble-machine GitHub Wiki

🖌 Design Reviews

Week 2

Joeri & Remco

In the second week because of a planning issue we both had a design review with Sanne at the same time. We showed the designs of the UX students and some first graphs we made during the first week.

Hiding content is a good idea, but show the content that is important. Think of the buttons for:

  • play/pause
  • next step
  • parameters,

These are so important that they can remain in the picture.

Hide the elements with a transition so that it becomes clearer to the user that there is content on the screen. The challenge here is that you have to ensure that the content does not blink, but remains hidden until the mouse is actually moved.

A zero state with explanation is useful, see how you can add this.

Spend more time on the actual visualization of the data, this is the most important part of the assignment, so that is where the focus should be the most.

See if you can visualize a filter-bubble as an actual bubble when it arises.

“Dingen als menuutjes, lekker boeiend, dat is niet waar jullie opdracht over gaat”

Nora

Feedback UX review week 2

  • What is the goal of using of using code in this case? What does it add to the application? Why not make the protype in Adobe Xd?
  • Make different data visualisation based on the same dat, this way you can show different patterns in the dataset and highlight them.
  • The simulation is vague at this point because you can not "see" yourself in it. We could work on highlighting a specific user in the simulation to see its links between other users and documents.
  • Start onboarding when you work on the Simulation instead of before - none one is going to read it
  • Explain the model by letting the user do something
  • Is there a clear goal or end to the simulation? When is the simulation done?

Remco

I missed this week's design review because I wasn't feeling too well. I asked my teammates about the feedback they received.

Tim

This week I had the first code review with Robert. I showed the prototype I had made and found the result nice. How I explained the project was not so smooth. He said that I could improve on that. The reason I could not explain it so well in the first week whas because I didn't understand the project and the data it showed.

Week 3

Joeri

This week I had a design review with Vasilis

The slide-out menu is not a pleasant UX experience, then there is little content in the expandable harmonica, so why would you let it expand if there is little content?

It might be a good idea to cluster the different parameters by species. Get inspiration from tooling programs such as Adobe.

For the data visualization, I would recommend that you look into the Data Visualization books. You can find this on the 3rd floor of the TTH, or you can ask Jan Jaap or Maaike.

Nora

Design review week 3

  • This will create a good base to explain onboarding.
  • Is the visualisation clear to the user?
  • Do they know what is going on? What is the goal of the simulation?

Tim

This week I showed the prototype I built from the data of the API. The feedback here whas to explain the project better next time. I als showed a design I had made with bubbles stacked on top of each other. He found the different layers interesting and suggested using blend mode to blend the layers better instead of opacity.

Week 4

Joeri

I've missed the third Design review because of a wedding. I made an agreement with Justus about this issue.

Nora

The final design review was with Vasillis. I had questions about the onboarding screens, how do I make sure people understand what is going on? From the design I got sent by the UX students it did not seem very clear to me what was going on, or that other would understand and read it. The onboarding had large amounts of text that was dense with information and terms. I got the advice to test the onboarding with the target group, ask around at the HVA if you can explain the application to people and see if they understand. this is the base for writing a good explaination of the model.

Remco

During the last design review, I had a meeting with Vasillis, during the meeting I showed him the latest design, not knowing that later in the day the UX-students would show up with a revamped design. I had some questions regarding how to display the parameters and some design solutions for information that wasn't displayed in the UX-students designs.

Regarding the parameters, he rightfully noted that the current display of parameters didn't do justice to the bubble-machine. What you would like to see is all the different parameters that you can play with. So in the current iteration it only showed one, and when you clicked on a different one it would hide the previous one. He gave some hints, one of them was to look at how Adobe uses all their different options and how they are displayed and when you play with them the immediate effect the user can see.

Then, regarding some graphs that were made that weren't displayed in the UX design. Vasillis noted that you can make a small display graph, but it should never interfere with the main graph.

Tim

This week I had a design review with Sanne. The feedback that I have gotten is that it is not logical for a new user what this project can do. Now I have to explain to people what it is that you're looking at without me explaining. Tips I have gotten are adding a legend to explain the items. The second graph I showed was also not simple to understand because you didn't know what the data mean on the X and Y asses without me explaining. The two graphs didn't als match with colours so that made people confused if they are connected.