The thing that makes BetMGM different from a normal Android app is that it is real-money and licensed per US state. Legal online gambling is granted state by state, so the app is gated by device geolocation: before a bet is enabled, a location check has to confirm the user is physically inside a licensed jurisdiction, and the same binary changes its available markets and rules depending on where it runs. That is why most of the product complexity lives in compliance, identity, and payments rather than only in the betting screens.
I contributed to that native Android app, one of the leading regulated sports betting and online casino platforms in the United States. It pairs a full sportsbook (pre-match and live in-play markets across major US and international sports) with an online casino of slots, table games, and live-dealer tables, all inside a single app, plus the account, deposit, and withdrawal flows that state gaming regulations demand.
Where the engineering pressure sits
Every betting action is conditioned on where the user physically is and which state license applies, so geolocation, KYC identity verification, and responsible-gaming tooling (deposit limits, time-outs, self-exclusion) are first-class parts of the flow, not afterthoughts. The bet slip has to keep odds, stakes, and payouts consistent with a fast-moving server-side source of truth. Settlement and wallet updates have to be reliable enough that users trust the balance they see. And the app has to do all of this while adapting its markets and rules to the jurisdiction it happens to be running in.
Product surface
- Live in-play betting: real-time odds that update as games unfold, cash-out on eligible open bets, and a continuously refreshing market list driven by live event data
- Bet slip and parlays: single, parlay, and Same Game Parlay construction with live stake, odds, and potential-payout calculation, plus parlay and profit-boost token redemption at the slip level
- Online casino and live dealer: slots, table games, and streamed live-dealer tables surfaced through casino lobbies, search, and category browsing, embedded alongside the sportsbook
- Account, deposits, and withdrawals: KYC identity verification, multiple deposit and withdrawal methods, and responsible-gaming controls
- Geolocation and multi-state compliance: mandatory location checks with jurisdiction-specific markets, rules, and content
- Live scores and bet settlement: in-app scores, event tracking, and near-instant settlement that moves wagers from open to won or lost and reflects balance changes
- MGM Rewards integration: loyalty tie-in so play contributes to the wider MGM Rewards program across the operator’s properties
Tech Stack
- Native Android written in Java, following an MVP (Model-View-Presenter) architecture
- Dagger for dependency injection across the app
- Retrofit for typed REST integration to the sportsbook, casino, wallet, and identity back ends over TLS
- Realm for on-device persistence of user, market, and bet-slip state
- XML layouts for the UI
- Real-time data over WebSocket and streaming connections to keep odds, live markets, and scores current
- Third-party SDKs typical of regulated betting apps: geolocation compliance, KYC/identity, and payment providers
- Distribution via the Google Play Store, subject to real-money gambling policies
Frequently Asked Questions
What platform is the BetMGM app built for? It is a native Android app, written in Java on an MVP architecture and distributed through the Google Play Store under its real-money gambling policies.
Why is geolocation part of a betting app? Legal online gambling in the US is licensed per state, so a location check has to confirm the user is physically inside a licensed jurisdiction before betting is enabled, and available markets and rules change by state.
How does the app keep odds and payouts accurate? Odds, live markets, and scores are kept current over WebSocket and streaming connections, and the bet slip calculates stake, odds, and payout against a fast-moving server-side source of truth.