News

Hello everyone,

Hope you’ve had a great week! Time for a recap of what’s been happening on FulGaz.

This week marks the start of our new content strategy and the launch of FulGazette, replacing the Top Up Tuesday emails. It’s your new weekly digest with all the latest info, challenge rides, updates, special events and more! While this week’s edition doesn’t include a new ride collection (we’re moving to monthly ride drops), Pete is already working on fresh content behind the scenes and you can expect the next batch in May. In the meantime, look out for a beach themed mini tour coming in April!

We’ve also been fine tuning the public voting system at feedback.fulgaz.com. You can now log in with FulGaz account credentials. Just a heads up for a minor thing we’re tweaking as I’m writing this, the best method is to first log in at members.fulgaz.com, then go to the Feedback site and click Log In with FulGaz account. If you’re not already logged in, it won’t redirect back properly but this will be resolved early next week.

This Feedback site lets you report bugs (which as communicated earlier will get the majority of development time), submit feature requests (like the Garmin integration) and get notified about updates to any posts you’ve submitted, commented on or upvoted. You’ll also be able to follow the FulGaz Friday posts in the News section, just subscribe there for updates! We’ll also start logging internal bug reports here so this becomes your single source of truth for FulGaz development.

Speaking of bugs, we released the much discussed new Windows version this week. While it’s running smoothly for most users, we’re aware of a few issues that we’re actively working on. A hotfix is in the works and expected early next week:

• Crash on Startup: A few users have reported the app crashing immediately after opening

• Oversized Thumbnails or Text: In some cases, the app doesn’t scale correctly and a temporary fix is to adjust your scale settings in Windows display preferences

• Zoomed-In Video Playback: Likely related to scaling, but ending and restarting the ride may help; this issue seems to affect downloaded rides more often than streamed ones

We really appreciate all the feedback and tickets you’ve sent to support@fulgaz.com, it helps us spot and fix these issues faster. If you’re seeing anything else, please head feedback.fulgaz.com and log it there directly.

That’s it for this week. Thanks again for your support, have a great weekend and as always, stay fit and keep riding!

~Erik

Happy Friday!

How’s everyone doing? Time for a quick recap of what’s new this past week!

On the content side, a new mini-event is in the works and we’ve pulled one last trick out of the sleeve before shifting to the new content strategy next week. So enjoy the final Top Up Tuesday before it transforms into… well, more on that from Klem next Tuesday (and this time for real! :D).

Otherwise, we’ve been heavily focused on development and we’re happy to announce that FulGaz is now officially migrated out of IRONMAN systems and fully running on ROUVY’s infrastructure! We’ve also squashed a bunch of bugs in the new Windows version which is scheduled for release next week. With that, FulGaz will be fully running on the new MAUI framework, a transition that’s been a looong time in the making.

And just to clarify, IRONMAN content remains available until September 30, 2025 so no worries for athletes training for their events.

I also promised an update on the public voting system so consider this Step 1. You can now preview it at feedback.fulgaz.com. For now, you’ll find this and past FulGaz Friday Updates in the Changelog which I’ll start posting there exclusively over the next few weeks. The next step? Enabling FulGaz account login so you’ll be able to submit feature requests, report bugs, track progress on a public roadmap and best of all, get notified about anything you post or upvote as well as receive these weekly updates directly in your inbox!

That’s it for this week! Thanks for your support, enjoy the weekend ahead and as always, stay fit and keep riding!

~Erik

Hey everyone,

Another week down and it’s time for your Friday FulGaz Update! Here’s a recap of what we got done (and a bit of foreshadowing on what to expect).

On the content side, Peter managed to set up several new rides before heading off on holiday. He’s also been refining the video editing process which will streamline future ride releases. That being said, new ride collection is already in the works.

Support is running smoothly and keeping the queue in check has allowed us to maintain fast response times. Huge shoutout to Klem for staying on top of it all while also finalising the new email content strategy with Pete. This will bring you weekly emails featuring your favourite John Hallas challenges, updates on new ride collections and refreshed tour schedules. Expect more details from Klem in your inboxes next Tuesday!

On the development side, we’ve assembled the Windows Alpha tester group and a big thanks to everyone participating! It’s already helped Moray catch a small bug ahead of the wider release. With this Windows update we’re also completing the migration to the MAUI framework (for the more technical folks here) and if all goes well we’re aiming for release next week

What does this mean for you? This will mark the kickoff of our new development strategy. With a feature freeze in place, updates will now focus on bug fixes and stability rather than waiting for feature development across all platforms. Platform specific updates (like the problematic Apple TV) will now happen independently rather than being bundled into joint platform releases. We’ll also continue community testing in small groups (like the Windows Alpha tester group) to catch issues early and ensure a smoother experience for everyone.

On the infrastructure side, we're finalising the migration away from IRONMAN systems together with ROUVY engineers (ETA next week as well). This will allow us to improve our issue monitoring and thus identify problems with bigger blast radius faster. One great example? Post ride emails. We found the root cause behind missing emails and it’s now 99.99% fixed (no person working with data at scale will tell you 100%, sorry :D) so you should be receiving them properly. If you’re still missing any check out this Knowledge Base article on how to reupload past rides: https://support.fulgaz.com/hc/en-us/articles/360044708871-My-ride-ended-and-or-did-not-upload-can-I-recover-the-data

Next milestone for post ride feature? Garmin uploads. Since this requires a coordinated release across all platforms it won’t be the very next fix but it’s definitely on our radar. We've also started discussions on setting up a public roadmap and feature request system to bring even more transparency to what’s happening. More on that from me in next Friday’s update so stay tuned!

That’s it for this week! Thanks again for your support, enjoy your weekend and as always, stay fit and keep riding!

~Erik