Comment 5 for bug 1535755

With an API approach it should be possible to build a telephony app that handles contacts in a uniform manner. By this it could be possible to maintain the telephone contacts and social contacts as separate data sources, yet still allowing a unified user experience in a single app (e.g. search for a contact -> get the results presented in a collected/combined fashion).

See the concept in bug 1627747 ("generic API for communication and data exchange").