2Coders Studio
Contact us
Industry TrendsOTT platforms and apps

Post-Event Engagement in Sports Apps

We opened the F1, MLB, World Cup and MotoGP apps the moment events ended. The best one won because every screen knew the event was over.

Karen Gallego

Karen Gallego

Lead UI/UX Designer

7 min read

Sports fans celebrating in a stadium

Episode 1 of 6: what four sports apps show a fan in the hours after the final whistle.

Tested on iOS, 24 June to 1 July 2026.

The match just ended. Your fan has their phone out, still excited about what happened, looking for the replay, the stats, something to send to the group chat. What does your app do with that moment?

For a rights holder, this is the cheapest moment to keep a fan: they are already invested and already holding the phone.

We opened four sports apps right after live events: F1 after the Austrian Grand Prix, MotoGP after the Dutch GP at Assen, the FIFA World Cup 2026 app across several Round of 32 matches, and MLB across a regular-season week. We timestamped every capture from the moment the event ended until the next morning, and followed the fan through the home screen, the result notification, the content inside the app and the bridge to the next event.

The best app in our set won because every screen knew the event was over at the same time.

Key findings in 60 seconds
  • Post-event engagement in sports apps comes down to one thing: whether every screen treats "event just ended" as a state it was designed for.
  • F1 and MLB update the home screen within seconds. MotoGP stayed on FOLLOW LIVE for up to 46 minutes.
  • MLB and the World Cup app put the score in the push within minutes. MotoGP's result push came 59 minutes later and opened the wrong session.
  • MLB's Wrap tab is the strongest catch-up hub in the set. MotoGP sends every race video to X.
  • The World Cup app shows the next match within 12 minutes of full time.

The best post-event experience comes from every screen agreeing that the event is over.

This is the first episode of UX Rerun, our feature-by-feature look at UX in major sports apps.

Dimension F1 MLB FIFA World Cup MotoGP
Home screen after the event Result within seconds LIVE flips to FINAL instantly Match card moves behind the next fixture in ~30 min; arrival banner stays FOLLOW LIVE for 37–46 min
Result push Podium teaser at T+6 min Full stat line within 8 min Score at full time Teaser at T+59 min, opens the wrong session
Content inside the app Strong, spread across several surfaces Wrap tab: 9 modules in one scroll Live Blog continues into post-match coverage Fast Live Blog, every video on X
Bridge to the next event Session bar flips at T+2.5 h Next game shown during the current one Bracket card at T+12 min Structural hook days later

When the app knows the game is over

The first thing a fan sees after the final whistle is the home screen. Does it reflect what just happened?

F1 was the fastest in our set. After the Austrian Grand Prix, the session bar already read “Race > Finished”, the driver strip showed the top four, and a star marked the drivers you follow. Zero taps from lock screen to result. The editorial headline followed about 30 minutes later.

MLB was just as clean, in two moves. The moment the last out is recorded, the LIVE pill flips to FINAL and the pitch tracker freezes on the final play. A few minutes later, the card rebuilds into a post-game summary with new tabs: Wrap, Box, Videos and Story.

The World Cup app moved the finished match behind the next fixture within 30 minutes. But a stadium-arrival banner (“aim to arrive when gates open”) stayed at the top of the home screen from kick-off to the next morning.

MotoGP’s home screen stayed on “FOLLOW LIVE” for 37 to 46 minutes after the race, and at one point showed a LIVE badge and a “FINISHED” label side by side. The hero led with a crash story and never showed the winner during our 18-hour capture.

When the home screen shows the wrong state, fans learn that the app isn’t the first place to check, and that habit is hard to change.

F1 app session bar: FP3 still live on the left, the Austrian GP race result already shown on the right
F1's Austrian GP session bar: FP3 still live on the left, the race result already up on the right.
MLB Astros–Tigers Gameday in three states: live at Top 1, pitch tracker frozen on the final strikeout, then the full Wrap-style rebuild
MLB's Astros–Tigers Gameday, same game, three states: live at Top 1 (left), the pitch tracker frozen on the final strikeout with the tab row untouched (centre), then the full rebuild into a Wrap-style score card with pitchers and Top Performers (right).
FIFA World Cup app home screen 40 minutes apart: the completed match card gives way to the next fixture, but the stadium-arrival banner at the top stays unchanged
The FIFA World Cup app's home screen, 40 minutes apart: the completed South Africa–Canada card gives way to the next fixture, but the "Important information for your matchday" banner at the top doesn't move at all.
MotoGP home screen across 17 hours: Follow Live during the Dutch GP, then Finished with the Bezzecchi crash leading, then the same crash follow-up the next morning
MotoGP's home screen across roughly 17 hours: "FOLLOW LIVE" during the Dutch GP (left), "FINISHED" with the Bezzecchi crash leading the story instead of a result (centre), and the same crash follow-up still leading the next morning (right).
Builder's takeaway Use one event-state layer that every screen reads from, so the home screen hero, the badges and the cards all change in the same update.

The notification after the final whistle

A push notification after the final whistle is the simplest way to bring a fan back. What matters is what it says, when it arrives and where it opens.

MLB’s game-end push carried the full stat line (“The Tigers beat the Astros, 8-0”, with the winning and losing pitchers) within minutes of the final out. The World Cup app sent the score at the exact moment of full time, with a branded score card.

F1 and MotoGP wrote teasers. F1’s push at T+6 minutes read “Find out who’s on the podium in Spielberg” (we had F1’s Spoiler Mode on, which may shape that copy). MotoGP’s “Who has emerged victorious?” arrived at T+59 minutes, which is late for a fan who wants the result. It then opened the Results tab on Warm-Up times instead of the race classification.

