03-10-2016 03:18
03-10-2016 03:18
The suggestion box has to be full by now and it would be nice to see to updates and fixes for the worst problems. How about it FitBit.
Answered! Go to the Best Answer.
03-10-2016 11:30
03-10-2016 11:30
@SunsetRunner @bbarrera @ChaneRZ thanks for your input.
We are compiling some great feedback for future improvements on Blaze, as we do with all of our devices. @bbarrera makes a valid point; any changes do take time. While I don't have any time frames for specific changes to Blaze functionality, you can expect to be amongst the first to know, especially since we announce any and all changes here on the Community.
03-10-2016 09:39
03-10-2016 09:39
They are still thinking about it and trying to figure it out...NOT lol . I don't know. If this was Garmin or TomTom, they would release a patch asap.
03-10-2016 10:25
03-10-2016 10:25
LOL, I don't know, Fitbit and Garmin both seem to take their sweet time dealing with buggy releases.
Seriously its not easy... I've been in software industry for 20+ years, it takes time to fix things and then make sure (QA) so that you don't push out a release with new bugs. Better to be patient and wait until its ready.
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze
03-10-2016 11:30
03-10-2016 11:30
@SunsetRunner @bbarrera @ChaneRZ thanks for your input.
We are compiling some great feedback for future improvements on Blaze, as we do with all of our devices. @bbarrera makes a valid point; any changes do take time. While I don't have any time frames for specific changes to Blaze functionality, you can expect to be amongst the first to know, especially since we announce any and all changes here on the Community.
03-10-2016 11:33
03-10-2016 11:33
I agree with @bbarrera in that any company that continually pushes out updates without a serious quality check is only looking for more problems to deal with.
Then also some of the updates people want, have more to do with the App and not the tracker.
03-10-2016 11:49
03-10-2016 11:49
@bbarrera wrote:LOL, I don't know, Fitbit and Garmin both seem to take their sweet time dealing with buggy releases.
Seriously its not easy... I've been in software industry for 20+ years, it takes time to fix things and then make sure (QA) so that you don't push out a release with new bugs. Better to be patient and wait until its ready.
QA? What's that??! 😉
03-10-2016 12:40
03-10-2016 12:40
There is also the possibility that we will only get a few fixes and no new features. Nothing makes them do anything and we all have to wait for the "new device" for new features.
03-10-2016 12:45
03-10-2016 12:45
@FelixFive wrote:QA? What's that??! 😉
LOL, I'm sure the Fitbit product manager was more concerned about the release schedule than quality... Its just the way the world operates these days, sigh.
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze
03-10-2016 12:58 - edited 03-10-2016 13:00
03-10-2016 12:58 - edited 03-10-2016 13:00
QA quality assurance. Fitbit has teams of engineers, that work in dofferent departments.
Those that are working on, and testing the updates, would not be working on the new tracker release.
03-10-2016 13:16
03-10-2016 13:16
@Rich_Laue wrote:QA quality assurance. Fitbit has teams of engineers, that work in dofferent departments.
Those that are working on, and testing the updates, would not be working on the new tracker release.
LOL, I'm sure the QA comment was a joke... sadly the same joke applies to just about every new product coming to market these days...
Unless you have insider knowledge, don't be so sure that the team working on updates is different than team working on next release. I've been selling to firmware and software developers for a long time and every organization is different (even differences within same organization). Some companies put QA with dev team (say 1 QA for every 3-4 devs), some push QA into the dev team (emerging trend), and others put QA on a different team (= longer release cycles). And as you pointed out, some issues, like Bluetooth issues and platform specific bugs (e.g. Android active minutes) are likely handled by a different team than Blaze firmware engineers. At this point in lifecycle, at many companies, the dev teams are focused on stabilizing the product and resolving known and new issues.
Aria, Fitbit MobileTrack on iOS. Previous: Flex, Force, Surge, Blaze
03-10-2016 14:09
03-10-2016 14:09
@Rich_Laue wrote:I agree with @bbarrera in that any company that continually pushes out updates without a serious quality check is only looking for more problems to deal with.
Then also some of the updates people want, have more to do with the App and not the tracker.
Garmin is the perfect example of this. They crank out updates all the time and wind up breaking more than they fix.
I have a $500.00 fenix3 that just sits in my drawer because it's so buggie, i dont even want to use the thing.
03-10-2016 15:10
03-10-2016 15:10
Please add the ability for the Blaze to show all notifications on iPhone like the Martian Notifier or Garmin!
03-15-2016 14:01
03-15-2016 14:01
Marked as solved. LOL