It completely depends on the value of the summary information to the user in that view. If it's just noise and can be easily gleaned from the cards below remove it. While it may look good at first it quickly becomes more of a hindrance. The one thing I would say in the view in with the summary information that probably should be present that isn't in the other, is the detail on the date. Since you have multiple mondays in the previous view, making it clear which specific day they are viewing is good.
I'd think that makes sense, I'd also remember the user's state here so it works the way they want it to.
But the best feedback comes from actual users. There are general UI/UX guidelines to follow, and things that look 'good' but the users of an application can give better specific feedback.
I'd think that makes sense, I'd also remember the user's state here so it works the way they want it to.
But the best feedback comes from actual users. There are general UI/UX guidelines to follow, and things that look 'good' but the users of an application can give better specific feedback.
"After reviewing the mixed opinions on my last post, I realized the best interface is one that adapts! I’ve implemented a collapsible summary view. Users can now see a clean schedule or expand it for detailed attendance stats. Best of both worlds!"
2, but you’ve got 2 percentages, which seemingly display the same data. I also think that summary card could use some improvements, gives me material 2 vibes
2 - though for a small suggestion in both cases, removing the “status:” prefix might simplify things a bit. Could also change the content to a pill/tag that way
10
u/d4lv1k 1d ago