Experience live telemetry and timing data from Formula 1 races. Get insights into leaderboards, tire choices, gaps, lap times, sector times, team radios, and more.

For sometime I have been using a real-time Formula 1 Live Timing Website called f1.tfeed.net. But I always didn’t quite like the UI of it, its a great website for functionality don’t get me wrong but the UI looks quite “old”. So I decided to write my own Formula 1 Live Timing Dashboard. For now It looks like this:

And with the next GP coming right up, I thought now would be a great time to “release it to the public”.

So here is the f1-dash Website

Its has been In the works for a couple Months now, mainly because I wanted to over engineer it, but failed.

Its also completely free to use, as well as open-source on Github, so If you would like to contribute, feel free.

I hope u like it and have fun using it.

Things Id like to do next are:

  • Race Schedule of Current Seasons and Past Seasons
    • Because of that maybe a replay option of old races
  • Head to Head View
  • Favorite driver Highlighting
  • Position after Pitstop
  • Graphs for Gap and Laptime
  • Write backend in Rust
  • LittleWizard@feddit.de
    4·
    1 year ago

    I’m currently testing this during qualifying. I have an issue, that all updates stop after a couple of seconds. Is this because your server is overloaded? I tested Firefox and Vivaldi mobile (also using the desktop website).

    I have to say though as long as I got updates, it was mighty impressive. Keep up the great work! I may have to test running the code in my own machine.

    • Slowlydev@programming.devOP
      2·
      1 year ago

      Yeah I also noticed this, definitely something is going wrong. The server was under some use because the backend is hosted on an old desktop of a friend which also runs other game servers, which probably impacted performance.

      Yeah go ahead and run it on your own machine, all you need is bun, node and yarn :)

      But thank you for your feedback 🙏🏻

    • smegEnglish
      2·
      1 year ago

      I’ll second this, it was brilliant when it was working! I assume it’s just the old hug of death, but great work otherwise OP!

        • smegEnglish
          2·
          1 year ago

          Honestly aside from it freezing a few times it was really cool to use! Getting the mini-sector time colours is way more detail than I was expecting, and the delay-to-sync-with-your-stream option is such a good feature.

          • Slowlydev@programming.devOP
            2·
            1 year ago

            Thank you I appreciate it a lot. The mini sectors were a big part of why I wanted to create f1-dash 😅 And the delay feature Is still a bit wonky but I really wanted to add it because its such a bad feeling getting spoilers from the live timing 😂

    • Slowlydev@programming.devOP
      1·
      1 year ago

      I deployed a new version of the backend, im gonna test it during the race, if it doesn’t work, I’ll revert to the old version. Let’s see how this goes…

  • fisco™🇬🇧🇺🇦@lemmy.ml
    3·
    1 year ago

    Well this works really well, very easy to follow what’s happening, the team radio recordings are really cool too. One thing I noticed, the actually time, doesn’t appear to be either local or my time…for example, the session was green flagged at 12:30 local time, (11:30 BST) in app it said 10:30…🤷🏻‍♂️

  • spacebug@feddit.de
    2·
    1 year ago

    Works really well for me for now, and looks fantastic. Just the team radios sometimes showed a 100% bar and did not play in Safari on the iPad.

    The delay to stream is perfect, maybe save the value to the local storage to save it during reloads?

    • Slowlydev@programming.devOP
      1·
      1 year ago

      Okay will take a look at the Team Radios. The delay is a feature I wanted to get out asap, but I am gonna revisit it again and make it better, the saving is definitely a good idea!

    • Slowlydev@programming.devOP
      2·
      1 year ago

      Yeah it’s a known issue, Safari doesn’t like the SVG text updates. I need to take a deeper look into that once. But thanks for the feedback!