> Let me communicate with a unified UI and unified contacts.

This was from the top comment. It is suggesting the solution is to glom everything together. I think the comment you are responding to is concurring with their parent comment by providing an illustration of the concerns raised.

I think a better example is how WebOS and Windows Phone handle communication. They treat communication like it's between two people, rather than between two applications. Text messages and Facebook messages are combined into one, so you can continue the conversation from anywhere. Facebook and Twitter posts are added together to show what the person is doing, rather than what accounts on disparate are doing. These aren't huge monolithic apps, they're more like feeds from services all tied to a single person. Both WebOS and Windows Phone allow you to combine multiple accounts for contacts together into one person.

Basically, it shouldn't matter what service someone is using. What really matters to people is people. If someone is at their computer, they might want to use Facebook messenger. If they're away, they'll want to use text. Barring that, they might rather use email. The point is, someone shouldn't have to open the Facebook app, find they're not online, send a text only to wait for a response and assume they do or do not have their phone on them, then send an email. If they can do it with one app, the app telling them the best way to contact someone, it makes communication much easier.

No one has gotten it right yet, but I feel WebOS and Windows Phone are closer than the traditional discrete applications.

No, there just needs to be interoperation layers like file systems, sockets, stdio, etc. In the kitchen metaphor, it's your hands.