Boško KosićVisual & Motion Designer Available — Q4 2026
← InterfacesUX case study

UX case study · Concept · 2026

APSIS

Live betting apps move the odds under your thumb, show the win before the risk and hide the limits. APSIS fixes all three inside the bet flow.

  • UX research
  • Flows & IA
  • UI design
  • Design system
  • Prototyping
Try the prototype

Concept project — not a real product. No real-money gambling. Teams, players and odds are fictional; demo credits only.

Role
UX research, flows, UI design, design system, live prototype
Duration
Concept sprint · 2026
Platform
Web · desktop, tablet, phone
Status
Concept, not a real product
APSIS on a wide screen: a live match with the bet slip open
APSIS on a wide screen: a live match with the bet slip open
01Problem & goal

Who

People who bet on live matches from a phone: one hand, short bursts, attention split with the game.

Today

Odds refresh while the thumb is on its way, so the tap lands on a price nobody read. The slip shows the possible win in big type and the stake in small. Limits and breaks live four screens deep in settings, far from the money.

Goal

A bet in three taps that never lands at an unseen price, with the risk as loud as the win and the limits one tap from the balance.

Targets for a usability test, not results

02Research · what was really done

No interviews or usability tests were run for this concept. What follows is a heuristic review against Nielsen's ten heuristics, of patterns that live-betting interfaces commonly use, plus one assumption of my own. Each insight says which it is.

Heuristic review · error prevention

The odds jump under the thumb

Live prices refresh several times a minute and cells reflow when markets open or close. A tap meant for 1.85 can land on 1.67, or on the next market.

Heuristic review · match with the real world

The win is loud, the risk is small

Possible returns get the biggest type on the slip; the stake, the amount you can actually lose, is a grey label beside the input.

Heuristic review · user control

Limits are four screens deep

Deposit and time limits sit under Account, Settings, Responsible gambling, so the tools exist but are not where the decision is made.

Assumption

Neon costs legibility

A futuristic look tends to put glow and gradients behind the numbers. I assume the odds have to win that fight on every screen, and kept the effects away from them.

03Users · jobs to be done

Proto-personas: assumptions to test, not research findings

Proto-persona · assumption

The live-match regular

When the game turns, I want to back what I just saw in seconds, so I don't miss the price.

NeedsStable targets, one-handed reach, a slip that never covers the score.

Proto-persona · assumption

The weekend multi builder

When I plan Saturday, I want to stack picks and see the total odds and stake clearly, so I know what I'm risking.

NeedsReadable totals on a phone, easy removal, Singles beside Multi.

Proto-persona · assumption

The careful one

When I set a budget, I want the app to hold me to it without lectures, so betting stays fun.

NeedsThe limit visible near the money, plain words, a break that is easy to take.

04Flow & information architecture

Three taps, every exception in words

From odds to a placed bet is three taps: odds, stake, place. Everything that can go wrong is checked before the last tap counts, and every exception has one way out that never places a bet by itself.

USER FLOW · PLACING A BETLobby or matchlive odds1 · TAP ODDSSlip openspick added2 · TAP STAKEReviewreturns · can lose · limit3 · TAP PLACEPlacingunder a secondReceiptbet ID · limit leftMy betsopenCHECKED BEFORE THE TAP COUNTSOdds changedaccept new odds · one tapMarket suspendedwait, or remove the pickOver today’s limitset stake to what is leftNot enough balancelower the stakeBACK TO REVIEW, NOTHING PLACEDNot placednothing charged · try againReality checkat your interval: time · staked · netKeep goingTake a breakEVERY EXCEPTION HAS ONE WAY OUT, IN WORDS, AND NONE OF THEM PLACES A BET BY ITSELF.

The slip is one tap away, everywhere

Five places, no deeper than two levels. The bet slip is not a page but a layer every screen can open, and Limits hangs off the balance, not off Settings.

INFORMATION ARCHITECTUREAPSISLobbyhomeFeatured live matchFilters: All · Live · sportLive nowStarting soonLive games (out of scope)Matchscoreboard · all marketsTAP ODDSBet slipone tap away, everywherePicksMulti / SinglesStake + quick amountsReturns · You can loseToday’s limit barPlace → receiptMy betsOpenSettledWalletdemo creditsUSDT · BTC · ETHAdd demo creditsHistoryLimitsresponsible playToday, as a ringDaily stake limitReality checkTake a breakThis sessionOn every screen: the balance sits inside a ring that fills as today’s limit is used. One tap on it opens Limits.
05Wireframe → final · three key screens

01Lobby

Odds that stay put

The first screen is the live list. Every match has the same three cells in the same place, so the eye and the thumb learn one target.

