Re: [mediacapture-main] "user-chooses": Does required constraints make any sense now? (#669)

If we go with a device picker, we should design it for the best user experience, from scratch.
If we have to update the API to make sure the user experience is great, we should probably do it.
Once we have a good model, we should think of the transition plan.

> Last point: I don't think a transition plan to a more limited API will succeed.

It depends. You could always reduce the power of the old API, for instance by only selecting the default devices with the old API (after some deprecation time) and using constraints as ideal in that case.

Also, I doubt that the fact of modifying how we handle constraints will be seen as a more limited API. I might be biased but to me, constraints are over-complex and sub-used. Simplifying constraints would be beneficial.

GitHub Notification of comment by youennf
Please view or discuss this issue at using your GitHub account

Received on Tuesday, 24 March 2020 11:06:31 UTC