Live Sports Betting PlatformLive Sports Betting Platform

The hard requirement

In-play betting is a real-time financial system wearing a sports interface. Odds change by the second, thousands of users act on them simultaneously, and every one of those actions has to settle correctly. Approximately right is not a category that exists here.

What we built

• Native SwiftUI client with live odds across multiple leagues
• Odds distribution to many concurrent clients with bounded latency
• Transactional bet placement that cannot double-settle or partially apply
• Full audit trail on every state change
• Responsible-gambling controls: deposit limits, self-exclusion, session reminders
• Age and identity verification at account level

Concurrency is the whole problem

The interesting failures are all races: two bets against odds that changed between display and submission, a settlement arriving while a cash-out is in flight. These are resolved with database transactions and idempotency keys rather than optimism, because the alternative is discovering the bug from an accounting discrepancy.

Why native

The odds board updates constantly and the list is long. Sustained high-frequency updates across a scrolling view is exactly the workload where a cross-platform bridge starts dropping frames - and a stuttering odds board undermines confidence in a product whose entire value is being current.

Regulatory features are product features

Deposit limits, self-exclusion and session reminders were built to the same standard as the betting flow. They are legally required in most jurisdictions, and treating them as a compliance checkbox is how they end up broken.