Both styles have a place. A fan following live wants the score, and a fan saving the race for later wants a teaser, which is the focus of Episode 5.

MLB full stat line push, FIFA World Cup score push at full time, and F1 podium teaser push
MLB: full stat line, 8 minutes after the final out. FIFA World Cup: score confirmed the instant full time blows. F1: podium teased, no name given.
MotoGP's two result pushes, hours apart, neither naming the winner Ai Ogura
MotoGP's two pushes, hours apart, still no winner's name in either.
Builder's takeaway Match the push to the fan: the score for fans following live, a teaser for fans with a spoiler setting on. Send it within minutes, and open it on the screen that shows the result.

What’s waiting inside the app

The push brings the fan back. What they find decides whether they stay for 30 seconds or 10 minutes.

MLB’s Gameday screen switches to a Wrap tab about 8 minutes after the final out. It packs nine modules into one scroll, from the line score and highlights to Player of the Game and Statcast visualisations generated for every game. It’s dense, but a fan can stop at any point and still leave with something useful.

The World Cup app kept fans where they already were. Its Live Blog turned into post-match coverage, with bylined articles within 22 minutes and highlights at T+26.

F1’s content was strong but spread out. Driver quote cards, free team radio clips and new F1 Moments clips each live on a different surface, so a fan has to know where to look.

MotoGP named the winner in its Live Blog within 3 to 6 minutes, the fastest in the set. But every race video in the feed was an X embed, so the app found the moment and sent the fan elsewhere to watch it.

Stories show the same split. After you watch one, F1 removes it from the rail, the World Cup app moves it to the end, MLB leaves it unchanged and MotoGP greys it out in place. MotoGP’s version is closest to what we’d build: an unwatched circle still pulls fans back, and nobody loses a recap they want to see again.

MLB Wrap tab showing line score, recap, Player of the Game, Top Performers, and Statcast visualisations
MLB Wrap tab with line score, recap, Player of the Game, Top Performers, and Statcast visualisations.
FIFA World Cup Live Blog showing match highlights and player quotes in the same post-match feed
FIFA World Cup Live Blog with match highlights and player quotes in the same feed.
F1 Live Blog showing driver quote cards, inline team radio clips, and race overview
F1 Live Blog with driver quote cards, inline team radio, and race overview.
MotoGP Live Blog naming Ai Ogura within minutes of the race ending, with every video clip routed through Watch on X
MotoGP Live Blog naming Ai Ogura within minutes, every clip routed through "Watch on X."
Builder's takeaway Keep video inside the app, and keep watched Stories on the rail with a visual change so fans can find them again.

Bridging to the next event

The apps that hold attention longest also give the fan a reason to come back.

The World Cup app did this best. A Round of 16 bracket card appeared in the Live Blog at T+12 minutes, Canada’s next match date at T+19, and the match page carried a RELATED MATCHES tab with the schedule, all while the emotion was still fresh.

MLB showed the next game before the current one had ended: a followed player’s card read “Next Game: Sat 6/27 6:10 PM vs. Astros” in the 7th inning.

F1 moved on quickly. Its session bar flipped to the British Grand Prix at T+2.5 hours, so a fan catching up on Sunday evening found the Austrian result one step further away.

MotoGP’s Live Blog pointed to the Sachsenring at T+70 minutes, but the home screen only switched to the next round, with a countdown, a few days later.

Builder's takeaway Show the next fixture on the finished event's page, where the fan already is.

What this tells us about post-event engagement in sports apps

Every app in our set builds good individual features. What separates them is whether those features still agree with each other when the fan opens the app again.

MLB comes closest: its pill states, push, Wrap tab and next-game hooks all follow the same event lifecycle. MotoGP is uneven, with the best Story handling in the set and a home screen that kept saying LIVE. The World Cup app has the same split the other way round: a Live Blog that moves smoothly into post-match coverage, under a banner that never knew the match had ended.

That gap says more about how mature an organisation’s digital operation is than any feature list. A club app with one highlights rail can start in the same place: decide what “event ended” looks like on every screen, and make them all change together.

How does your app compare?

Score your post-event experience against what we found.

Does your home screen show "event ended" within 60 seconds of the final whistle?

Event-state architecture is front-end work we design and build for sports apps.

Talk to the team behind UX Rerun

Frequently asked questions

What is post-event engagement in a sports app?

It's what the app gives a fan in the minutes and hours after an event ends: an updated home screen, a result notification, highlights, data and a link to the next fixture. Done well, it turns the end of a match into a reason to stay in the app.

Which sports app handles the post-event moment best?

In our testing, MLB, because its home screen, push, Wrap tab and next-game hooks all change together. F1 shows the result on the home screen fastest, and the World Cup app has the strongest bridge to the next match.

Should a result push notification include the score?

It depends on the fan. A fan following live wants the score in the push, as MLB and the World Cup app do. A fan saving the match for later wants a teaser that names no winner. The best setup lets the fan choose with one setting.

Why do sports app home screens still show LIVE after the event has ended?

Usually because each part of the screen updates on its own schedule. The hero, the badges and the cards read different sources, so one changes while another still shows LIVE. A shared event-state layer that every screen reads from solves this.

This is Episode 1 of 6 in UX Rerun. Continue with Episode 2, Episode 3, Episode 4, Episode 5 and Episode 6. The full season comes together in our Fan Engagement Benchmark.

Fan Engagement Benchmark

SportsUX/UIFan EngagementMobile AppsUX Rerun