Hey everyone,

As promised here’s a bigger update to address FAQs. I’ll also be engaging in individual threads where relevant but let’s start this way to cover the main topics. I’ve grouped the most common questions into 4 key areas. Feel free to follow up with any additional questions in the comments

1) Content and Ride Contributions

What do we mean by “curated content?” The focus will shift towards making the most of the existing ride library rather than adding many new rides on weekly basis. We want to highlight underutilised rides, continue running tour events with leaderboards and challenges from John Hallas.

We’ll still accept new ride submissions but with a stronger focus on quality over quantity. The goal is to prioritise variety. New locations, different scenery and famous rides rather than just adding “more of the same”. Processing rides takes time and we need to be mindful of resources. Peter and Klem are figuring out the best way to manage this moving forward.

For those wondering about rides they’ve already recorded or plan to record this summer, we’ll find a way to handle them effectively with automated ROUVY Route Creator pipeline. But the details are still being worked out so I can't give you exact details now.

2) Stability and Product Development

FulGaz will continue to be supported on all current operating systems and devices. Moray is already working on critical technical updates (one of those "invisible but crucial" ones). Once that’s in place we’ll shift focus to addressing user reported issues.

To help prioritise what matters most, we’ll introduce a public voting system for bug reports and feature requests. This will help us measure demand, understand the real impact of certain issues and balance development effort vs. how much it actually improves your experience. Some common questions I’ve seen in latest comments and that will need such prioritisation:

• Apple TV issues? Definitely something we can look into.

• Will 4K resolution remain? Yes, absolutely.

• CDN performance? We’re optimistic about improving this.

• Garmin integration? Doable because we have it in ROUVY.

• Post-ride email issues? We know this needs attention.

Again, this doesn’t mean every request will be addressed overnight but we’ll focus on incremental improvements with biggest added value.

3) IRONMAN Rides and Subscriber Base

IRONMAN rides will be removed from FulGaz by the end of September 2025 to align with the start of the next indoor season and they'll only be available in ROUVY. These rides are licensed content and that license is expiring. Just like streaming platforms rotate content, this is a contractual limitation not a choice.

We understand this will impact many users. Based on our data, about 10% of active subscribers rely on these rides. We factored this into our projections along with a buffer for possible underestimates. That said, IRONMAN content has its new home on ROUVY where triathletes can get race ready with official race courses and structured tools they need to prepare.

Some of you raised concerns about what happens if we don’t meet the 80% subscriber retention goal. Well if things don’t go as planned, we adapt. Selling or merging FulGaz isn’t the plan.

There will be marketing efforts, we factored it into the budget, but we need to be smart about how we approach it. This announcement wasn’t made for FulGaz to slowly fade away.

At the same time, FulGaz has to hit certain numbers to stay sustainable. That’s just how it is with any business. The vision is clearly laid out. Now we need to address several topics like content strategy, app stability and support tickets in the coming weeks and months. Beyond that, we adapt while sticking to that vision. I personally believe in Kaizen = continuous improvement, adjusting as things evolve as you can’t see over certain horizon.

4) Subscriptions and Membership Options

If you switched to ROUVY but want to return to FulGaz, no problem. Submit a support ticket and we’ll refund your ROUVY plan so you can resubscribe to FulGaz.

We considered a joint subscription option, but demand didn’t justify the effort required to build it right now. It’s way more complicated than it seems. That said, if enough people want it, we’ll reevaluate it down the line. This is exactly the kind of thing that would go into the public voting system.

Other ideas, like longer term plans or alternative ways to support FulGaz have come up as well. It’s great to see this level of commitment from the community and once we have a clearer picture of how subscriber numbers look over summer we can explore these options further.

Hope this helps answering your biggest concerns!

~Erik

P.S. Again, if you read all here, kudos to you! I'm thinking this would be a good format --> FulGaz Friday Updates? What do you think?