3 ms·

Apple has many, many tools to prevent this from being a problem. To name a few: - They can lock the API behind entitlements that must be manually requested and

Apple has many, many tools to prevent this from being a problem. To name a few: - They can lock the API behind entitlements that must be manually requested and reviewed by Apple - They can lock the API behind a user approval - They can regularly prompt the user if they still wish to share notification data with the watch (same way they do to keep giving an app localisation data) - They could enforce that the notification is sent encrypted over bluetooth, without giving access to it to the app itself - forcing its handling to be done on-device - if they're so concerned about this. It's also worth noting that this problem is a complete non-issue for Android, and nobody seems to believe it is an issue there...

JKCalhoun 2y ago
Yeah, you're right. Not easy, but do-able. Apple, probably due to their success and size, are trying "Make me!" as a response until, you know, someone makes them. But they're not willing to voluntarily offer these API up.
burnerthrow008 2y ago
> - They can lock the API behind entitlements that must be manually requested and reviewed by Apple > - They can lock the API behind a user approval Not if the EU has anything to say about it. Apple is already in trouble for requiring prompts for 3rd party vendors, and you know that already. Same for entitlements.
- roblabla 2y ago
  > Apple is already in trouble for requiring prompts for 3rd party vendors Well yeah, they're specifically in trouble for requiring prompts *only for 3rd party vendors*. The problem is that Apple treats their own platform differently. There would be _no issue_ with a prompt if the apple watch required it too. Case in point: Apple Maps has the same localisation prompt as Google Maps, and as such, there is no regulatory problems here. Entitlements are a lot more complicated, and here the DMA isn't very clear about whether or not it's acceptable or not - it's really up to the regulator.

JKCalhoun 2y ago

Yeah, you're right. Not easy, but do-able. Apple, probably due to their success and size, are trying "Make me!" as a response until, you know, someone makes them. But they're not willing to voluntarily offer these API up.

burnerthrow008 2y ago

> - They can lock the API behind entitlements that must be manually requested and reviewed by Apple > - They can lock the API behind a user approval Not if the EU has anything to say about it. Apple is already in trouble for requiring prompts for 3rd party vendors, and you know that already. Same for entitlements.

roblabla 2y ago
> Apple is already in trouble for requiring prompts for 3rd party vendors Well yeah, they're specifically in trouble for requiring prompts *only for 3rd party vendors*. The problem is that Apple treats their own platform differently. There would be _no issue_ with a prompt if the apple watch required it too. Case in point: Apple Maps has the same localisation prompt as Google Maps, and as such, there is no regulatory problems here. Entitlements are a lot more complicated, and here the DMA isn't very clear about whether or not it's acceptable or not - it's really up to the regulator.