Bring leaving space experience in line with Web

[kittykat]

Your use case

Current behaviour on iOS: when a user leaves a space, they do not leave the rooms in that space

User should be able to leave a space without having to leave many rooms individually after the fact. Behaviour should be brought into line with web to offer three options.

• (RELEASE BLOCKER) If not enough time to implement next point, add a note to say that leaving a space will not leave rooms in that space
• (not a blocker, highest priority) If enough time, add option to stay in all rooms and leave all rooms, with a note that there are other options in Web
• (not a blocker) Implement third option to leave selected rooms only"

Have you considered any alternatives?

No response

Additional context

No response

[niquewoodhouse]

@gileluard Just recently (in the last day or so) improved the copy of the leave Spaces so this is a bit out of date. I can take a look and suggest new copy here

[kittykat]

Removing release blocker label as it's no longer a blocker in its current state

[gileluard]

@nadonomy @kittykat here is the actual screen on web:

As you can see, the list of rooms is not displayed if the user doesn't select first Leave some rooms.

We could base the UI on the list of rooms so the user can see the rooms that belongs to this space. Having All rooms and No room options may make things also more flexible especially if the user wants to leave all rooms except one room.

Here is a sample view.

[kittykat]

@gileluard that's a much nicer interaction IMO than having the three options and then choosing later.

Some notes:

• Buttons should probably say "select all" and "select none"
• "space" in "Leave space" should be lower case

[nadonomy]

@gileluard +1 to Kats comments. There's also some other visual & interaction tweaks we should make, things like:

• Considering how the user should interact between All / Some / None.
• Tweaking how scrollviews behave / what persists while scrolling.

Etc.

@gileluard can you remind me of the timeliness/which RC you want to merge this in for? Wondering how to action.

[gileluard]

@nadonomy this is not a release blocker but it's high priority so I would say we'd like to have this feature done for the next RC after this one. @kittykat To confirm.

[kittykat]

If we could have this implemented and tested by 4th April, that would be ideal 👍

[nadonomy]

@kittykat @gileluard great! @amshakal is taking a look at this now, also benchmarking Android to consider cross-platform consistency here on mobile.

[gileluard]

@amshakal I'm almost done with this feature. Let me know if there is something I should change

Also I'm wondering if we shouldn't rather display an simple alert if the space is empty as we display a large empty view in this case:

[niquewoodhouse]

After discussing with @kittykat @fedrunov @gileluard, I've got some alternative designs that aim to:

• Help the filtering make more sense (eg "what does select all rooms" do if I'm filtering
• Reduce some of the ux complexity (eg why does someone need to see a list of all the rooms straight away - on mobile it can be a lot)

These designs aren't comprehensive, just trying to address the largest concerns that came from the meeting - any thoughts welcome and if we have a preferred route, I'll make more comprehensive designs and of course the android equivalent.

Idea 1 As little change as possible

• Remove label and all/none options when filtering
• Change "select rooms" in label to "rooms"
• Wasn't sure what currently happens with the CTA when searching so left it out

ele-ios-leave-space-1.mov

Idea 2 Split the steps

• Removes issues of select all/none options when filtering

ele-ios-leave-space-3.mov

Idea 3 Remove select none

• Its the default option anyway
• Add functionality to top bar (clear + cancel)

ele-ios-leave-space-2.mov

[gileluard]

Thanks @niquewoodhouse

• Idea 1 works for me
• I wouldn't go for idea 2 as it supposes that the users knows the exhaustive list of rooms for this space. That's why we thought to display the list of sub rooms of the space at first.
• Idea 3 works for me. Hopefully, the user won't need to leave all sub rooms very often.

[niquewoodhouse]

Because this feature is already in development, I'd personally lean towards doing as little change as possible, especially as it's not like this is a flow every user will definitely experience. @kittykat @fedrunov does Idea 1 above resolve the issues raised for you?