Live Activities for Sports Scores: Glanceable, Live

A Live Activity puts a live game score on the Lock Screen and in the Dynamic Island, so a fan never has to open your app to check it. The short answer: build the layout from a free VP0 design and drive it with ActivityKit, keeping it ruthlessly glanceable, teams, score, and game clock, and design every presentation (compact, expanded, minimal). It fits how fans behave: live sports drive heavy second-screen use, with around 50% of fans using another device while watching, per Deloitte, so a glanceable score is exactly what they want.

Glanceable is the whole point

A Live Activity is tiny and high-frequency, so restraint is everything. Show only what a fan needs at a glance: the two teams, the score, and the game state (quarter, clock). Resist cramming stats, ads, or extra controls, there is no room, and clutter kills the glance. You must design several presentations: the Lock Screen layout, and the Dynamic Island in its compact (leading and trailing), expanded, and minimal forms. Each shows progressively more, but all stay scannable in a fraction of a second. Apple’s Human Interface Guidelines for Live Activities define these presentations and the glanceability bar.

Build it from a free design

VP0 is a free iOS design library for AI builders. Pick a compact card or scoreboard design, copy its link, and have Cursor or Claude Code rebuild it as a SwiftUI widget powered by ActivityKit. Update the score through ActivityKit (push updates for remote games), and respect the system update budget, do not hammer it every second; update on meaningful events (a score, a period change). Start the activity when the game starts and, crucially, end it when the game ends so it does not linger. Keep every presentation legible and on-brand. For the Dynamic Island interactions specifically, see iOS Dynamic Island interaction Figma, and for another glanceable surface, see watchOS 11 health ring UI clone.

Live Activity presentations

Design each form to stay glanceable.

Presentation	Shows	Keep it
Lock Screen	Teams, score, clock	Clean, one glance
Island compact	Score or key number	Tiny, legible
Island expanded	A little more context	Still scannable
Island minimal	A single indicator	Just enough
End state	Final score, then stop	Do not linger

Common mistakes

The first mistake is cramming too much (stats, ads, controls) into a surface built for a glance. The second is updating too often, blowing the system budget and the battery; update on real events. The third is not designing all the Dynamic Island presentations, so some look broken. The fourth is never ending the activity, leaving a stale score on the Lock Screen. The fifth is poor legibility at tiny sizes. Show the few things that matter, update them efficiently, and end on time.

A worked example

Say you build a sports app. When a game starts, your VP0-built Live Activity shows the two teams, the score, and the clock on the Lock Screen, with a compact Dynamic Island showing the score and an expanded form adding possession. Updates arrive on scores and period changes (via push), not every second, so it is efficient. When the game ends, it shows the final and then stops. The fan follows the whole game without opening the app. For the subscription that might gate premium features, see RevenueCat paywall UI clone Figma, and for the contactless-payment pattern next, see NFC Tap to Pay on iPhone UI clone.

Key takeaways

• Live Activities show a live score on the Lock Screen and Dynamic Island, no tap needed.
• Build the layout from a free VP0 design and drive it with ActivityKit.
• Keep it glanceable: teams, score, and clock, not stats or ads.
• Design all presentations (Lock Screen, compact, expanded, minimal) and update efficiently.
• Update on real events within the system budget, and end the activity when the game ends.

Frequently asked questions

How do I build a Live Activity for sports scores? Build the layout from a free VP0 design and power it with ActivityKit, designing the Lock Screen and all Dynamic Island presentations, and updating the score on meaningful events via push.

How often should a Live Activity update? On meaningful events (a score, a period change), not every second. Respect the system update budget to avoid being throttled and to protect battery life.

What should a sports Live Activity show? Just the glanceable essentials: the two teams, the score, and the game state (period and clock). Avoid stats, ads, or controls, which do not fit a glance.

When should the Live Activity end? When the game ends. Show the final score briefly, then end the activity so a stale score does not linger on the user’s Lock Screen.