-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The new session manager beta is confusing and disorienting #23709
Comments
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
Denis and I had a similar reaction and some of the same feedback in the internal Element product feedback room earlier. Some tweaking was done to the UI, but the global information architecture is still not very clear and a tad confusing, even for me a relatively well informed user. I'm concerned this could lead to a lot more confusing for people who are not "into" Matrix but who just use a product have conversations. |
@janogarcia do you have thoughts on how we could improve this flow? This part seems more severe than the rest because not noticing the button effect would mean not being able to use the feature. |
Agree that the described scenario is lacking some proper feedback. So, I came up with a way to provide visual feedback without requiring us to introduce deeper levels of navigation. So, besides smooth scrolling to the list when there's enough content, now the session list background will be temporarily highlighted (and automatically fade out) each time you act on the "View all (n)" link. Live Demo
It's actually a collection of all other sessions, which can be filtered by verification status (verified, unverified), and inactive sessions (session with 90+ days of inactivity).
We currently can't launch a verification process for multiple targets.
First, there's a bug in the current implementation, where the "Verified session" block for the current session sould be hidden when uncollapsing its details. We show that block to educate users on the importance on verifying your sessions and what that means. Actually, the (now old) screenshot is missing a "Learn more" link for that block. That said, I've added a little arrow shape to the container to better establish the relationship.
We don't consider signing out all other sessions a common use case, that's why it's not being promoted to a primary action and kept as a secondary one instead, given that it's quite destructive. Also you can alternatively perform that action as well in the "Other sessions" list by using the the "Select all" checkbox. So, there's currently two wasy to discover and perform that action. We can always reconsider promoting it as primary action, based on usage and feedback. 👍 Hope all of this give a bit more helpful context. |
I think there is more to this point than needing an arrow trying to connect it to the subject. These blocks that go below the list item start getting a lot more confusing to associate to the right thing when you've expanded multiple items in the other sessions list. It feels like the list item could transform to the block and/or the list item could be the top part of the block itself. Don't take this literally but this is some form a transforming block, https://dribbble.com/shots/3757219-Collapse-And-Expand-Concept And a simple mock-up doesn't even need to move this information around (notice no duplicated block below the list item as it is now): Collapsed: Expanded: |
That's an interesting exploration, but we would need to account for many other moving parts like the selection state etc. It's also worth noting that the example screenshot has some layout/styles issues that make it not follow the intended design spec. For example, the session details container should be indented, with its left edge aligned to the text of the session tile. |
@janogarcia That looks worse than current imo (at least stands out as not right). I can see how it's trying to address the problem with hierarchy though. My point is that the blocks upon blocks and within the list get out of hand.
👍 It's just a mock-up. On the selection state point, I don't think it would need to be any different from current with the checkbox and changing the avatar. We could iterate that point to be even better but it's not something that stands out to me. |
This still looks confusing to me. I don't really understand the indentation, nor why the title "Element Web: Firefox on macOS" is repeated twice. The intended body and the list element with the bottom facing arrow don't seem obviously connected to me. The "sessions" header doesn't seem particularly connected to the elements below it either. The dropdown has an arrow which is at the same place that other arrows below but it does a completely different thing. At first sight it's quite difficult to understand what is happening on this screen |
I agree with the other feedback:
Beside of that I welcome the re-work of the session management 👍 |
@MadLittleMods and I conversed a little more about this in private. We do have a number of people objecting to the current UX now. At the same time, we did have a (greater) number of people not object to the UX during ideation, implementation and testing. This is overlaid by the fact that the session management isn't an area of the app that sees high-profile usage and that once OIDC arrives, it'll move into the OP web interface anyway. Both of these certainly lower my own interest to spend much time discussing this. Personally I do think that overall the UX is good enough though I admit that I'm not a particular fan of the boxes within boxes style either. To prevent us putting more time into discussing this on a theoretical level, maybe it'll be a good next step if somebody submitted a PR showcasing some of the changes that were proposed here. Seeing them side by side and being able to actually try them in a deployment of Element Web might make it easier to reach consensus. |
So, I've been exploring ways to mitigate the last remaining feedback points in a way that would require little/limited engineering effort. It's a mix of early explorations I did while working on the session manager but now accounting for the feedback above. ChangelogImproved visual relationship and hierarchy for session tile and details More obvious/explicit nesting for the session details card, which edges now align to the width of the session tile text contents. Also, I brought the session details card closer to the session tile. Remove redundancy No duplicate session names. The "Rename session" action can now be decoupled from the card heading. @Johennes If moving forward with this, I'd recommend implementing the first variant, given that the second is less visually prominent and could require more effort (moving the edit form to a modal dialog). Minimize chrome/visual noise Removed the divider between the session validation status card and the session details list. ↓ Updated design ↓ Original design for reference The original design was initially ideated to be rendered on a standalone/separate session details view (you would need to navigate back and forth between the session list and the details view). Still, I eventually kept it in context for quicker batch comparison and more straightforward implementation. Other explorationsBorderless card The borderless version goes a step further in removing chrome/noise and helps align the session details text content to the same vertical lines as the session tile contents. We lose the enclosure provided by the bordered card, though. Expanding tile The expanding tile pattern is maybe a bit more visually heavy/complex, but it's something we could easily test live as it's adding just a global border to the "Borderless card" implementation. There are even more explorations on the related Figma file, but I didn't consider them as successful as the three above. Also, a quick note on feedback. When sharing feedback, always remember to ask yourself why it is not working for you — how it's preventing you from moving forward or making it more difficult to understand a specific interaction or piece of information, etc. That can help uncover the underlying issues behind seemingly subjective feedback. |
Your use case
It looks slick but it's horrible to use and understand. The essence of some of this stuff makes sense but it's all put in a really confusing format.
Watching the video of me walking through my confusion is probably better than some of the text to understand (unmute for voice-over):
Element.Session.Manager.Beta.is.confusing.mp4
1. Unverified session security recommendations flow is bogus
Notes:
2. Sections and block UI hierarchy identity crisis
All of these border blocks are confusing.
All of this really seems like it could use this type of Hyperplexed treatment:
3. Sign out all other sessions is under the Current sessions section
There is a Sign out all other sessions action under the context menu in the Current sessions header. But it's hidden away and it's talking about "Other sessions" which has it's own section below. Probably should just have a "Sign me out of everywhere" obvious action somewhere.
Have you considered any alternatives?
Let's compare to the current session management:
Additional context
No response
The text was updated successfully, but these errors were encountered: