DraftKings Fantasy Sports UI Clone in React Native

What makes DFS different from a sportsbook, legally and in the UI?

The contest structure. Daily fantasy sports entered US law through the UIGEA’s 2006 carve-out for fantasy contests, on the argument that lineup-building is skill; several states have disputed exactly that, and the result is a state-by-state patchwork where DFS is explicitly legal in some places, banned in others, and licensed like gambling in more of them every year. DraftKings itself carries the scars: the 2016 merger with FanDuel, a combined five-million-plus users, was blocked by the FTC, and the New York insider-data scandal forced employee-play bans industry-wide.

For a builder, that history compresses into one instruction: clone the mechanics freely, but build the chassis like a regulated product, because wherever real money enters, the regulator follows. Geolocation gating per state, age verification, deposit limits, self-exclusion, and a visible link to problem-gambling resources are not add-ons in this genre; they are the price of the lobby existing. A free-to-play clone skips the licensing but should keep the structure, because the structure is the product.

What is the lineup builder, really?

A constraint-satisfaction puzzle with a $50,000 budget, and the single screen the whole genre is judged on. The mechanics that make it work:

• The remaining-salary line is the protagonist. Cap minus spend, recomputed on every add and drop, always visible, with average-remaining-per-slot as the second number (“3 slots, $14,200 left, $4,733 avg”). Burying this math is the most common clone failure.
• Position slots are the structure: QB, RB, RB, WR, WR, WR, TE, FLEX, DST (in the NFL shape), each slot a tappable target filtered to eligible players.
• The player pool is a sortable, salary-annotated list: salary, projected points, opponent, game time, with swap-in one tap and the cap math updating live.
• Lock times are per player, not per contest. A player locks when their real game starts, so late swap (changing unlocked slots while early games run) is a first-class flow, with locked slots visually frozen.

Build the list virtualized from the start (hundreds of players, salary sorts, position filters), and make invalid states unenterable rather than validated after the fact: a player who breaks the cap renders as unaffordable before the tap, not as an error after it.

How do contest types shape the lobby?

Contest type	Payout shape	Who enters	What the card must show
Tournaments (GPPs)	Top-heavy; a few entries win big	Upside chasers, mass entries	Prize pool, entrants/cap, multi-entry rules
Cash games (50/50s, head-to-heads)	Double-up or nothing	Bankroll grinders	The cash line: finish top half, double
Satellites	Tickets into bigger contests	Ladder climbers	What the ticket is worth

The lobby card carries entry fee, total prize pool, current and maximum entrants, and start time, with the fill bar (12,841 of 20,000 entered) as the urgency element that is honest by construction, since it renders server truth rather than a countdown trick. Filters by sport, entry fee band, and contest type matter more than search; nobody types in a lobby.

What does live scoring owe the user?

Honesty about provisionality. Fantasy points stream in while games run, and the genre’s quiet integrity problem is that points are provisional until stat corrections settle, sometimes a day later. The live screen handles it the way the odds-display genre handles flashing numbers: stream updates with player-level deltas (who just scored, what it did to your total), keep a visible “live” state on every number, and mark contests as “unofficial” until results settle, so the user who slid from 4th to 6th overnight reads it as the settlement process rather than a glitch.

The watching experience borrows from the live trivia genre: your entries ranked by current payout position, one tap into the player-by-player breakdown, opponent lineups revealed per the contest’s rules. And because state rules and league data deals shift constantly, real-money apps in this genre ship forced update gates as standard equipment; a compliance change cannot wait for organic adoption.

A free VP0 design covers the genre’s screens, lobby cards, the salary-cap builder, live scoring drawers, so an agent generates the constraint mechanics against real layout structure instead of improvising the cap math into a corner.

Key takeaways: a DFS app done honestly

• The carve-out is contested: UIGEA opened the door, states keep relitigating it; build geolocation, age gates, limits, and self-exclusion as core architecture.
• The lineup builder is the product: visible cap math, per-slot eligibility, unenterable invalid states, per-player lock times with late swap.
• The lobby is server truth: fee, pool, fill bar, start time; filters over search.
• Live points are provisional: stream with deltas, label unofficial until corrections settle.
• Free-to-play keeps the structure without the licenses; real money means lawyers before code.

Frequently asked questions

How do I build a DraftKings-style fantasy sports UI in React Native? Start from a free VP0 design for the lobby and builder screens, then have Claude Code or Cursor generate the salary-cap lineup builder (visible remaining-salary math, position slots, per-player lock times), a server-truth contest lobby, and a live scoring drawer with provisional-points states. Keep real money out unless licensing is in place.

Is it legal to build a daily fantasy sports app? Building the UI and running free-to-play contests is generally fine; offering real-money DFS triggers state-by-state licensing, geolocation enforcement, and age verification in the US. The UIGEA carve-out is not blanket permission, and several states treat DFS as gambling.

What is the hardest screen in a DFS clone? The lineup builder: a constraint puzzle where the $50,000 cap, slot eligibility, and lock times interact. The craft is making invalid states unenterable and keeping remaining-salary-per-slot visible through every swap.

How should live fantasy scoring handle stat corrections? Label everything: points stream as live and provisional, contests stay marked unofficial until results settle, and overnight ranking shifts present as settlement rather than error. Provisional numbers that look final are how this genre loses trust.

What responsible-play features does a DFS app need? Deposit and entry limits, self-exclusion, clear age gating, state geolocation checks, and visible problem-gambling resources. In regulated states these are requirements; in a free-to-play clone they remain the right defaults.