Suggestions for UX/UI Refinement

[jiangrui2026]

Affected area

Other

Summary

1. The interaction effect here is excellent once found, but the default UI isn't "hooking" the user. It’s hard to tell that this section is interactive.

2. I’d suggest changing the labels on the left to match the original filenames (like Epstein Flight Logs) to pique user interest. The current naming feels a bit vague.

3. Can we add a preview (or some visual feedback) on the right-hand side for single clicks? Right now, single-clicking does nothing and the hover delay is quite long, so users don't know they can double-click or drag-and-drop.

Reproduction steps

Relevant request or job details

[jiangrui2026]

Sorry the label should be enhancement but it seems that I don't have the access to edit it.

[torinkwok]

@jiangrui2026 Agree on the naming. We should switch to more readable, human-style source names @suguanYang. The current labels are too vague.

For the interaction, the current behavior is intentional. We modeled it after desktop file explorers: single click selects, double click opens preview, since that’s already a familiar mental model from Finder and Windows Explorer.

But the affordance is still too weak right now. Users don’t immediately realize the area is interactive or supports double-click. We should polish the interaction feedback and make that clearer.

[torinkwok]

@jiangrui2026 Agree on the naming. We should switch to more readable, human-style source names @suguanYang. The current labels are too vague.

For the interaction, the current behavior is intentional. We modeled it after desktop file explorers: single click selects, double click opens preview, since that’s already a familiar mental model from Finder and Windows Explorer.

But the affordance is still too weak right now. Users don’t immediately realize the area is interactive or supports double-click. We should polish the interaction feedback and make that clearer.

I’ll think a bit more about the interaction design for the second issue and explore a cleaner approach. @suguanYang Let's fix the naming problem first.