Devil’s in the details here, but it sounds to me like the blame is on Abbott’s dev team here. Apple doesn’t just drop iOS versions out of nowhere; the beta has been out for months and developers...
Devil’s in the details here, but it sounds to me like the blame is on Abbott’s dev team here. Apple doesn’t just drop iOS versions out of nowhere; the beta has been out for months and developers have had plenty of time to test and fix issues with their app.
I don’t disagree with the author suggesting that maybe not everything should be a smartphone app, but the headline reads as though Apple is breaking these devices. This sounds to me like a failing on the part of the app developers for not preparing their software for a major OS update.
I don’t have any insider insights or anything it I’d bet that this is the result of yet another company treating software as a checkbox; that is, they contract it out to the lowest bidder and...
I don’t have any insider insights or anything it I’d bet that this is the result of yet another company treating software as a checkbox; that is, they contract it out to the lowest bidder and promptly forget about it when they should really be hiring on a team of full time software engineers to properly maintain their app.
It would make me happy to see some new regulations surrounding non-optional software like this that not only requires in-house development and maintenance of such software but also enforces a certain level of quality. Yes that’s expensive, but realistically if a company can’t afford to develop proper software for the hardware they sell they shouldn’t be in the business.
If Apple didn't provide an easy way to bypass the new functionality, "complete rewrite of how we do what we do" could take a good bit more time than a few months, especially if Apple isn't willing...
If Apple didn't provide an easy way to bypass the new functionality, "complete rewrite of how we do what we do" could take a good bit more time than a few months, especially if Apple isn't willing to budge.
I know medical software in general tends to be write-once software, which is a bit of a problem sometimes. OTOH it prevents a lot of that needless tweaking that many other sectors spend too much time on.
I know there have been many times my college has told Mac users to hold back on major version changes for a few months to insure that all of the required vendor software works in the new version. M1/M2 Macs were not reccomended for some time due to some of these complications.
Given my long usage of the Libre monitors and the experiences with them I have a hard time believing that this isn't explicitly their fault. The original Libre worked no problem. Then the Libre 2...
Given my long usage of the Libre monitors and the experiences with them I have a hard time believing that this isn't explicitly their fault.
The original Libre worked no problem. Then the Libre 2 came out and 1/3rd of all the sensors just don't work or drop connections constantly while forcing me to switch to juggluco instead of the official app due to a complete lack of settings and blasting max volume alarms. Now the Libre 3 exists and they're just as prone to failure as the 2 but harder to get working with third party apps.
There's not much Abbott could say here to make me believe they didn't just completely drop the ball on their already zero effort app development.
The maker of the FreeStyle Libre 3 glucose monitor is warning users to 'disable automatic system updates on your iPhone' because it could break a core functionality of the device.
One of the largest medical device companies in the world is warning some of its diabetic customers not to upgrade to iOS 17 and to disable automatic updates because a new feature may break some key functionality on several of the company’s glucose monitors. The affected features include alarms that tell users if their glucose is too low or too high, a sign that they may need to take immediate action.
Owners of the FreeStyle Libre 3, one of Abbott Laboratories’ flagship glucose monitors, received an email this week warning them to “disable automatic system updates on your iPhone” because the new operating system’s StandBy Mode and Assistive Access Mode “may impact your ability to receive time-sensitive notifications including glucose alarms and notifications indicating that alarms are unavailable.”
Devil’s in the details here, but it sounds to me like the blame is on Abbott’s dev team here. Apple doesn’t just drop iOS versions out of nowhere; the beta has been out for months and developers have had plenty of time to test and fix issues with their app.
I don’t disagree with the author suggesting that maybe not everything should be a smartphone app, but the headline reads as though Apple is breaking these devices. This sounds to me like a failing on the part of the app developers for not preparing their software for a major OS update.
I don’t have any insider insights or anything it I’d bet that this is the result of yet another company treating software as a checkbox; that is, they contract it out to the lowest bidder and promptly forget about it when they should really be hiring on a team of full time software engineers to properly maintain their app.
It would make me happy to see some new regulations surrounding non-optional software like this that not only requires in-house development and maintenance of such software but also enforces a certain level of quality. Yes that’s expensive, but realistically if a company can’t afford to develop proper software for the hardware they sell they shouldn’t be in the business.
If Apple didn't provide an easy way to bypass the new functionality, "complete rewrite of how we do what we do" could take a good bit more time than a few months, especially if Apple isn't willing to budge.
I know medical software in general tends to be write-once software, which is a bit of a problem sometimes. OTOH it prevents a lot of that needless tweaking that many other sectors spend too much time on.
I know there have been many times my college has told Mac users to hold back on major version changes for a few months to insure that all of the required vendor software works in the new version. M1/M2 Macs were not reccomended for some time due to some of these complications.
Given my long usage of the Libre monitors and the experiences with them I have a hard time believing that this isn't explicitly their fault.
The original Libre worked no problem. Then the Libre 2 came out and 1/3rd of all the sensors just don't work or drop connections constantly while forcing me to switch to juggluco instead of the official app due to a complete lack of settings and blasting max volume alarms. Now the Libre 3 exists and they're just as prone to failure as the 2 but harder to get working with third party apps.
There's not much Abbott could say here to make me believe they didn't just completely drop the ball on their already zero effort app development.
Maybe a notification permission setting?