When will the next firmware update come to the ionic?

[soguilk]

I am saddened that my thread was deleted. As it had shown valuable insight by many users both that are in support of the ionic and those that are troubled by what appears to be a lack of communication in terms of improving the ionic. I think its very clear that as of right now, there are many first time users and fitbit users (like me) that are quite frankly disappointed with the smartwatch feature of the ionic (the fitness tracker feature is great). As I have mentioned on my previous posts I am intent on keeping my ionic. However, communication between the company and customers such as myself is something that might help alleviate my concerns. Lets be real here: the company is struggling financially. If you guys want loyal customers then treat your costumers with loyalty as well. That means answering hard questions and dealing with customers like me who is financially conscious about my purchases ($300.00 to me is not cheap).

Here was my original question: When will the next firmware update come to the ionic?

Here is the solution provided before deleted: by @MatthewFitbit

"Since this thread has unfortunately devolved into petty arguments and personal attacks, I'm just going to remove the whole thing.

The answer to the original question is that Fitbit is very excited about Ionic's next firmware update, and we think customers will be very pleased with the improvements and additions that update will deliver. We haven't announced a timeframe for this update's release, and appreciate everyone's patience while we continue working hard to make Ionic an amazing Fitbit product."

Here are my follow up questions:

What are potentially going to be updated in the next firmware?

Will there be a calendar and reminder function that will be implemented?

You mentioned that "Fitbit is very excited" and "customers will be very pleased" about the upcoming update, can you please elaborate?

Will a firmware note be provided for us?

Please understand, that I am just seeking answers NOT to be difficult but to have an informed decision regarding my purchase.

Moderator Edit: Clarified subject

[Hesooo]

Id love to know that also.

[SunsetRunner]

Well, as tends to be the case with any developer, you’re (we’re) unlikely to find out until it’s released. Change logs aren’t provided until after the event and, generally speaking, you don’t get notification until release. So I think you’ll be wishing on a prayer and heavily speculating until whenever.

But nice to know they think we’ll be pleased.

[MatthewFitbit · Accepted solution]

@soguilk The original thread was not removed because of your question, but because the majority of the content became off-topic and inflammatory. I share your confidence that we can have this discussion without such elements.

I'll offer a bit of insight into how Fitbit approaches development. Our teams have been hard at work since before Ionic's launch on developing content for the next firmware release. Over the past few weeks, Fitbit Support has been regularly meeting with developers and executives to relay first-impression feedback from customers, to which the Community Forums are a major contributor. Everything from unanswered questions to potential bugs and feature suggestions gets reported and discussed - and based on that, a collaborative team decides what development will be most valuable to customers for the next update.

Once that decision is finalized, we set a timeframe and a plan for getting the work done and delivering the next update in a timely fashion. We don't announce the specifics of what that update will contain or when we expect it to release because those things can sometimes change during the development process. I understand that customers like you are interested in knowing what to expect, but we simply don't disclose that kind of information ahead of release.

With Ionic specifically, we are excited to welcome third-party developers into this process. While the Fitbit team will always be involved in the aforementioned refinement and improving of products, third-party developers will be able to use the Fitbit SDK and contribute to the upcoming App Gallery with watch faces and apps (such as the ones you mentioned). While there are obviously boundaries to what a company can accomplish within its resources, the limits of the developer community are as vast as its contributors. 

Hopefully that helps to explain the situation a little more. The feedback on these forums is definitely being heard, and we are very excited about the next firmware release, as well as the potential of the upcoming App Gallery.

[soguilk]

Thank you for the reply. I appreciate you trying to answer my question. I hope that " first-impression feedback from customers" are really being considered as you say. I also hope you see that while everything you mentioned are obvious to tech-enthusiast, early adopters and developers, it is not obvious for regular consumers such as myself.

If I may add these are some issues that I believe can really deter new users from appreciating the ionic.

 - the setup from opening the ionic to full use (strava, firmware update, pandora music transfer) is cumbersome. it takes too long, very agonizing.

 - Bugs, many many bugs. (I feel that this is something that you guys are already prioritizing).

 - Music provider - I have used Pandora, Spotify, Apple music, and Amazon music. Support for spotify is a MUST have. (I know negotiations fell off at some point supposedly but you really need this).

 - Smart features - I realize that this is highly dependent on the community and other developers but please have some of the basic ones that other wearables have had 2 years ago. Ex. text message reply, Calendar, see stocks, etc.

[SmyrnaSoccerRef]

@MatthewFitbit, Thank you for the update, and for the insight into your development team's methodology. I agree with almost all of the points you made, and am glad to see (but also expected) that the team is indeed using our feedback on both bug fixes and enhancements as part of the equation to finalize the items in scope for the next release. Having been in I.T. in various roles from programming to management for over 30 years, I can appreciate the difficult but necessary product development decisions that must be made, and then sticking to it without allowing perpetual scope creep to derail those decisions. 

The only suggestion I would make however is to be more transparent regarding dates and expectations.  Maybe Fitbit is feeling a bit gun-shy regarding setting expectations after the negative press that was written due to the delays in the Ionic's release dates?  If so, that's understandable.  From a customer point of view, even a broad statement that says something like "We have identified a number of bug fixes and enhancements that are to be included in our next firmware release, and we currently expect that to occur in late Q4 2017 or early Q1 2018." would at a minimum give your customers a firm indication that the company is actively making improvements. That statement doesn't reveal any details about the items included/excluded, and gives the development and QA teams some flexibility on dates, but also gives your customers an awareness that improvements are forthcoming within a reasonable range.  The worst thing you can do is not communicate, or go lonnnnnng periods of time without communicating anything.  That can lead to a feeling of apathy and abandonment by the company, and by the consumer.

