Re: [mediacapture-screen-share] Multi-capture (concurrent capture of multiple surfaces) (#204)

I think this idea presumes too much about application logic, which is seeping into browser UX here:
1. it assumes order doesn't matter
2. the UX presented ignores the question of whether to include audio or not for each user choice
3. users have no way to correlate choices made with their role in the application
4. it doesn't handle duplication well (users wanting the same choice for multiple roles in the application)
5. it assumes to some degree that users will make all their choices at once (can't revisit picker with the same choices)

Picking, or more broadly _managing_ multiple things is a problem best dealt with in the context of an application IMHO, and the above problems are ones that [picking one thing at a time](https://jsfiddle.net/jib1/L53psjyr/) in the context of the application doesn't have.

I think hyper-focusing on the initial picking rather than management skews the value-add of a monolithic picker like this. It's not going to save the application from needing to design a place where the user can manage the multiple choices made, but might lead some applications to _think_ they can skip that by instead leaning on calling this picker again, expecting the user to check the boxes over and over, rather than let them edit an existing choice (which my fiddle above allows btw).

I think picking multiple things outside of the context of an application isn't very webby, a bit of an anti-pattern on the web.

> The user is liable to make mistakes when trying to remember which surfaces they've already started capturing

My fiddle has thumbnails. Also, as mentioned at the meeting, browsers could highlight already-captured choices in the UX today without a spec change, if they think this information is useful. This wouldn't rely on the user making all choices at once.

-- 
GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/204#issuecomment-1040879380 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 15 February 2022 22:55:28 UTC