Pulse - Inventory Management System Design

I like how you did research and designed this complex system! Incredible job! Everything looks simple and clear, and using the Shadcn design system is a great choice it makes development much easier later. The flow is well thought out, and the tabs for each product show important information step by step without overwhelming the user.

Since this is a complex dashboard, here are a few things to double-check:

• In a gym or warehouse, lighting can be poor and users are often on the move. I’d suggest adding distinct icons to your status tags (like a checkmark for "Available" or an alert for "Overdue") so they are instantly recognizable without having to read the text.
• The barcode scanning screens look good, but check the button placement at the bottom. When users hold a phone with one hand and equipment with the other, those buttons should be very easy to reach with a thumb.
• For the mobile scanning flow, it’s important to consider non-visual feedback. Adding a note about haptic (vibration) or audio confirmation after each successful scan would make the "batch mode" much more reliable in a busy environment.
• The "Member Reliability Score" is a great feature. You could take it further by adding a "Safe Check-out" trigger. For example, if a user has a very low score, the system could automatically require an extra confirmation from an admin before releasing expensive equipment.
• Since staff might be busy or wearing gear, consider adding a "voice memo" option for damage reports. It’s often faster to record a quick comment than to type it out on a phone screen while holding equipment.
• You have many status tags (Available, Maintenance, Overdue, Lost). Make sure the colors have enough contrast against the background and that they are easy to distinguish for colorblind users.
• In a big database, the search bar is the most used element. Maybe add more specific filters (like by "Storage location" or "Assisted by") right next to the search to make finding assets even faster.

Overall, it’s a very professional and solid project. Keep it up!

Hi! 👋

Pulse is an impressive project for a 28-hour sprint. The system is very clear, and the keyboard-first approach perfectly addresses the need for speed at a busy front desk.

I love how the side panel allows for detail viewing without losing the list's context.

I agree with Anastasiia’s suggestion about status icons. It will boost recognition in high-traffic environments. The "Member Reliability Pulse" is a smart way to handle damage disputes. While some error states in the scanner are missing, the overall quality is great.

This is a solid foundation with huge potential. You have a sharp eye for balancing functionality with clean UI. Keep pushing it forward. You’re definitely on the right way! 🫡❤️

I think the project looks really polished, especially considering it was done within a 28-hour hackathon. The visual direction feels strong, clean, and consistent, and the overall interface looks very focused and easy to scan.

I really liked the idea of combining a desktop dashboard with a mobile scanning flow. It makes sense for this type of product, because staff probably need to move quickly between checking equipment in and out, scanning items, and confirming everything on the dashboard.

The product also feels practical! Features like bulk check-ins and checkouts, barcode scanning, item history, damage logging, and automated reminders all seem relevant to the problem space. They make the concept feel like it could actually help teams manage equipment faster and with less manual work.

Visually, the presentation is one of the strongest parts. The typography, spacing, dark/light sections, and overall branding make the product feel modern and professional.

One thing I would improve is the beginning of the case study. I wanted a bit more clarity around the original hackathon challenge: what was the brief, what was given, and what did you define yourself? Right now, the final solution is clear, but the starting point is a little hard to understand.

I also think the pain points could be backed up more clearly. They make sense, but I would love to see a bit more evidence behind them — for example, what came from competitor research, user reviews, or your secondary research. That would make the insights feel stronger and more grounded.

Another thing I would add is a sharper problem statement. The solution is presented well, but the main problem could be stated more directly, something like: staff need a faster and more reliable way to check equipment in and out, track item history, and handle damage or overdue returns without relying on slow manual processes.

Since this was a hackathon, I would also be interested to see how you prioritized the work. For example, why did you choose these three core flows? What did you decide to leave out because of the time limit? That would make the design process feel more intentional.

Overall, I think the concept is strong and the presentation looks really polished. I would mainly improve the storytelling around the brief, research, and decision-making process so it’s easier to understand how you got from the problem to the final solution.

I’m also adding a link to one of my projects here. Since I reviewed yours, I’d really appreciate it if you could take a look and share your feedback as well:)

https://app.uxcel.com/showcase/solar-system-dashboard-utility-585?utm_source=share-brief-project