Where did I mention Slack? I say "messages" and you assume Slack? Seriously? Also WTF does that article have to do with non-Apple smartwatches being unable to reply to message notifications on iOS?
You can not reply to SMS or iMessage notifications on non-Apple smartwatches. It's not allowed.
What are you talking about then? Using a third party app that can reply to your iMessages or SMS? Why in the heck would I trust a third party for my SMS messages?
But as far as third party watches replying to SMS/iMessages, they could do it just like you respond to messages from cars before CarPlay was a thing - you support the appropriate Bluetooth profile.
Microsoft did it on computers without official Apple support
I'm talking about replying to SMS/iMessages from a non-Apple smartwatch. For example, with my Garmin watch on Android I can do things like send a canned message like "Yes" or "On my way" or whatever from the watch itself in reply to a notification. This is not possible on iOS with a non-Apple watch.
Why wouldn't you trust it? Yes, in theory a smartwatch could abuse my trust and send my friends spam or something but so could some no name Bluetooth keyboard yet I can use those just fine on iOS. Why should APPLE get to decide what devices I trust?
Microsoft did a hacky workaround with a whole host of limitations that proves my point. Apple is keeping the proper way to do it to themselves to make their products seem better.
There is a standardized Bluetooth protocol called the “Messaging Access Protocol”. Any Bluetooth device that you connect to the phone can work with that protocol and send and receive messages. It worked with my old 2011 Ford Fusion.
The iPhone has supported that for at least a decade.
Ok? Maybe it's unsuitable for a smartwatch (e.g power draw)?
This is a limitation common across non-Apple smartwatches on iOS. If it was SO simple you'd think they'd all do it and wouldn't have taken Microsoft 5+ years since the rollout of Phone Link.
I get that you love Apple but my man they are not the good guy you seem to believe. Have fun living in the reality distortion field, I hope you wake up one day.
So you went from “it doesn’t exist”, “Apple doesn’t support it”, “it’s a hack” to “maybe it’s too much of a power draw?
> Have fun living in the reality distortion field, I hope you wake up one day.
Yes a standardized Bluetooth profile that has been available on iOS devices for over a decade is “not reality”.
And now your excuse is that “maybe Bluetooth takes too much battery life”?
> This is a limitation common across non-Apple smartwatches on iOS
Have you ever thought that Android devices makers who are competing on price decide it’s not worth making the investment in supporting iOS devices since the Apple Watch is so dominant?
I told you exactly how it could be done using an existing Bluetooth standard that Apple has supported for over a decade. You’re really pulling at straws.
You could also at one point send “canned messages” from third party watches before the Apple Watch was introduced.
And I’m sure that’s all crappy Android watch makers with horrible processors and battery life would have to do to convince Apple Watch owners to switch is to enable message replies.
Use quick replies to send customized responses to text messages and messages from certain apps with Fitbit Charge 3, Fitbit Charge 4, Fitbit Charge 5, Fitbit Inspire 3, Fitbit Ionic, Fitbit Luxe, Fitbit Sense series, or Fitbit Versa series. This feature is currently available on devices paired to an Android phone . Devices paired to an iPhone can respond to Fitbit app notifications, such as messages, cheers, taunts, and friend requests.
You can not reply to SMS or iMessage notifications on non-Apple smartwatches. It's not allowed.