The match just ended. Your fan is at peak emotional investment, phone in hand, ready to see the replay, check the stats, share the moment with friends. What does your app do?
We opened four sports apps in the minutes and hours after a live event to answer that question. The FIFA World Cup 2026 app across several Round of 32 matches. The F1 app after the Austrian Grand Prix. MotoGP after the Dutch TT at Assen. And the MLB app across multiple games during a regular-season week. All captures were on real devices, manually timestamped from the moment the event ended through the following morning.
What we found: the gap between the best and worst post-event experiences comes down to whether the app treats “event just ended” as a product state that gets designed for, or as a moment that happens and then fades into a generic home screen.
This is the first episode of UX Rerun, our feature-by-feature analysis of UX in major sports apps. Season 1 focuses on fan engagement: six episodes covering post-event experience, pre-match build-up, personalisation, gamification, catch-up and spoiler management, and social sharing. Future seasons will cover discovery, live event experience, monetisation, and more. Each episode takes one subtopic and compares how different platforms handle it. No rankings, no awards. Just what we found and what we’d build differently.
When the app knows the game is over
The first thing a fan sees after the final whistle is the home screen. The question is simple: does it reflect what just happened?
F1 was the fastest in our research set. The instant you open the app after the Austrian Grand Prix, the session bar reads “Race > Finished” with a chequered flag. The driver strip shows P1 Russell, P2 Verstappen, P3 Antonelli, P4 Piastri, with a small star marking the drivers you follow, so you can spot your favourite’s finish at a glance. Below the strip, a tappable editorial card links to the full race report: “Russell seals thrilling Austria victory from Verstappen.” Zero taps from lock screen to result; one tap to the deep analysis. The data layer updated within seconds of the chequered flag; the editorial headline caught up within about 30 minutes. Two different systems running at two different speeds, but the result is visible immediately.
MLB handled the transition differently but just as cleanly, and it happens in two moves. The instant the last out is recorded, the matchup header flips from a LIVE pill to a FINAL pill, and the Gameday pitch tracker freezes on the final play (in our capture, a called swinging strikeout, pitch location grid and play description still on screen). At this stage the tab row hasn’t moved: Watch, Audio, Gameday and Story are all still there. A few minutes later, the whole card rebuilds into a post-game summary and the tabs swap to Wrap, Box, Videos and Story (more on that in the content hub section below). It’s an instant freeze-frame first, then a fuller rebuild. A fan checking the score in the first thirty seconds after the game and a fan opening the app ten minutes later both get an accurate “this is over” signal, just at different levels of depth.
The FIFA World Cup 2026 app moved the completed match card behind the next fixture within 30 minutes, a clean editorial choice. But a stadium-arrival banner (“Important information for your matchday: aim to arrive when gates open”) sat in the top home screen slot throughout our whole capture window: during the match, right after full time, and still there the next morning. Someone opening the app the next morning still saw an arrival-time notice for a match that had finished hours earlier.
MotoGP’s home screen stayed in “FOLLOW LIVE” state for 37 to 46 minutes after the race ended. The hero never transitioned to show the winner across our entire 18-hour capture window. Instead, the editorial team led with the Bezzecchi crash story. Meanwhile, the LIVE badge and a “FINISHED” label appeared side by side on the same screen, a state-sync issue that makes the home screen feel unmanaged.
The contrast matters because the home screen is the most-visited surface in any app. When it doesn’t reflect reality, the fan’s trust in the app’s freshness erodes. They learn, over a few events, that the app isn’t the place to go first.
The notification that earns its open
A push notification after the final whistle is the simplest re-engagement mechanic in sports. The question is what it says and when it arrives.
MLB’s game-end push contained the full stat line: “The Tigers beat the Astros, 8-0. WP: Keider Montero (4-5), LP: Spencer Arrighetti (7-4).” Winning pitcher, losing pitcher, innings pitched, earned runs, strikeouts, walks. Even without opening the app, you get the complete result from the lock screen. The notification arrived within minutes of the final out.
The FIFA World Cup app sent a push at the exact moment of full time: “South Africa v Canada match ended, South Africa 0 : 1 Canada,” with a branded score card thumbnail. It arrived the instant the game ended and told you the actual score. No teaser copy to unpack.
F1 took a different approach. The first push at T+6 minutes read: “Find out who’s on the podium in Spielberg.” No winner named. We had spoiler-free mode switched on in Settings ahead of the race, so we can’t yet say whether this is F1’s standard podium push or copy the app personalises when that setting is on; that needs a control test with the setting off. A second push at T+4 hours linked to a depth article. Two beats: one for the result seekers, one for the analysis seekers. Either way, the two-wave architecture is the interesting pattern here, and if the spoiler-free setting really does reach into push copy, that’s worth its own callout in the Ep 5 catch-up and spoiler episode.
MotoGP’s result push arrived at T+59 minutes: “Who has emerged victorious? Full results HERE!” The mystery framing deliberately withheld the winner’s name to drive a tap. A second push at T+266 minutes, headlined “WORDS OF A WINNER,” still didn’t name Ai Ogura. For anyone who finished the race and picked up their phone an hour later, the official app hadn’t yet told them who won.
One operational detail worth flagging: MotoGP’s result push correctly deep-linked to the Results tab, but the tab defaulted to Warm-Up session data, not the race classification. The routing worked; the session filter didn’t. Tapping “Full results HERE” landed you on the right screen showing the wrong results.
The post-event content hub
This is where session time lives or dies. The notification gets the fan back into the app. What’s waiting for them determines whether they stay for 30 seconds or 10 minutes.
MLB’s Gameday screen, the same one that froze on the final pitch the moment the game ended, transitions from a “Live” subtab to a “Wrap” subtab within about 8 minutes of the final out. The Wrap tab packs nine content modules into a single scroll: line score, winning and losing pitchers, a highlights rail, a full-width editorial photo with headline, an MLB.TV replay CTA, Player of the Game with win probability added as the metric, Top Performers with detailed stat lines, a team comparison table, and Statcast data visualisation clips. It’s dense. Arguably too dense for one scroll. But every module earns its place, and a fan can stop scrolling at any point having already consumed something useful.
The FIFA World Cup app used a continuity approach. The Live Blog, the same surface fans were using during the match, transitions into a post-match editorial feed. Content populates progressively over about 90 minutes: match highlights at T+26, interview quotes at T+25, articles at T+22 on the News tab, POTM voting result at T+8, and PlayZone trivia games arriving around T+90. The fan doesn’t have to navigate anywhere new. The editorial velocity was strong: proper bylined journalism with narrative headlines, not automated result cards, within 22 minutes of full time.
F1’s post-race content spread across multiple surfaces. The Lap by Lap feed introduced driver quote cards within minutes of the chequered flag: first-person reactions from podium drivers. Team radio clips played inline with no paywall, which is notably generous given that team radio is F1’s strongest exclusive content. F1 Moments, the app’s short-form vertical video shelf, refreshed with NEW-badged clips within 90 minutes. The content is strong, but it lives across several tabs and surfaces. A fan has to know where to look.
MotoGP’s Live Blog delivered the fastest winner identification in any app we tested: Ai Ogura named within 3 to 6 minutes, followed by six labelled celebration sections covering the full podium and championship implications within 7 minutes. The editorial narrative was rapid and well-structured. But every race video in the feed was an X/Twitter embed with “Watch on X” CTAs. The app surfaced the signal; it just sent every fan to someone else’s platform to watch it.
How highlights and stories serve catch-up fans
Post-event catch-up content comes in three formats across our set, worth naming properly before comparing platforms. Horizontal highlights are the traditional widescreen clip, watched full-screen. Stories are the Instagram/Snapchat-style format: vertical slides you tap left or right to move through, usually pinned to a circle or card on the home screen. Short-form vertical video (Reels or Shorts-style) is the swipe-up/down feed of standalone vertical clips. Not every platform uses all three.
| Platform | Horizontal highlights | Stories (tap left/right) | Short-form vertical video (swipe up/down) |
|---|---|---|---|
| MLB | Play clips live during the game; full package and condensed game auto-advance by the next morning | Game Story: video plus info card, per-slide reactions, no auto-advance, no watched-state marker | Not offered |
| FIFA World Cup | Live Blog embed first, then the Tournament Highlights tab, then an on-page pill button | Full match narrative arc published live as each moment happens (Starting XI, kickoff, halftime, goals, full-time), persistent CTA, moves to end of rail once watched | Not observed as a distinct format from Stories |
| F1 | “2026 Highlights” home shelf, auto-advancing Related queue | Race Live - Austria: updates live during the race (~40 clips), loses its LIVE badge and gets renamed Relive Race - Austria after; auto-advances, deleted once watched | F1 Moments, refreshed within 90 minutes post-race |
| MotoGP | Dedicated Highlights shelf, manually-tapped Related list | Dutch GP story circle: continuously updated across the whole race weekend (practice, a crash, rider interviews, Sprint grid and results, breaking injury news), stays in place with a grey overlay once watched | Moments, carries the real post-race racing content |
The table captures the format mix, but the more interesting comparison is what happens after you’ve watched a Story. F1 removes it from the rail entirely. The FIFA World Cup app keeps it, moved to the end. MotoGP marks it watched in place with a grey overlay. MLB doesn’t mark it at all — no repositioning, no visual change. MotoGP’s version is closest to what we’d build: the pull of a fresh, un-greyed circle stays intact as a reason to come back quickly, but nobody gets locked out of a recap for having watched it once.
The full per-platform breakdown of format behaviour, live-update mechanics, and content depth is covered in the Fan Engagement Benchmark when it drops in August.
Data that explains what happened
The result answers who won. The more interesting question is why and how it happened, and three platforms in our set actually dig into that.
MLB’s Statcast visualisations are auto-generated for every game. The Wrap tab includes animated pitch movement charts, velocity scatter plots, bat contact analysis with sweetspot position, bat speed, launch angle, and exit velocity data. They’re branded (“MLB STATCAST powered by Google Cloud”) and include an AirPlay button for TV casting. For someone who missed the game, these clips explain the moments that mattered in terms that go beyond the box score.
The FIFA World Cup app introduced Aramco-branded Power Rankings about two hours after full time. Three hero cards (Attacking, Creativity, Defending) with player ratings and a sortable table of all players. Tapping a column header re-sorts the rows correctly, a small detail that makes the table feel trustworthy rather than decorative.
F1 has extensive session data at the timing screen level (lap times, sector splits, tyre strategy), but that’s a separate surface from Power Rankings, which turns out to be better presented than we first captured. It arrives as a push notification (“Who impressed our judges at the Austrian Grand Prix?”) that opens into a full article: a “How it works” explainer up top (a five-judge panel scores every driver out of 10 across the weekend, machinery factored out), then a driver-by-driver breakdown: colour-coded position bar, team livery, headshot, race position, and score in a green badge, each backed by a paragraph of real analysis, plus a “Missing out” section for drivers just outside the top 10. Only the season-aggregate leaderboard at the very bottom condenses into a dense table, and even that carries colour coding and change arrows.
Bridging to the next event
The apps that extend sessions don’t just show what happened. They give a reason to come back.
The FIFA World Cup app did this best. At T+12 minutes, a Round of 16 bracket card appeared in the Live Blog (57 likes). At T+19, an editorial card announced Canada’s next match date. A previously undocumented RELATED MATCHES tab on the match page embedded the tournament schedule right inside the completed match view. All of this while emotion from the current match was still high.
MLB planted next-game hooks before the current game even ended. A followed player’s card showed “Next Game: Sat 6/27 6:10 PM vs. Astros” during the 7th inning. With games every day for six months, there’s always a next event, and the app uses that cadence.
F1’s session bar flipped to the British Grand Prix at T+2.5 hours, removing the Austrian GP result from one-tap access. The Relive Race story’s final slide contains a British GP card, but only fans who watch all 40 slides see it. The handoff is aggressive; a fan catching up on Sunday evening finds the app has already moved on.
MotoGP’s Live Blog included one forward-looking line at T+70 minutes: “full focus turns to Round 11… Next stop: Sachsenring.” Effective copy, but nothing structural backed it up in the following hours. The structural version does arrive eventually: a few days later, the home screen hero flips entirely to the next round, “Germany > MotoGP Gearup,” with a Tissot-branded countdown running in days, hours, minutes, and seconds. It’s a real next-event hook, just a much slower one than the rest of the set: F1’s session bar turns over at T+2.5 hours, MLB surfaces the next game before the current one even ends, and the FIFA World Cup app has a bracket card live within 12 minutes. MotoGP gets there in days, not minutes.
What this tells us
The strongest post-event experiences don’t come from getting everything right. They come from architecture: every surface in the app tied to the same understanding of what state the event is in, updating together instead of on its own separate schedule. MLB comes closest to holding that line across the board: the same event-lifecycle logic runs through its pill states, its push, its Wrap tab, and its sharing assets, with no surface caught out of step with the others.
MotoGP is the clearest case of what happens when that consistency breaks down within a single app. Its home screen sat in a “FOLLOW LIVE” hero for the better part of an hour after the race ended, at one point showing a LIVE badge and a FINISHED label side by side. Its result push routed correctly to the Results tab, then showed the wrong session once it got there. And yet its Stories format has the best watched-state handling in our entire set. A story stays exactly where you left it, greyed out but still reachable, while F1 deletes the equivalent Story outright the moment you’ve watched it. MotoGP isn’t behind. It’s uneven, doing the hardest part well and an easy part badly.
The FIFA World Cup app runs the same contradiction in the opposite direction. Its Live Blog transitions cleanly from live coverage into post-match editorial within minutes, and its Stories publish live as each moment happens, one of the strongest continuity mechanics we tested. But that Live Blog sits below a stadium-arrival banner that never once acknowledges the match has ended, because that slot was never built to know what state the event is in.
F1 comes closest to a fully joined-up picture: a zero-tap result, a Power Rankings experience that turns out to be a real article rather than a bare table, and a race Story that updates live and relabels itself the instant the chequered flag falls. Its one gap is the mirror of MotoGP’s strength: once you’ve watched that Story, it’s gone.
Consistency, not quality, is the real variable here. Every one of these apps builds good individual features. What separates them is whether those features are still talking to each other by the time a fan opens the app again. That gap maps directly to how mature each organisation’s digital operation is — not how much they’ve spent, but how joined-up their systems are.
For anyone building a sports app: the post-event window is the cheapest retention moment you have. The fan is already invested. They’re already holding the phone. The content they want is finite and predictable — result, highlights, stats, reaction, next fixture. The only question is whether every part of the app already agrees that the moment has arrived.
We build these systems. If we were starting a post-event experience from scratch today, the first thing we’d wire up isn’t the content — it’s the event-state layer that tells every surface in the app what just happened, at the same time, so nothing gets caught showing yesterday’s news. The features come after. The architecture comes first.
This is Episode 1 of 6. The complete UX Rerun Season 1 analysis compiles into the Fan Engagement Benchmark — a cross-platform scoring framework covering post-event, pre-match, personalisation, gamification, catch-up, and social sharing. It drops in August 2026.
New episodes weekly through August.
