So for those who are looking to FitBit to fix this problem, I have been told by support that it has been "fixed". The problem is, the "fix" is worse than the original broken feature.
Problem: FitBit app on all platforms deletes old notifications after 30 days, except that it doesn't work on the iOS version of the app.
FitBit solution; Keep "only" the first 100 notifications. Delete all older ones, but don't announce the new feature, and don't include info about it in the release notes.
I don't know about you guys, but I don't yet have 100 notifications, and I'm already frustrated that the list isn't being cleared. (More so, I'm frustrated with how poorly FitBit is responding to the problem.) I certainly don't want to wait until I have 100 to see them just start to disappear. I would really like to be able to see that this feature actually exists. As it stands now, I have no idea if this new "feature" is for real or just a phantom whipped up quickly by the support folks on FitBit's Twitter page.
Bottom line: This "feature" does nothing but further annoy and insult users.
For those not interested in the whole thread, let me quote the last two bits of the conversation:
Me: So let me see if I follow this correctly - you had a 30-day delete feature in all platforms, but it didn’t work on iOS, so you replaced with a watered-down feature which deletes any message beyond 100, which is of little-to-no use to anybody. Since many users don’t have over 100 messages, they may never know whether the feature is working. Between that and the fact that your release notes do not introduce this new feature, there’s no proof that it actually exists or works. So how is this good for your customers?
FitBit Support: We appreciate your feedback but this is how the notifications work now. You can let our developers hear you by voting and commenting to the feature suggestion that we previously provided. Thanks for your understanding.
"...this is how notifications work now". Wow. What an incredibly sorry excuse for customer service. I don't mind bluntly being told the truth, but FitBit seems to be going out of their way to avoid talking about this issue. Both the "fix" and the response are terrible. (For that matter, since the "fix" is no better than the problem, and is almost indiscernible from from current behavior, I really do doubt that it exists.)
So if this bothers anybody else as much as it does me, go pound FitbitSupport on Twitter with tweets telling them how you feel. Don't use the link on their support web page, it will generate a Direct Messages, which is private. Tweet them publicly so that your voice can be heard.
If this is representative of the level of support that FitBit offers, (evasion & deception with a saccharin-sweet smile) I may have to start looking at competing products.
For those curious about my conversation with support, please see the screen shots below:
Best Answer
