I am working on a feature where the user can start a video recording of a YouTube live-stream. The feature is per default disabled. A required input for the recording to work is to select which stream quality it should record from (e.g 480p, 720p, 1080p).
To clarify, the system fetches the video stream of the selected quality directly from YouTube. It does not do any compression or post-processing itself.
I have two options of how to implement this feature, but I'm not sure which is best from a UX-perspective. I have also listed what I consider to be the pros/cons for each, but I could be wrong or have missed some.
Option 1 - On/off integrated in dropdown
To enable the feature, the user selects a resolution from the dropdown. The default option is "disabled".
What I consider as pros/cons:
+
The feature can never be enabled without also setting the desired resolution.
-
No clear hierarchy of which controls are disabled as a result of the whole feature being turned off.
-
Putting the "off" option in a list of resolutions.
-
Changing the selection from "disabled" to a resolution does not explicitly communicate that the feature is now enabled.
Option 2 - On/off a separate control input
To enable the feature, the user first toggles the switch control. This enables the feature with the resolution that is first in the dropdown. Changing resolution is a separate control.
What I consider as pros/cons:
-
The feature may run (albeit for a second) for a resolution the user does not want, until changed.
+
Clearer which is the top-level input that controls the whole function.
+
The dropdown has only resolution options, and is thus "cleaner".
Very grateful for thoughts and input on each. Also very thankful for suggested alternative solutions.
Edit: By "record" I mean save to disk, aka download. (I'll figure out the wording later)