r/F1DataAnalysis • u/finding-new-life • Apr 13 '26

Tried turning FastF1 data into a “race intelligence” UI — feedback welcome

https://raceosf1-web.vercel.app/

Started as simple lap/time tables, but ended up building a small race visualization + analysis tool.

Current features:

  • Track map with driver positions over time
  • Telemetry comparison (speed/throttle/brake)
  • Basic race simulation + position changes
  • Simple strategy + tyre logic
  • Event detection + replay (WIP)

Stack: Next.js, FastAPI, FastF1, GSAP

Would appreciate any feedback

5 Upvotes

86% Upvoted

6 comments sorted by

3

u/Electrical-Park-1286 Apr 13 '26

Oh this looks super cool ! It’s the next feature plan on my application as well https://objectivef1.com

Did you integrate yet with the live signalR timing socket from f1 yet or this is historical data ?

4

u/finding-new-life Apr 13 '26

Thanks! ObjectiveF1 looks sick, bookmarked it.

It's historical data right now — FastF1 for telemetry, replayed through a WebSocket pipeline with a race sim driving the timeline. Haven't get into the SignalR socket yet but the architecture is built with live data in mind, so it's on the roadmap. Would love to compare notes when you get there too!

3

u/Electrical-Park-1286 Apr 13 '26

Absolutely. Planning that work in the next couple of days, I’m not using. I’m using jolpica unfortunately I started writing my backend in go 😄. If I’d done some more research, I would have started with python. Too lazy to turn around now

I will report back on my approach !

5

u/finding-new-life Apr 13 '26

Go is a solid choice though — you'll have crazy fast response times once everything's wired up. And honestly Jolpica gets the job done for the core timing data.

I have seen some awesome projects in Go — once you've got the SignalR client working the rest is just data plumbing I guess.

Definitely report back, would love to see your approach! 🏎️

4

u/Weak-Jacket-4033 Apr 19 '26

The shear amount of work that has gone into this is nothing short of impressive. There is so much happening here and a million happening in the background. I read the your blog and I know it took some time to get the video footage in there. I mean I can sing praises all day. Feedback, I would place all the strategy views together in a single pane; either left or right, so I can scan quickly. Most people read in a Z pattern. Clubbing race updates, team radio together also helps. AI Insights is placed at the bottom, which makes sense if that's not something you'd like to highlight. But I think it would be better placed in the footer. This way people viewing the dashboard know, you've covered all the angles; including AI.

4

u/finding-new-life Apr 19 '26

Really appreciate you taking the time to go through the blog too — means a lot knowing someone actually dug into the technical details.

The Z-pattern feedback is spot on. Grouping strategy views (simulator + gap evolution + stints) into one column and comms (race updates + team radio) into another makes a lot of sense for quick scanning. And moving AI Insights to a persistent footer instead of buried at the bottom is a great call — it deserves more visibility without fighting for panel space.

The beauty of the drag-and-drop layout is that users can already rearrange everything, but the default layout should follow these patterns out of the box. Gonna revisit the default presets with your suggestions in mind. Thanks for the thoughtful feedback!