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

[IonicAndy]

Thanks lostlogic, wasn't aware of that one. I will give that a try on my next run. Presumably I pause it from my headphones since any control from the watch is disabled when in run mode.

[Annie311]

Should fitbit not of got the software right before releasing? Or scaled back the MVP to get what you were releasing right? #regrettingnotgettingtheiwatch3

[MatthewFitbit]

@Annie311 I'll assume that you're genuinely asking why software bugs exist, and not just trying to be negative.

There isn't a single reason why bugs exist in software - it can involve anything from conflict with another device's communication method to an extra character left in a line of code. Even after extensive testing, it simply isn't possible to account for the infinite software/hardware combinations and variables that might come up in the real world. Simply put, bugs represent the fact that it's impossible for programmers to account for every last possibility - the product would literally be in testing forever if that was the goal.

Part of every product release is paying close attention to the unexpected behaviors that users might encounter, and working to get those resolved. As mentioned above, the Community plays a major part in that process, and we work to promptly address anything that is significantly impacting the experience, or affecting a large group of individuals.

I'm not sure which bug you were specifically thinking about, but you can be sure that all feedback has been received and considered by our team for the next Ionic firmware update. Hopefully that helps!

[bbarrera]

---

@Annie311 wrote:

Should fitbit not of got the software right before releasing?

---

From my vantage point, Ionic shipped on a management imposed schedule. Happens frequently in consumer electronics world.

[mlindgren]

I'd really like a public bug tracker so we can at least confirm that Fitbit is aware of the important issues and is working on fixes, with or without a timeline. The feature suggestion forum kind of serves this purpose, but it's too disorganized and there are too many duplicated requests, and there's no status which indicates that something is actually being worked on. Having a community manager comment on an item doesn't seem to have any bearing on whether or not it will actually get implemented.

Incidentally, it looks like Fitbit is doing a survey on how the feature suggestion forum should work. I'd highly encourage everyone who posted in this thread to share their opinions in the survey as well: https://goo.gl/forms/LwEnUn26sCMWCVkc2

[SunsetRunner]

---

@mlindgren wrote:

Incidentally, it looks like Fitbit is doing a survey on how the feature suggestion forum should work. I'd highly encourage everyone who posted in this thread to share their opinions in the survey as well: https://goo.gl/forms/LwEnUn26sCMWCVkc2

---

Yeah I did that survey..  Seriously they need to implement the 30 or so requests that are over 1000 votes and just get on with it (once the bugs have been destroyed). Oh and FLAC support LOL.

[MatthewFitbit]

@mlindgren The Feature Suggestion forum is not intended to be used as a bug reporting forum, so I wouldn't recommend filling out that survey with that mindset. However, it sounds like your suggestion lines up with this post, so you might vote and comment there. I definitely understand your interest in a public-facing bug list - that is something that may happen in the future.

The best way to report something that you think isn't working correctly is to post on the relevant product or feature forum, or to contact Support directly so that our team can investigate and take action. Please don't create Feature Suggestions about bugs.

[billdehaan]

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

Speaking as a dev myself, it's also entirely possible to complete internal testing, get ready for release, and find some new showstopper that never appeared in testing. It could be some unusual sequence of events that hadn't been anticipated, or it could be because of an external interface.

Fitbit could test every phone they could think of, release the Ionic, and two days after it's released, Google could release a patch to Android to fix their Pixel 2 burn-in issue, and that patch could cause serious issues with the Ionic.

A lot of time, you're coding to a moving target. This is especially true with a mass market retail product that's sold in hundreds of markets around the world, has to interface with hundreds of phones, versions of operating systems, banking systems, etc.

On the one hand, customers want to know when they can expect a fix, and that's fair. On the other, often developers can't say until they get in under the hood and fully understand the reason for the problem. And the worst thing to do is give a date that then has to be postponed again and again.

[SunsetRunner]

4 likes for that last comment. Glad some people understand.

[Abdoanmes]

I found myself here because I was curious about when the next firmware update might happen. I do find it curious that I am in a forum instead of reading an official Fitbit statement. Based on the release date of the Ionic it appeared Fitbit afforded themselves enough time to potentially release a late Q4 "Christmas present" firmware release. This thread cleared up a lot of the challenges involved and why we don't have a timeline yet. I'd put my money on a late 2017 Q4 release from a sheer business perspective. I say this realizing the technical issues that could arise.

I am happy with the Ionic. I understood this was the first attempt to get into the smartwatch market. I have been a loyal Fitbit from the start because I enjoy the fitness side of the product. I was also a huge Pebble fan. When Fitbit acquired the Pebble software, I knew I would only have to wait for their newest product because wearing a Pebble and a Fitbit was a bit cumbersome. I can see the perspective of new customers being a bit underwhelmed by the feature set out of the gates in comparison to other smartwatches right now. 

At present I have patience and will happily give Fitbit 3 - 4 months to work through the next firmware release, but it would be nice to have a few official insights during that time. The one theme I have seen in this thread and others, is communication. @SmyrnaSoccerRef did sum it up nicely in regard to releasing a broad official statement. Silence induces frustrations and doubt. All of us want to be acknowledged from an executive level we are being heard and things are being done. Giving a statement of reassurance could alleviate any growing discontent and stave off negativity. There's my 2 cents 🙂

