You’ve built a great system that provides amazing functionality. That said, I’m sure that there is space for improvement. I’ve prepared a few raw ideas that I hope you’ll find useful.

https://www.loom.com/share/2908d0cca0254ea08e614da24afd9f8d?sid=7b18f3cc-8373-4abc-81bf-b30c94ad15af

Since there are three types of navigation to move across the system (side panel, breadcrumbs, dropdown packaging selector, and bottom navigation panel), I guess users struggle with it. My guess is there are a few reasons that make navigation problematic:

• Side-panel navigation and breadcrumbs behave differently.
• Normally, breadcrumbs are allowed to move users only up through the logical hierarchy of a product, but not through the same logical level (like between “Home” and “Project” which are at the same logical level).
• Normally, breadcrumbs also don’t open parts of the system outside of what is presented in breadcrumbs (like a project opens “Project Definition” or a packaging opens “Composition”).

There are many ways how you can fix this obstacle. It seems like removing breadcrumbs would be the most logical step. Since the breadcrumb’s nested structure poorly fits the structure of the system.

Of course, the side panel could be improved as well:

• “New project” button could be removed, since it already exists on the “Home” and “Projects” pages.
• Titles (project and packaging names) could look non-clickable and look different than links to pages (”Rulesets”, “Composition”, etc.)
• Rename the term “Active Project”, because it may create an impression that other projects are inactive or disabled. A few variants for the new term: “Focused Project”, “Opened Project”, “Selected Project”. It also could be replaced with the name of the selected project.
• Rename “Projects” to “All Projects” to highlight the difference between selected and all projects.
• I’m not sure if “Project Definitions” is the best title. The term “project” is currently slightly overused. Maybe “Properties” would be better.

Of course, these are just raw ideas that could be improved. For example, I didn’t mention bottom navigation. Meanwhile, its particular implementation is applicable only for single-path flows and doesn’t work too well in forking flows (cases when there is more than 1 packaging):