> Starting with iOS 8.0, the NP can inform the NC of potential
> actions that are associated with iOS notifications. On the
> user’s behalf, the NC can then request the NP to perform an
> action associated with a specific iOS notification.
These API have exited for over a decade and plenty of other wearables use them. Yes there are some limits, but many fewer than the original article implies to create outrage
OP said “ cannot do A or B”. I demonstrated how to do B, proving the original statement to be a lie. The fact that you still cannot do A irrelevant. Hyperbole has no place in technical discourse.
>The NC must neither assume nor try to guess in advance the exact action performed on an iOS Notification, because these actions are based upon information unavailable to it, as well as other factors such as the ANCS version implemented by the NP. The NP guarantees that positive and negative actions are associated with results that do not surprise the user.
So pebble app can’t explicitly say dismiss or mute but has to hope that the phone does that action on a given notification.
Imagine the app says dismiss but the phone‘s real action is just a snooze.
Press X to maybe dismiss doesn’t sound like a great functionality, does it.
> It’s impossible for a 3rd party smartwatch to [...] or perform actions on notifications (like dismissing, muting
REALLY? Why not RTFM?
https://developer.apple.com/library/archive/documentation/Co...
>Notification Actions
> Starting with iOS 8.0, the NP can inform the NC of potential
> actions that are associated with iOS notifications. On the
> user’s behalf, the NC can then request the NP to perform an
> action associated with a specific iOS notification.
These API have exited for over a decade and plenty of other wearables use them. Yes there are some limits, but many fewer than the original article implies to create outrage