4 ms·
iOS apps have always been behind an Apple interface. I fail to see how registering a voice command is different from registering, say, a mailto: handler. There'
by matt4077 10y ago
iOS apps have always been behind an Apple interface. I fail to see how registering a voice command is different from registering, say, a mailto: handler. There'll be guidelines (hopefully) regarding preferred sentence structure, because it's a basic need of such an interface.
Users may often not see the app – that's kinda the purpose of voice commands. But the interface isn't replaced by an Apple interface, its surface is simply reduced.
You'll say 'Facebook message mom' or something like it, and it's going to message mom. You won't see the FB logo, because you won't see any logo. You may see more your mom, though.
In fact, third-party apps will profit, because they are no longer second-class citizen compared to Apple-provided apps.
There are certain tasks that are predestined for Siri – such as starting A Nike+/Runkeeper/etc. run: easy one-shot commands that replace unlocking, navigating, opening, menus etc. I'd suspect if this were a major conspiracy, Apple would have opened the API earlier.
- basch 10y ago>mailto: handler ios hasnt previously let you set a default app for protocols or filetypes.
- e28eta 10y agoMaking 'mailto' a bad choice, but iOS does allow you to register URL protocol handlers (better choice: 'x-fooapp:'). I believe it's undefined which app is chosen in the case of conflicts.
- asmala 10y agoI think you're right in that this won't have much immediate impact on the service providers. But think of this as a step towards commoditization of services. It's a small step from "Hey Siri, get me an Uber" to "Hey Siri get me a ride", whereupon an Apple bidding algorithm gets you an Uber, a Lyft, a GrabCar, etc. based on e.g. price, wait time, and reviews. As a user, I wouldn't necessarily care which platform got used as long as it meets my need.