Why
  • Fixed 1 / X / 2 cells: a price change only changes colour and an arrow, never the layout.
  • The empty slip teaches the flow in one line: “Pick, stake, place: three taps.”
  • The balance sits inside a ring that fills as today's limit is used.
  • A “Concept · demo credits only” pill stays on screen, so a screenshot can't pass for a real product.
Lobby, final
Lobby, wireframe
WireframeFinal

Desktop · drag to compare

Lobby on a phone, final
Lobby on a phone, wireframe
WireframeFinal

Phone

02Match + bet slip

The risk as loud as the win

The slip opens beside the scoreboard on desktop and as a sheet on a phone, so the game never disappears behind it.

Why
  • “You can lose” sits above Returns, at the same size.
  • Quick stakes +5 / +10 / +25 / +50 for one thumb, no keyboard needed.
  • A limit bar shows the bet against today: “38.00 of 100.00 used · 58.00 after this bet”.
  • The button names the amount, so the last tap reads as a sentence.
Match with the bet slip, final
Match with the bet slip, wireframe
WireframeFinal

Desktop · drag to compare

Bet slip on a phone, final
Bet slip on a phone, wireframe
WireframeFinal

Phone

03Limits

Limits beside the money

Limits open with one tap on the balance from anywhere, and read as today's ring, not as a settings form.

Why
  • Lowering a limit applies at once; raising one takes 24 hours.
  • Reality check every 15, 30 or 60 minutes: time, staked and net, in plain numbers.
  • Take a break for 24 hours, 7 days or 30 days, two taps away.
  • This session's net is always shown, win or loss, without colour drama.
Limits, final
Limits, wireframe
WireframeFinal

Desktop · drag to compare

Limits on a phone, final
Limits on a phone, wireframe
WireframeFinal

Phone

06Design system

Every colour, face and radius is named once, as a token. The odds button is the main component, and its states carry the whole live behaviour.

Colour tokens

  • Night#060827background
  • Surface#141A4Ecards, odds
  • Text#F4F5FFnumbers, labels
  • Muted#AEB3DEsecondary text
  • Pick#FF5CB8selected, primary action
  • Live#8FE3FFlive state
  • Up#6DF2B0odds went up
  • Down#FFD166odds went down

Type

Odds that stay put

Nippo titles · Satoshi interface and numbers

1.85  2.10  1.67  11.11  38.00 / 100.00

Tabular figures: odds line up and never shift when they change

Odds button · the main component

  • 11.85

    Default

  • 11.85

    Selected

  • X2.10

    Went up

  • 21.67

    Went down

  • 11.92

    Suspended

52 px tall, the whole cell is the target. A price change is colour plus an arrow, never movement. With reduced motion the flash is off and the arrows stay.

Contrast, measured (WCAG 2.2)

  • 1.85Text on Night18.1 : 1AAA
  • 1.85Muted on Surface8.0 : 1AAA
  • 1.85Pick on Night7.0 : 1AA
  • 1.85Live on Night13.6 : 1AAA
  • 1.85Up on Surface11.6 : 1AAA
  • 1.85Down on Surface11.3 : 1AAA
  • 1.85Ink on Pick (selected)6.9 : 1AA
07Responsible play · the exceptions

Responsible play is not a page here, it is the exceptions of the bet flow. Each one stops the bet, says what happened in plain words and offers one way out.

08What I'd test next

Five people who bet on sport at least monthly, 20 minutes each, remote, thinking aloud, on the live prototype with demo credits.

#TaskPass when
01Place a single on a live match≤ 3 taps and under 10 s, for 4 of 5
02Odds change while the slip is open0 bets placed at odds not seen
03Set a daily limit of 50 from the lobby1 tap to Limits, for 4 of 5
04After placing, say what you could lose4 of 5 name the stake
05Read the total odds of a multi on a phone0 misreads

A plan, not results: no test has been run yet

09Result
Try the prototype

A working prototype of the whole flow: lobby, match, slip in single and multi, my bets, wallet with demo credits and Limits, with loading, empty, error, changed-odds, suspended and limit states, on desktop, tablet and phone, keyboard and reduced motion included.

Concept project — not a real product. No real-money gambling. Teams, players and odds are fictional; demo credits only.

10What I'd do differently

Run five short interviews before drawing a single screen, so the personas start as findings instead of assumptions.

Test the reality-check timing with real session lengths: an interval that interrupts too often gets dismissed without being read.

Selected work · 01 Live on the Streets 50+ billboards across Belgrade, designed for the three seconds a driver gives them.
●Contact

Got a brief?
Let’s make it move.

Open to full-time roles, remote contracts and freelance projects worldwide.

Quick brief3 taps · 20 seconds

To
Boško KosićUsually replies within a day
Subject
Pick what you need below

Hi Boško,

I need

Timing

Send the brief Opens your email, ready to send

Then I reply within a day, with questions and first ideas.