We trust that you will keep us posted on new information as it is given to you. Just let us know periodically that activity is indeed happenning, and when you are authorized to provide a date, or even a date for a date (i.e., "we will be able to announce a date for the next firmware release on or around mm/dd/yy") , we will all appreciate knowing about it.

[soguilk]

Thank you sir for that beautiful response @SmyrnaSoccerRef.

That is exactly how I would have loved to explain how I feel in a beautifully written opinion. 

I understand we cannot get exact dates. But how Fitbit communicates with its customers matter. Especially. Now when many customers such as myself are dying to see new apps on the ionic. 

[SunsetRunner]

Apple doesn’t give dates, neither google. Microsoft didn’t with its band either. Why do you expect Fitbit to be any different?

[SunsetRunner]

---

@SunsetRunner wrote:

Apple doesn’t give dates, neither google. Microsoft didn’t with its band either. Why do you expect Fitbit to be any different?

---

Exactly. It's agile.

https://en.m.wikipedia.org/wiki/Agile_software_development?wprov=sfla1

[jkimrey]

Not to nitpick but it's my understanding that Agile does tend to promise a timeframe (date); it's the deliverables that may change.

[SunsetRunner]

---

@jkimrey wrote:

Not to nitpick but it's my understanding that Agile does tend to promise a timeframe (date); it's the deliverables that may change.

---

Discussion here:

https://softwareengineering.stackexchange.com/questions/274203/are-deadlines-agile

The main thing to take away here is it that the situation is complex. It is a pretty unrealistic to expect to be supplied deadlines just because you are a customer and you want it... nowadays .. you simply  just have to wait until it is ready or almost ready.

[jkimrey]

I don't think it's a "deadline" that is being asked, instead it's more of an expected timeline or roadmap.

A deadline would be "on November 5th the following will be corrected..."; a roadmap would be something like "a release is targeted for early Q4 which will address bug-fixes as well as performance improvements".

I don't think expectation that a company would provide customers with a roadmap is unrealistic, especially for a new product just released that has significant issues to be addressed.

[SunsetRunner]

---

@jkimrey wrote:

I don't think it's a "deadline" that is being asked, instead it's more of an expected timeline or roadmap.

A deadline would be "on November 5th the following will be corrected..."; a roadmap would be something like "a release is targeted for early Q4 which will address bug-fixes as well as performance improvements".

I don't think expectation that a company would provide customers with a roadmap is unrealistic, especially for a new product just released that has significant issues to be addressed.

---

Customers I'm sure would love that idea, until one day they find that their preconceived expectations have not been met for whatever reason. Also Fitbit's rivals and competion would love it as well.

Hence the reason why it does not happen that often!

Customers just love to be stroked and feel important, but ultimately it's the results that count.

[jkimrey]

I don't want to clog the threat anymore, so we can just agree to disagree on this one. 🙂

Having said that, @MatthewFitbit - I really appreciate your earlier post.

Looking forward to hearing from you again when more details can be shared.

Thanks again.

[DIKKE]

@lostlogik  :For the very simple reason that my notifications are still sometimes working, and sometimes not. So, if i get a rough timeline, i can decide to send it back and ask for a refund, or wait for the update?

[avanarden]

@SunsetRunner

"Apple doesn’t give dates, neither google. Microsoft didn’t with its band either. Why do you expect Fitbit to be any different?"

Fair point. However, fitbit released a product that most user don't see as being ready. People that are sticking with the device are swallowing the initial disappointment and hoping for improvement in an upcoming update. As the 45 day return policy counts down, users are really asking; Is there hope or should I give up now?

[IonicAndy]

Hopefully the next update will fix the GPS distance issue and also the random bluetooth disconnect with headphones. Especially annoying on a run since you have to end you workout in order to reconnect the headphones. If these things aren't being addressed then I'll be steering clear of future products. Happy to wait for fitbit pay, streaming music support, a reliable weather app and additional apps - need to get the basics sorted first though.

[SunsetRunner]

---

@avanarden wrote:

@SunsetRunner

"Apple doesn’t give dates, neither google. Microsoft didn’t with its band either. Why do you expect Fitbit to be any different?"

Fair point. However, fitbit released a product that most user don't see as being ready. People that are sticking with the device are swallowing the initial disappointment and hoping for improvement in an upcoming update. As the 45 day return policy counts down, users are really asking; Is there hope or should I give up now?

---

You may not see the product as being ready, but I don't see this as changing anything. There is always whole load of bugs when new Android/MS/Apple operating systems are released btw.

No pre-information is going to help you make a judgement about returning it. It is what actually happens or blind faith that will be the judge of that. Regardless you're not going to get anything much until they roll out releases, might as well accept it.

[SunsetRunner]

@IonicAndy

Whilst aware of the Bluetooth disconnect issue, I seem to recall a work-around was to pause the music at about 20 mins then play it again. That way the disconnect was avoided, as it had to do with "idle state shutdown" and pausing playing kicked the idle state. 

[bbarrera]

I've developed software and worked in the software industry for 30 years.

Quite often, its simply not possible to give dates until the software has been tested and enters the release process.