3 ms·

No, I think that is exactly what happened. They wanted to merge their Android and iOS teams. I described one major bug (the alert stacking). It seems pretty ob

No, I think that is exactly what happened. They wanted to merge their Android and iOS teams. I described one major bug (the alert stacking). It seems pretty obviously they are using a cross-platform framework, the buttons and the way alerts are displayed is non-standard. Given that I've never seen a native app struggle so much with it's notifications, I'm going to go out on a limb and say that not dealing with bog-standard native APIs because they are running through a framework might be the problem. Honestly, I kinda think Apple has some responsibility here too. They should reject these apps, or help the companies figure out what is going wrong.

HumblyTossed 2y ago
> They should reject these apps, or help the companies figure out what is going wrong. This is what the 15/30% Apple tax is supposed to be for. I simply don't understand why they drop the ball so much when they're making a mint from developers (and consumers!).
jnsie 2y ago
As a matter of interest, are your issues on iOS or Android? No real reason for asking beyond curiosity...
chuckadams 2y ago
> Honestly, I kinda think Apple has some responsibility here too. They should reject these apps, or help the companies figure out what is going wrong. So it's on Apple to basically become a shadow FDA and maintain their own panel of experts to second-guess the whole FDA review process?
- thejohnconway 2y ago
  If the App Store is meant to have some sort of quality control to justify it’s existence, then yes, they should reject apps this buggy. They want to have health as a major feature of their platforms. To do that, they have an interest in making sure the most important health apps aren’t garbage.
  - chuckadams 2y ago
    From the app's perspective, it's working fine, it's just sending commands that crash the device (and even then, the device recovers, but then it gets sent into a boot loop that drains the battery). Does Apple then need to test the app with the actual device, and revalidate it every time the device is updated? Do they need to hire the expertise in medical devices for such review? I'm fine with more stringent requirements on medical apps, but that should be part of the FDA's review process. Their stamp should actually mean something. If it doesn't, the onus to fix it falls on the FDA (and by extension, the body politic). Apple not so much: their responsibility with health apps has more to do with safeguarding the data's privacy than with the reliability of the device. Furthermore, if you think Apple is asleep at the switch when it comes to quality control, why would you give them the oversight responsibility for life-and-death-critical software? They should take a package digitally signed by the FDA, do the additional testing that actually is in their wheelhouse (such as data security) then if it passes, publish it as-is. Otherwise, back to the FDA.
- HumblyTossed 2y ago
  oh good grief. There are ways to test the app without being a "shadow FDA".
  - chuckadams 2y ago
    I admit I was overly dramatic in that phrasing. But there's only so much one can expect the platform vendor to do when it comes to things like medical devices. I'd rather the certification were by an (ostensibly) accountable agency, not the corporation taking a cut of the profit.

HumblyTossed 2y ago

> They should reject these apps, or help the companies figure out what is going wrong. This is what the 15/30% Apple tax is supposed to be for. I simply don't understand why they drop the ball so much when they're making a mint from developers (and consumers!).

jnsie 2y ago

As a matter of interest, are your issues on iOS or Android? No real reason for asking beyond curiosity...

chuckadams 2y ago

> Honestly, I kinda think Apple has some responsibility here too. They should reject these apps, or help the companies figure out what is going wrong. So it's on Apple to basically become a shadow FDA and maintain their own panel of experts to second-guess the whole FDA review process?

thejohnconway 2y ago
If the App Store is meant to have some sort of quality control to justify it’s existence, then yes, they should reject apps this buggy. They want to have health as a major feature of their platforms. To do that, they have an interest in making sure the most important health apps aren’t garbage.
- chuckadams 2y ago
  From the app's perspective, it's working fine, it's just sending commands that crash the device (and even then, the device recovers, but then it gets sent into a boot loop that drains the battery). Does Apple then need to test the app with the actual device, and revalidate it every time the device is updated? Do they need to hire the expertise in medical devices for such review? I'm fine with more stringent requirements on medical apps, but that should be part of the FDA's review process. Their stamp should actually mean something. If it doesn't, the onus to fix it falls on the FDA (and by extension, the body politic). Apple not so much: their responsibility with health apps has more to do with safeguarding the data's privacy than with the reliability of the device. Furthermore, if you think Apple is asleep at the switch when it comes to quality control, why would you give them the oversight responsibility for life-and-death-critical software? They should take a package digitally signed by the FDA, do the additional testing that actually is in their wheelhouse (such as data security) then if it passes, publish it as-is. Otherwise, back to the FDA.
HumblyTossed 2y ago
oh good grief. There are ways to test the app without being a "shadow FDA".
- chuckadams 2y ago
  I admit I was overly dramatic in that phrasing. But there's only so much one can expect the platform vendor to do when it comes to things like medical devices. I'd rather the certification were by an (ostensibly) accountable agency, not the corporation taking a cut of the profit.