Ferrari’s fan app adds an AI race timeline and summaries for every session

IBM and Scuderia Ferrari HP are extending the app from race recaps into live session context, games and fan stories.

IBM and Scuderia Ferrari HP announced new features for the team’s mobile app on 22 October, ahead of the United States Grand Prix weekend. An automated Race Timeline presents key session events in a scrollable visual sequence, while AI-written Race Summaries now extend to practice, sprint, qualifying and the race.

The summaries use agents built with IBM watsonx to combine race data with insights from Ferrari’s drivers and team principal. IBM says the narratives appear within minutes of a session ending. The app is available through Apple’s App Store and Google Play.

Other additions include a tire-selection reaction game and Tifosi Hub, where the team can showcase fans’ six-word stories. Together, the features connect race information, participation and community in a single product.

Two ways to understand the same session

A timeline and a summary solve different reading problems. The timeline helps a fan locate an event: a pit stop, changing weather or a safety-car intervention. A narrative can explain how several of those moments combine into a wider account of the session.

That pairing is especially useful in sports, where the audience’s available time varies sharply. Someone following live may need the latest event immediately. Someone returning after work may want a compact explanation of what changed and where the decisive moments occurred.

A well-organised session record can serve both readers. The event sequence gives a narrative its anchors, while a summary gives those anchors context. The app’s expansion across practice and qualifying also extends the story beyond the final race classification.

AI inside the publishing workflow

The product illustrates a growing role for AI in turning structured information into a reader-facing account. The starting material is already tied to a particular event, rather than an open-ended request to describe a sport. That gives the publishing workflow a natural schedule and a bounded set of inputs.

For a media team, the design questions concern how the information moves. A session finishes, the relevant data becomes available, a draft is produced and the reader receives a coherent update. The elapsed time matters, but so does consistency between the timeline, the narrative and subsequent corrections.

Readers should be able to move from a high-level recap back to the particular moment that supports it. That connection can make an automated summary more useful than a stand-alone paragraph, especially when strategy changes throughout the session.

Engagement extends beyond the recap

The reaction game and fan-story hub add activities with a different rhythm from live reporting. A game invites repeated participation; a short personal story gives supporters a way to express identity. Those features can keep an app relevant between race weekends as well as during them.

The combination also broadens what a fan product has to coordinate. Session data, generated text, game state and submitted stories each need their own content path, yet the person using the app experiences one destination.

The current release is therefore a useful example of AI being integrated into an existing media service. The announced value lies in specific reader actions: scanning the session, catching up on its story, playing a short game and contributing to the community. Those actions offer a more concrete way to understand the update than treating the presence of a language model as the feature itself.

Sources

- [IBM and Scuderia Ferrari HP Expand AI-Powered Fan Experience Ahead of the United States Grand Prix](https://newsroom.ibm.com/2026-10-22-ibm-and-scuderia-ferrari-hp-expand-ai-powered-fan-experience-ahead-of-the-united-states-grand-prix) — IBM · 2026-10-22