This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Are there any reason to explain progressive rollout for Marq ? (Don't see the point)

Are there any reason to explain progressive rollout for Marq ?

It is understandable what it is for, even though V10.00 was in progressive rollout , and V10.10 was pushed a few time later, as a Weather Widget latest cure.

But I don't think that we are as numerous people who had bought a Marq watch as Fenix 6, and i don't understand reasons why is firmware 10.10 under progressiv rollout.

Not to be someone flogging a dead horse, but definitively don't see the point.

  • Or just post the bits in this board for those who wish to install.

  • Agree ! Especially as border between official and beta firmware is thin and fragile.
    Don't get me wrong. Appreciate firmware's evolutions, and program. Juste the final progressive rollout is a mess.

  • Of course there is ... just to train people to be patient again in this fast world  ...  ;-)

  • Training people to be patient knowing that 10.10 solves every known problems...not sure it is good strategy.

  • Watches are a minor part of Garmin's enterprise.  A simple, common-across-all product lines approach keeps it simple from the standpoint of employee training and this approach spreads the server load across time.  That is my thinking, but only a guess.

  • Server/network capacity management/balancing is one of the reasons. If Garmin didn't use any rollout procedure thousands of devices would want to download the latest firmware within a short period of time after the release and it could overload their system or cause disruptions in other services too as most probably they don't use separate infrastructure for each of their services.

    Of course, it can be easily solved by up-scaling the infrastructure for that period of time but from business point of view it is an unnecessary cost which would be needed to spent on every release.

  • Another reason is if there's a problem in the update, less people will have it instead of all. For example, Fenix 6 software version 10 had some problems and they were reported even before it reached my watch. Next Garmin pushed update 10.10, so I didn't get the faulty update.

    The problem was maybe a small thing but, think it as some watch breaking update. What happens to all the watches in a short time?..

  • You all guys are right, and appriciate Garmin's helping hand you've given them to try to justify or explain what's going on. None of the reasons expected you've given here, are ignored by this thread.
    But, considering that Garmin is a third place smartwatch seller, it's time for them to upgrade their policies, given their new leaderchip in the business, price of the their tools, etc. Don't you think ?

  • I am not sure why my comment was down-voted, but anyway.

    We gave explanations about the most probable reasons in business and technology point of views, however it seems you consider everything which is not your expectation as justification.

    I am also not sure I understand why a rollout policy should be affected by the business status or a price of the device.
    We are speaking about that some people receives updates a few days later than others. Is is really that bad? If you want to enjoy the new functions/fixes as soon as possible you can still download the RC.

    Even if it's not always obvious, in my experience, every company has similar methods.

    Additionally, we are in a very good position I think compared to the APAC models where they will receive updates months later.

  • It is a practice used in even mobile phone app stores. I understand the roll out procedure but it can be faster. I have Fenix 6X Pro and usually get the updates probably after the rollout stage %80. And it takes almost a week. This should be accelerated I think.