Live Scores with Live Activities
summary
Forza Football builds a native Live Activity that shows match score, minute and latest event but discovers key limits: Live Activities cannot make network requests or be started by push and the system owns the process, so updates must come via remote pushes. Engineering creates an internal UI tool (Xcode previews are too slow), implements JSON attribute + contentState payloads, handles per-activity push token, debugs via Console searching for chromed logs and learns the hard rule that timestamps must change; Apple suggests sending 90 pushes per match, and the final compact Dynamic Island UI ships and boosts CTR and retention.
AI-written summary · about
chapters (18)
- 0:00Introduction to Live Activities
- 1:05What is a Live Activity
- 3:37Live Activity vs Widgets
- 5:00Live Activity Limitations
- 6:46Design Specifications
- 11:18Design Goals and Iterations
- 13:25UI Design Candidates
- 15:11Dynamic Island Design Challenges
- 21:39Final UI Design
- 22:41UI Testing Tool
- 23:46Live Activity Data Structure
- 25:31Updating Live Activities
- 27:58Push Notification Setup
- 29:03Debugging Push Notifications
- 31:55Common Debugging Issues
- 32:37Update Frequency Challenges
- 34:22Apple’s Official Guidance
- 35:27Unexpected Benefits
related talks
01h 00mLive Scores with Live Activities
23mEnhancing App Experiences with App Intents and Live Activities
45mHow Not to Break Things with Live Activity
24mDynamic Island & Live Activities with Flutter & Swift
33mSwiftUI for Flutter Developers
49mAdvanced live streaming
46miOS Infrastructure
41mHow We Built Facebook for iOS