Skip to content
All case studies

Sportsbook features at ComeOn

Building betting features that have to be fast, clear and correct for players in three languages, as the main frontend developer in my team.

Role
Frontend developer
Timeline
Apr 2024 — now
Stack
React · Next.js · TypeScript

01 · The problem

Complex bets, simple screens

Features like Boosted Odds and Bet Builder pack a lot of rules into a small screen. Players need to understand what they’re getting at a glance, in English, Brazilian Portuguese or Austrian German.

02 · Constraints

What made it tricky

  • Three locales in every release: EN, PT-BR and DE-AT
  • Designs arrive in Figma and need to become responsive, accessible components
  • Components get reused across features, so they have to be flexible and documented

03 · Options

How to build it

  • One-off screens

    Quick for a single feature, but every new feature starts from zero.

  • Chosen

    Reusable components + docs

    More work up front, but each feature makes the next one faster.

04 · Decision

Turn client problems into building blocks

“I start from the client’s problem, not the ticket, and leave behind components and docs the whole team can reuse.”

05 · Outcome

What changed

  • 3languages in every release: EN, PT-BR, DE-AT
  • 2026Make It Happen award, ComeOn Summer Awards

I can’t share internal numbers or unreleased screens, but this work earned me the Make It Happen award at the ComeOn Summer Awards 2026.

06 · What I learned

Listening is a frontend skill

The best solutions came from asking one more question before writing code. Translating a client’s problem well matters as much as translating the UI.

Keep reading