I don’t expect most iPhone users to ever change their default settings, but it’s nice that it will be possible in a year.
Who knows, maybe one day you can run actual Firefox on them too? :p
I don’t expect most iPhone users to ever change their default settings, but it’s nice that it will be possible in a year.
Who knows, maybe one day you can run actual Firefox on them too? :p
Whoa, this is interesting tbh. I don’t think calls/messages is something they really expose at the moment for developers, do they?
Personally I don’t really care, the default apps are good and I don’t even know what you would want to replace the dialer for, but it’s nice that you can.
Imagine iOS getting the capability to have third party RCS messengers before (non rooted) Android though. Lmao
As a developer, you don’t really get access to any of that.
Mainly, you can’t access any history of calls and messages at all, nor can you automate sending one. All interactions with calling or texting has to be done with user interaction. Namely, calling requires the user to confirm the call, and sending a message requires the user to confirm, and they can also edit the message beforehand.
I don’t think that’s bad, given that messages are some of the most private things on our devices, and personally, I never had to use any of these or required more access. But more choice is always appreciated.
Was always curious why there was an extra step to confirm when making a call through the GV app. Not using it anymore, but I see the logic behind requiring that confirmation.
Sure, it has to be done with user interaction, but that doesn’t mean it has to be through the stock apps, which is what the article says you will be able to replace here.
What I’m saying is, for this to actually work, they do have to expose these APIs to allow developers to write a custom dialer and messages app. I think the only thing remotely related there is right now is CallKit which is kind of the other way around (integrates non-phone calls into the stock dialer).