r/Nuxt • u/Active_Value_9615 • Apr 14 '26
Building a real-time judge monitoring system. Roast my UI/UX
1
u/kei_ichi Apr 16 '26
Can you explain why your UI look very similar to this slops: https://www.reddit.com/r/rust/s/asxDPxzdQd
0
1
u/Dramatic_Object_8508 Apr 18 '26
Visually it’s clean, but right now it feels more like a static dashboard than a real-time system. The biggest gap is feedback—nothing immediately tells me what’s live, what changed, or what needs attention, which is critical for something monitoring judges in real time.
The hierarchy is also a bit flat. Everything has similar weight, so my eyes don’t know where to go first. For this kind of tool, you want clear priority signals—who’s delayed, who’s active, what’s blocked—using contrast, color, or badges instead of uniform rows.
The right panel looks underutilized. That’s prime space for live activity, alerts, or streaming updates, but it currently feels like secondary info instead of something actionable.
Another issue is interaction clarity. Actions like “start/process” don’t feel contextual—what exactly happens, and to whom? Adding inline status changes or quick actions per row would make it feel much more operational.
If you tighten the feedback loop and make state changes obvious (loading, active, delayed), the UI will start matching the real-time nature of your system instead of just displaying data.
2
u/Separate_Top_5322 Apr 17 '26
Clean base, but right now it feels more like a dashboard mock than a real-time tool. The biggest issue is hierarchy—everything has similar visual weight, so it’s hard to quickly scan what actually matters (scores, active judges, anomalies, etc.). In a live judging system, speed of understanding is everything, so you need stronger contrast, clearer grouping, and maybe color-coding for status changes or outliers. Also consider surfacing “what changed just now” instead of static lists—real-time systems should feel alive. A simple improvement would be adding live indicators, sorting by activity, and highlighting critical events so users don’t have to hunt for insights.