Radio Buttons - changing langauage

I get that Radio Button using Option Sets cannot be translated into a users local language.

So to get around this I’d like to use a static radio button set.

Gemini says that we can use:

“Bubble allows you to access the list of choices you defined on the element. To check if the user picked the first option:

  • Workflow Expression: RadioButton A's value is RadioButton A's Choices:item #1"

However there seems no way to actually address a particular ‘choice number’ in the radio button static choices without referring directly to the actual English Text.

Has anyone solved this? It would be so useful if Bubble allowed us to reference the choice number.

Many thanks.

Your approach is correct, you just need to reference the element’s own choices list in the expression. To check if the first option is selected, your workflow condition should be `YourRadioButton’s value is YourRadioButton’s choices:item #1`. This dynamically gets the text of the first choice, whatever it is, and checks if it’s the one selected

Thanks, but what I need to do is find a way to reference the actual position. I’m building a multi-language app and wanted to use a radio button element with static choices, say ‘apple’. ‘pear’, ‘banana’ so these translate when user is in another country, But the workflow need to be ‘when radiobuttons A’s value is choice #1…’ rather than ‘when radiobuttons A’s value is ‘apple’. That way the WorkFlow will continue to work even if the static choices change with the local language.

Hope this makes sense - I can’t find a way to address ‘choice #1’ without referring to the actual text of choice 1.

If you know a way do let me know, thanks.

Static radio choices are just text, so Bubble can only compare them by the text you see. If you need language switching, store a stable key instead of the label.

Two simple ways.

Use an Option Set anyway, but add attributes. Example: key (A, B, C), label_en, label_fr. Show RadioButton choices as Option Set’s label in the current language, then save the key. Your workflows compare by key, not by label.

If you really want static choices, create a tiny data type like RadioChoice with fields key and label, and load the repeating list as the choices source. Same idea, display label based on language, save key.

That gives you translations and clean conditions without relying on the English text.