Default dialer abilities & limitations

Question

Created 1w

Replies 1

Boosts 0

Participants 2

I've been trying to understand what kind of UX is available if my app is using the default-dialer capability. I have found https://developer.apple.com/documentation/livecommunicationkit/preparing-your-app-to-be-the-default-dialer-app and I am in the EU.

On android I built the UX I want and it's quite neat, so now I'm trying to work. out what I can get on iOS. Because the product is kind of worthless with just android.

I have built a simple dialer ux with a numberpad, contact lookup etc. Then when the user presses the Call button does it have to pop up the system prompt "Call number"? Does it have to swap over to the system ui for the actual call? So there's no way to show information about the call, during the call? Or am I using the frameworks incorrectly? I am very new to iOS development.

TrueCaller and others show validation, but as I understand it they pre-fetch all the data, I can't do that.

Boost

Answer 1

DTS Engineer OP

Apple

1w

I have built a simple dialer UX with a numberpad, contact lookup, etc. Then when the user presses the Call button, does it have to pop up the system prompt "Call number"?

No. A default dialer app can use the "StartCellularConversationAction" to initiate a call.

Does it have to swap over to the system ui for the actual call?

To be honest, I don't remember whether or not "StartCellularConversationAction" immediately presents the call UI (like Phone.app does) or just leaves the app in the foreground (like CallKit and LiveCommunicationKit do). However, that should be straightforward to test.

However...

So there's no way to show information about the call during the call? Or am I using the frameworks incorrectly?

I believe the system will still handle the "out of app" interface.

__
Kevin Elliott
DTS Engineer, CoreOS/Hardware

0