Styling and Learning

This week I began creating the style guide for the Podman desktop application. I started a LinkedIn learning course on UX weekly - learning how to interact with cross-disciplinary teams as a UX designer/researcher. I also iterated on the design of the registry page.

I redesigned the registry page so that each registry was separated with lines, I think it made for a cleaner design. Also, the container list page is delineated with lines so this design correlates with the rest of the application. The users could add a new registry with the button at the bottom of the page.

I like the design, I think it's very simplistic and it allows the user to add a registry easily. However, when add registry is selected, it seems that the page is overloaded with buttons.

So I came up with another design that simplifies things a bit more.

I think the second design reduces the number of buttons visible to the user, it's less overwhelming in that sense. Also, the user can collapse the drop-down when they want to.

The issue I see with this design is how the page will work with a scrollbar; when a new registry is added, the user will want to see their newly added registry to be sure that it was added, and scrolling to view this registry complicates the user experience.

I began a LinkedIn course called UX weekly where Drew Bridewell takes us through his day as a UX researcher. He teaches valuable lessons like what is expected of a UX researcher, the most important skill is "learning". He also touched on how to communicate with your team; how to discuss your designs and get valuable feedback. It's very useful content.

I began writing the style guide for the podman desktop application. The structure of the document is coming together nicely. I will have to discuss its content with M to finalise it.

Next Up

I will continue working on the mock-up prototype for the registry page but before I go further I would like to get M's thoughts on it. I will continue working on the style guide mainly on the structure of it, the details can easily be changed later on. I will continue learning to improve my skills as a UX researcher. I will look into joining a team that works with Flask.