[SunsetRunner]

@Abdoanmes wrote:

, but it would be nice to have a few official insights during that time. The one theme I have seen in this thread and others, is communication. @SmyrnaSoccerRef did sum it up nicely in regard to releasing a broad official statement. Silence induces frustrations and doubt. All of us want to be acknowledged from an executive level we are being heard and things are being done. Giving a statement of reassurance could alleviate any growing discontent and stave off negativity. There's my 2 cents 🙂

Well keep on dreaming. It will never happen the updates will simply speak for themselves.

---

[mr_manager]

As a developer and a long-time fitbit user and Ionic seemingly early adopter, I'm kind of disappointed with the byzantine nature of the release schedule. I would think that in this day of continuous delivery we might be seeing bug fixes roll out weekly, if not daily. I have had an ongoing issue with the fitbit deciding my walk is done before I do, and also, I'm getting kind of tired of bringing my hand up "just so" in order to see the time. I am tremendously hopeful that these are two of the issues being addressed in the next release. I'm frankly feeling like a beta tester who wasn't given advance or discounted access to the product I'm actively testing for the company.

[SunsetRunner]

---

@mr_manager wrote:

As a developer and a long-time fitbit user and Ionic seemingly early adopter, I'm kind of disappointed with the byzantine nature of the release schedule. I would think that in this day of continuous delivery we might be seeing bug fixes roll out weekly, if not daily. I have had an ongoing issue with the fitbit deciding my walk is done before I do, and also, I'm getting kind of tired of bringing my hand up "just so" in order to see the time. I am tremendously hopeful that these are two of the issues being addressed in the next release. I'm frankly feeling like a beta tester who wasn't given advance or discounted access to the product I'm actively testing for the company.

---

So you would want to see weekly or daily updates? So you are a developer as well? So could you imagine the QA going on testing builds every day or every week? Hint .. it isn't going to be very good there would not be enough time.

Having updates once a month is good enough me, I don't want to spend my life installing software and I'm sure the testing department is less likely to die of a heart attack from over work. As a Dev I would have thought you could see why daily/weekly is not a good idea. This isn't a video game, the software needs to be tested on tons of devices on multiple platforms. Very complex indeed.

[mr_manager]

Are you a software developer? Do you know about things like automated testing? Regression testing? Curious to know why you are so seemingly against a more responsive development cycle.

[SunsetRunner]

---

@mr_manager wrote:

Are you a software developer? Do you know about things like automated testing? Regression testing? Curious to know why you are so seemingly against a more responsive development cycle.

---

Yes I am a developer and have been a QA tester. If was only given a day to test multiple builds for multiple platforms I'd probably quit. 

You do realise you need to write the software to do automated testing, it does not happen overnight. Automated testing is always playing catch up. Regression is often used of course. There is also a lot to be said do manual testing, employees with deep knowledge can often beat other testing methods.

Whatever method or methods a day or even a week is not enough to test this software over multiple platforms on multiple devices.. if you think it is you are living in cloud cookoo sorry. It would be crazy!! If they did it I wonder how many devices they would end up accidentally bricking.

[mr_manager]

Um, ok. So, then, the answer is "no," you're not a developer. [Edit -- fitWhateverDude seems to edit his posts about fifteen times, so, no, I'm not crazy in saying he's not a developer here. He later went and edited his post prior to this one to add the bit about developing and QA testing. But I'm not entirely convinced ;)]

[SunsetRunner]

---

@mr_manager wrote:

Um, ok. So, then, the answer is "no," you're not a developer.

---

??

I'm a .NET developer I mainly work of Microsoft technologies and C# and C++/ASP.NET, SQL server, and basic scripting such a JavaScript and JQuery. I also maintain a number of servers on the Microsoft platform mainly using IIS and Exchange. I've worked for silicon valley off and on for several years although I'm based and live in the UK. Go ahead make my day Mr Agile.

What's your speciality ? Html?

[mr_manager]

.net... So, basically Java. You seem to be rather defensive and not at all interested in the point I made. It would be in the interest of Fitbit to be more responsive, but apparently you have a personal interest in naysaying. That's great.

[SunsetRunner]

---

@mr_manager wrote:

.net... So, basically Java. You seem to be rather defensive and not at all interested in the point I made. It would be in the interest of Fitbit to be more responsive, but apparently you have a personal interest in naysaying. That's great.

---

Lord no LOL. Java is nothing like .NET technologies. That's like saying Apple is like nVidia. Many of these programming languages are derivatives of C of course but they are nothing like each other. Do you know what .NET even is? It can use multiple languages.

So I said I'm a developer only when you asked me,  stated what I do and asked what you do. You response is to not tell me your Dev skills, and tell me .NET is like Java (most devs will be pissing themselves laughing at this statement btw).

Lol and I say I'm a Dev after you asked, you say I'm not, I show you and you say I have a personal interest in naysaying and I'm defensive. You could not make this up haha.

I was making the point that daily/weekly releases are not practicle and then you start banging on about how I'm not a Dev as though you are more qualified to give an opinion. You later say I'm not interested in your point. I'm starting to wonder if you are the Donald.

You write here in these forums claiming you're some sort of Dev expert and then start finger pointing. I'm kinda glad I called you out now sorry it backfired.

[mr_manager]

Enjoy your day.