Design: Outcome selection pattern (2–N outcomes)

[greatest0fallt1me]

Description

• Create an outcome selection UI that scales from binary to multi-outcome markets.
• Make selection unambiguous and safe on mobile.

Requirements and context

• Must support long outcome labels.
• Scope is frontend design only.

Suggested execution

• git checkout -b design/outcome-selection
• Implement changes:
  1. Define the pattern and when it changes (cards vs list vs table).
  2. Define selection and confirmation states.
  3. Provide examples for 2, 3, and 8 outcomes.

Test and commit

• Validate tap targets and spacing on mobile.

Example commit message

feat(design): multi-outcome selection patterns

Guidelines

• Prevent accidental selection changes.
• Timeframe: 96 hours.

[Agbasimere]

@Agbasimere has applied to work on this issue as part of the Stellar Wave Program's 3rd wave.

Hello there, can I work on this? ETA-3hrs.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Agbasimere to this issue.

[drips-wave]

Congratulations, @Agbasimere! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on March 30, 2026.

🧑‍💻 @Agbasimere: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