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

Subspace creation UX is confusing in how it avoids using the term 'subspace' #18296

Open
robintown opened this issue Jul 29, 2021 · 3 comments
Open
Assignees
Labels
A-Spaces Spaces, groups, communities A-Subspaces Spaces which are inside other spaces O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect X-Needs-Design

Comments

@robintown
Copy link
Member

As a user, I find it slightly confusing how the subspace creation UX avoids using the term 'subspace' entirely. In particular, these are the two points in the UI that feel the most incongruous:

Screenshot 2021-07-29 at 11-03-29 Element The Spaces feedback space

When creating a subspace, seeing this image causes me to think "wait, am I creating the same space again, or something?" I feel that changing the wording to "Create a subspace" would make it more clear what's going on, namely that I'm creating a space to be nested inside the Tỏaq space. "Add a space to a space" sounds a bit strange as well.

Screenshot 2021-07-29 at 11-19-54 Element general

Additionally, it feels strange that this menu says "Add space" instead of "Add subspace", since the current wording makes it less clear that the new space will be nested. The discussions in matrix-org/matrix-react-sdk#6458 mentioned a folder/file explorer analogy, though I think one reason that file explorers can get away with saying "Add folder" rather than "Add subfolder" is because in order to get to that action, you have to go inside a folder and click on the blank space within that folder, rather than clicking on the folder itself. The placement of the interaction itself makes it clear that nesting will happen, whereas the space UI has this interaction placed alongside the parent space.

This is of course general, subjective feedback, and can very likely be addressed in ways other than what I've suggested.

@robintown robintown added T-Defect S-Minor Impairs non-critical functionality or suitable workarounds exist A-Spaces Spaces, groups, communities Z-Subjective labels Jul 29, 2021
@novocaine novocaine added the O-Occasional Affects or can be seen by some users regularly or most users rarely label Aug 19, 2021
@mattdm
Copy link

mattdm commented Sep 4, 2021

An alterantive might be "Add nested space"

@niquewoodhouse
Copy link

niquewoodhouse commented Sep 16, 2021

Thanks @robintown for the detailed issue. They used to be called subspaces and it was changed to spaces for the following reasons:

We decided to change it to spaces and see what feedback comes, so thanks for raising this.

Are all the thumbs up so far coming from people familiar with the previous phrasing?

Even if so, I'm personally fine with changing it back to subspaces. I can see it's something used on gmail to add a label to a label so that gives me more confidence its not a jargon term.

image

@mattdm
Copy link

mattdm commented Sep 16, 2021

It might be useful to test this and some other options with a non-English-first audience. To me, "subspace" seems perfectly intuitive, but I can see a number of reasons it might actually be confusing to people.

@t3chguy t3chguy added the A-Subspaces Spaces which are inside other spaces label Jan 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Spaces Spaces, groups, communities A-Subspaces Spaces which are inside other spaces O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Defect X-Needs-Design
Projects
None yet
Development

No branches or pull requests

6 participants