It’s the end of May and time for another update on nitrous,
Team Radio
Quick update on the availability of the team radio data. In the March Update of the devlog, it was mentioned that F1 updated their API and removed the availability of the Team Radio Audio Snippets/Messages.
And we are happy to announce that they added them back to the API, meaning they will be shown again in nitrous. Because of the removal from the API, we removed parts of the code, and we’ll use this chance to implement it better. (No code was actually lost)
Homescreen
As promised in the last devlog, we got around to writing the home screen of nitrous. Currently it’s kept clean and simple, and I hope you like it. We’ll continuously improve and make changes to it if needed.
From the home screen you quickly see the details about the last/current/or upcoming race weekend. And you can start Live Timing or Replayed Timing right from there with a single button click.
Below the Hero section, there’s a list of all past meetings of the current season.
A proper page where the meetings of other seasons will be added in the near future.
Performance & Quality Improvements
Because we are working towards the MVP release, we also want to implement some quick wins that improve the performance and quality of the application. The improvements are mainly in the error handling and load speeds of Replays.
We also improved the F1 Account Login experience; we no longer require a Chrome installation and now use webviews instead.
New Hope for the F1TV Integration
With the rewritten F1 Account Login with webviews, there’s new hope for the F1TV integration. The reason being the working webview implementation. Being in a browser-like environment for DRM playback is a great advantage.
So stay tuned for the next update.
What’s left to MVP?
With the homescreen done, what’s left?
It was already mentioned in the last devlog, but it’s the release process, and that’s what we have been working on the last 2 weeks.
We asked you on the Discord which platform you are using, and we are working on making Nitrous available on all platforms.
We wrote the full CI/CD pipeline, which builds the app for all platforms and deploys it to our infrastructure so we can then provide it to you.
We updated and improved the way we deploy Nitrous to our infrastructure by moving to a helm-chart-based deployment.
And still open are the following points:
Website Update - Add the functionality to download Nitrous and look into release notes on this website.
Auto-update - Add the functionality to Nitrous that it can update itself without you needing to re-download Nitrous from the website and reinstall. This is the biggest point that’s still open, as it’s a really critical feature for a good user experience.
That’s it for this devlog.
Best regards,
- slowlydev