Improved process for faster updates in GAM

[Maxim_]

Shift review and test effort for updates from review team to developer by adding test steps checkboxes to GAM. These checkboxes should describe mandatory test steps for the developer before an update can be submitted and published without a review by review team. There should still be random chosen updates that must pass a review by review team.

[YojanaFitbit]

Hi @Maxim_, and thanks for taking the time to share this suggestion about improving process for faster updates in GAM. We rely on feedback like yours to help us develop products and features that we know our community wants to see. If this suggestion receives votes from other customers and gains popularity, it will be shared internally with various teams at Fitbit. To learn more about how Fitbit decides which suggestions get developed, visit our FAQs.

Watch this space for status updates. In the meantime, try visiting Health & Wellness to talk with other members about all things health and fitness.

[chris_starwf]

Would be better if updates were published automatically, without review. The description and the images can be updated anytime, without review, why not the watchface itself? It will be a win-win-win situation, happy customers, happy devs and less work for Fitbit reviewers. Why do we need to wait over a month to get an update published? Now with the release of 5.1, probably will take months or years for us to update all our inventory (if an update is really needed) 😢

There is a report system in place and users can flag buggy apps that don't work. An algo can be made to review the watchfaces that get reported for being buggy or that have low ratings since the last update. For example, Garmin doesn't review the updates and everything works ok. Customers are happy that bugs get fixed in minutes after they contact the developer.

[Maxim_]

It's just a proposal for a faster process for updates. The reviews by review team could cover some optional test steps that the developers don't have to do, which may lead to better quality. I think it is up to Fitbit optimize the update process to fit their strategy. I also think that we all agree that the current process should be improved to deliver a better experience for everyone (Users, Fitbit, Devs, ... ).