Skip to content
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

Learning curve for groups is fairly high #5246

Closed
turt2live opened this issue Oct 11, 2017 · 12 comments
Closed

Learning curve for groups is fairly high #5246

turt2live opened this issue Oct 11, 2017 · 12 comments
Assignees
Labels

Comments

@turt2live
Copy link
Member

Description

Having the experience of understanding the direction of groups made the climb a little bit easier for myself, however in a quick trial of a number of "regular users", everything fell flat.

I explained how to enable group support, then left them on their own to figure it out. Here's some of the comments/noticable problems:

  • People kept clicking the "Add featured user" button to invite someone to the group
  • People kept clicking the "Add featured room" button to add a room to the group
  • People did not understand how flair worked at all
    • Someone found the "Publish" button and clicked it, starting a downhill spiral as to how to make it work
    • Expected to see flair in rooms that were "featured" or part of the group in general - didn't bother to look at the individual room settings
    • Didn't understand how to customize it (wanted a different icon from the group icon)
  • Lots of problems with the bugs I've reported up to this point already

Overall, the introduction kinda flopped. People were excited about the groups in general (yay!) and flair when they found it, but towards the end it required a lot of coaching to get help them along. I'm not sure how to resolve some of these issues, but maybe this can help work out some of the bumps.

Version information

  • Platform: web (in-browser)
  • Browser: Chrome 61
  • OS: Windows 10
  • URL: riot.im/develop
@lukebarnard1
Copy link
Contributor

This is valuable feedback, thanks @turt2live

@lampholder
Copy link
Member

Thank you so much for this, and the rest of your feedback. My triaging fingers are bloody stumps from working through it all, but it's hugely valuable 😆

@lampholder lampholder added T-Defect P1 A-Spaces Spaces, groups, communities ui/ux labels Oct 12, 2017
@turt2live
Copy link
Member Author

No problem! As groups progress, I'll continue throwing people in the deep end and seeing how it goes :)

@lampholder
Copy link
Member

lampholder commented Oct 12, 2017

Okay, we've discussed a plan to mitigate the above.

For clarity, the objective of this plan is to get a first cut of groups out in front of all users as quickly as possible. What this means is:

  • we won't have all of the features implemented, but the subset that is implemented will be useful
  • users will be able to use the features without training. This might be achieved through great UX design, or it might be achieved through putting elabourate descriptions on things or through providing multiple routes to achieve the same result.

This doesn't have to be our forever UX - it just has to be simple and workable.

Okay so what is the plan?

And yes, we are cutting a lot back here, and losing some of the (perhaps most) useful bits about groups, but we're optimising for useful soon rather than complete/perfect later 🙂

@lampholder
Copy link
Member

I would also like to suggest (though this hasn't been discussed with anyone) moving the 'leave group' and 'publish/unpublish' UX into the group settings.

For better or ill, you leave a room by going into the room settings.

Publishing/not publishing could be a checkbox rather than a button

@turt2live
Copy link
Member Author

Part of the confusion around rooms and groups is the association. Adding a room to a group (via GroupSettings) doesn't seem to do much, but adding a group to a room (via RoomSettings) makes flair work. Is there a plan to also mitigate this confusion?

@turt2live
Copy link
Member Author

Overall I quite like the plan, even if it does mean losing some features. Hopefully some rapid development post-launch will recover the lost features ;)

@lukebarnard1
Copy link
Contributor

@turt2live

When User A adds room B to group C, automatically try and add group C to the 'Related Groups' room config for Room B (obviously only succeed if User A has the right power level in Room B)

@turt2live
Copy link
Member Author

oops, thanks for pointing that out.

@ara4n
Copy link
Member

ara4n commented Oct 12, 2017

what is the rationale for removing the join group button?

@turt2live
Copy link
Member Author

Currently it doesn't do anything. If it won't do anything by launch time, it feels broken and imo shouldn't be there, until it does something.

@heyakyra
Copy link

heyakyra commented Oct 18, 2017

With a hopefully solidifying featureset, Riot could probably use a UX overhaul generally. Not sure if a meta-ticket exists for that, but even before groups lots of UI oddities existed such as placement of notifications/user list/etc behind the same sidebar.

Edit: here's the UX general issue #2984

Edit 2: there's one specific to groups/communities as well #4430

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants