Stack Report for OpenShift.io
A system to analyze and improve application stack by suggesting a better alternative and additional dependencies/components.
Project Type & Deliverables
UI Prototype (Invision)
Visual Design (Sketch)
My Role — UX Design Intern
Project Duration — 5 Months
Red Hat OpenShift.io is a highly collaborative open-source, web-based application lifecycle management (ALM) solution.
It is a next-generation product for developers to manage the development lifecycle with one efficient tool. It enables you to plan, create, and deploy hybrid cloud services.
For OpenShift.io, we wanted to build an analytics system that provides meaningful insights on users' application stack that will help them build applications without any stack issues.
[Application stack: A set of libraries and components/dependencies used by developers to build product/application.]
What was my task/work?
As a UX Design intern, my job was to understand the product "OpenShift.io and Stack Report" and create an end-to-end experience.
What was the problem?
Even though we had the technology to provide analytics for application stack, we could not offer helpful insights to users, and because of that, improving user experience of the analytics system was necessary.
The stack report was already present in the OpenShift.io before I started working on it, but it was in the initial phase. When the developer built that report, there was no design team involved since it began as a small project that later turned into a more significant part of OpenShift.io.
We discovered four pain points
Pain Point 01
Security issues in the application stack
We were facing difficulties in monitoring and eliminating security issues of an application stack to the users.
Pain Point 02
Conflicts between the component licenses
We were facing issues to show component licenses that conflicts between each other in the application stack.
Pain Point 03
Lack of insights on the application stack
We could not show application stack insights effectively to the users due to a lack of information/data.
Pain Point 04
Understanding the purpose of Stack Report
Users could not understand the real purpose of a stack report and how it can help them build applications in OpenShift.io.
The stack report provides comprehensive information regarding your application stack, and it's component libraries that help you make informed choices. It analyzes your stack and recommends alternate and additional components to improve your application.
Skip to Design Process
Using Security Issues, users can remove/update affected dependencies, which would help them resolve application issues.
In the Licenses page, users can update affected dependencies by using alternate (suggested) dependencies.
Insights on Stack
The confidence score helps users decide whether they should use alternate (suggested) dependencies. Also, providing feedback supports the system to provide better recommendations.
Users can check the status of all dependencies by looking at the "Dependency check" column. It will help the user make decisions quickly.
How does this design solve the problem?
Users can check status just by looking at those four cards (Overview tabs). Also, on the list, we are showing status and giving significant information upfront.
In this design, we are showing security issues with the CVE score upfront to make a decision as soon as possible.
We are showing how many conflicts are present in a stack and how the user can solve it by using our suggested alternate component.
In this design, we also focused on stack insights. Users can check and update the stack based on the insights we are providing.
Each selective card (Overview tabs) except "dependency details" has an alert indication on the top-right corner with color showing the alert level.
Outcome & insights from this project
This project was successful. We tested this project in Red Hat Summit (Red Hat Annual Conference) during the workshop session with our users, and we got a positive response. Users gave feedback on the overall UX and tech used behind the stack report.
The user understood the purpose of the stack report and how it can help them. Users also shared how we met their expectations and what we can improve on the data and tech side.
Since it is an ongoing project and due to NDA, I can't share more insights on the outcome, but feel free to discuss it with me.
Thank you for reading this project
Also, check out these awesome projects