3 ms·
We're not just talking about dialing a phone; we're talking about a Phone app. Which is—besides being a dialer—also a call history list, and a notification UI t
by derefr 10y ago
We're not just talking about dialing a phone; we're talking about a Phone app. Which is—besides being a dialer—also a call history list, and a notification UI that appears when you receive a call to let you decide whether to accept it or not. Both of those use-cases benefit far more from looking up numbers than dialing does.
As it is, if I'm sitting at my desk with my iPhone and get a call from a number I don't recognize, I literally take a second to Google the numbers on my laptop before accepting the call on my phone. I wish iOS (or any VoIP app for iOS; I use Bria) had this integration, optional or not.
- sirn 10y agoiOS do have this integration in the form of Caller Identification. An app can provide a caller information to the Phone app (I believe in a form of a database, rather than sending each call to remote server) and it will show up in the caller screen. Any VoIP app that integrate with CallKit will automatically get this functionality as well. Whoscall is one example and is pretty popular in Asia.
- derefr 10y agoHuh, neat. I guess I never really thought about how large phone storage has gotten. (A thought—if they're doing this all-locally, then they don't technically even need a separate API: phone number databases could just act as Contacts sources, with each virtual contact containing a field denoting "not actually someone I know, just someone who is calling me" so they won't show up in the Contacts app.)