2 deleted 117 characters in body
source | link

As you know, you have to collect a combination of checkbox-style selections, and a filtered list of radio-style selections.

Combine them both into one list. Checkboxes enable the primary "radio button" (a star in this mock up, but fit it to your design).

List allowing checking many, but marking one as primary

Usually people tend to steer away from having a list of radio buttons with no default selected, but in your case, a "default primary" may not make sense, so that's why I chose not to use literal radio button elements, and instead chose stars.

Clicking a star replaces the primary selection, as a radio button would do, allowing only one star at a time. It may feel more comfortable for your users to want to unstar an item before starring the next. No big deal, let them do that, and enforce your requirements at the end.

If the list is long, maybe statically reproduce the designated "primary" option at the top.

Keep in mind that it may be difficult to communicate your requirements strictly through the input methods alone, without it being quite redundant (e.g. reproducing the list of enabled items).so I'd add a bit of instructions to make your user aware of how to make their selections, but also and fall back on some validation if they try to submit an incomplete selectionat the end.

As you know, you have to collect a combination of checkbox-style selections, and a filtered list of radio-style selections.

Combine them both into one list. Checkboxes enable the primary "radio button" (a star in this mock up, but fit it to your design).

List allowing checking many, but marking one as primary

Usually people tend to steer away from having a list of radio buttons with no default selected, but in your case, a "default primary" may not make sense, so that's why I chose not to use literal radio button elements, and instead chose stars.

Clicking a star replaces the primary selection, as a radio button would do, allowing only one star at a time. It may feel more comfortable for your users to want to unstar an item before starring the next. No big deal, let them do that, and enforce your requirements at the end.

If the list is long, maybe statically reproduce the designated "primary" option at the top.

Keep in mind that it may be difficult to communicate your requirements strictly through the input methods alone, without it being quite redundant (e.g. reproducing the list of enabled items). I'd add a bit of instructions to make your user aware of how to make their selections, but also fall back on some validation if they try to submit an incomplete selection.

As you know, you have to collect a combination of checkbox-style selections, and a filtered list of radio-style selections.

Combine them both into one list. Checkboxes enable the primary "radio button" (a star in this mock up, but fit it to your design).

List allowing checking many, but marking one as primary

Usually people tend to steer away from having a list of radio buttons with no default selected, but in your case, a "default primary" may not make sense, so that's why I chose not to use literal radio button elements, and instead chose stars.

Clicking a star replaces the primary selection, as a radio button would do, allowing only one star at a time. It may feel more comfortable for your users to want to unstar an item before starring the next. No big deal, let them do that, and enforce your requirements at the end.

If the list is long, maybe statically reproduce the designated "primary" option at the top.

Keep in mind that it may be difficult to communicate your requirements strictly through the input methods alone, so I'd add a bit of instructions to make your user aware of how to make their selections and fall back on some validation at the end.

1
source | link

As you know, you have to collect a combination of checkbox-style selections, and a filtered list of radio-style selections.

Combine them both into one list. Checkboxes enable the primary "radio button" (a star in this mock up, but fit it to your design).

List allowing checking many, but marking one as primary

Usually people tend to steer away from having a list of radio buttons with no default selected, but in your case, a "default primary" may not make sense, so that's why I chose not to use literal radio button elements, and instead chose stars.

Clicking a star replaces the primary selection, as a radio button would do, allowing only one star at a time. It may feel more comfortable for your users to want to unstar an item before starring the next. No big deal, let them do that, and enforce your requirements at the end.

If the list is long, maybe statically reproduce the designated "primary" option at the top.

Keep in mind that it may be difficult to communicate your requirements strictly through the input methods alone, without it being quite redundant (e.g. reproducing the list of enabled items). I'd add a bit of instructions to make your user aware of how to make their selections, but also fall back on some validation if they try to submit an incomplete selection.