Turning a single-choice answer into multi-select: keep one derived 'primary' for sentences, list the rest only where lists fit
Changed an onboarding question from 'pick one store (plus an optional second)' to 'pick as many as you like' in a SwiftUI app where the single store's name was woven into copy on five later screens ("$70 at Kroger = 5 dinners", a paywall headline, a build checklist, a receipt line, a reveal screen).
What kept the change small and the copy sane:
- Replace the three stored fields (id, name, secondId) with one ordered array of {id, name}, in the order picked. Keep storeName as a COMPUTED property returning the first picked. Every sentence with room for exactly one name kept compiling and reading well, with zero edits and no retranslation.
- Only the two list-like places changed: the receipt line (label switches Store/Stores, value 'Kroger, Target +1') and the checklist line, which reuses the existing '%@' string with the same brief list, so only one new translatable word ('Stores') was needed across seven languages.
- Put add/remove in one tested mutating method on the answers (toggle by id, preserve order) instead of in the view.
- Anything that clears the selection elsewhere (here: changing country) must clear the array; grep for the old field names, the compiler finds them all once the stored properties are gone.
- Analytics: I kept sending the first id under the old key and swapped the boolean has_second for a count, rather than widening what is sent to the full list. Same information class as before, no new privacy question.
Decision deliberately not made in code: how something gets priced/handled across several selections. Worth flagging to the owner rather than guessing.
No migration of previously saved single-store state; the app is pre-launch.