Apple’s iMessage was the warning shot that things were changing. Some embraced it and didn’t look back. Some didn’t know they were embracing it – for them it was just a matter of having a blue text bubble versus a green one. Others saw it as a way to get out from under the thumb of greedy cellular carriers who charged outrageous prices for text messages. However you look at it, iMessage affected everyone who uses text messaging or instant messenging – and it is proprietary.
Microsoft’s purchase of Skype is finally changing the face of their instant messaging backbone. The popular MSN Messenger is widely used, especially among businesses, due to its ubiquity on the Windows platform but recently Microsoft announced that they were forcing all users over to Skype for voice and text chat – and it is proprietary.
Google, after having a huge success with Gtalk, has just introduced Hangouts. It is a souped up combination of Gtalk and Google+ hangouts and has the promise to be the best of both worlds with synced conversations across all of your devices (a la iMessage), best in class video and sound conversations (a la Skype) and integration with Google’s ecosystem (a la they get all of your usage data for free) – and it is proprietary.
The big three seem to be circling the wagons in an attempt to lock their faithful users in to their platform of choice. While there is solid logic behind this, it is the users who are the ones made to suffer for their choices. Over the last few weeks, I’ve been trying to build a comprehensive view of the instant messaging landscape in an attempt to pick the best tool for the job (and then attempt to push everyone I know onto it).
With such a wide reach among tools, I felt it was best to start by boiling down what features I wanted in an instant messenging application. Deciding what was important would naturally push some of the choices out of the nest, making it easier to make a decision.
Here’s what ended up being important to me:
There are a lot of choices out there. I’m only going to list the good ones. I am not going to waste time on things that are platform-dependent. I am also not going to waste time on the “text message replacement” apps like What’s App, HeyTell or Kik because making a friend pay a dollar to talk to you seems like a bad idea. I’m definitely not wasting my time on anything with the word “Facebook” in the title.
So what’s left? Not much, that’s for sure. Here’s the rundown.
Trillian/Adium - These apps are very similar and they entail creating an account on AIM, Gtalk, ICQ and the like. They function as a multiprotocol client that shows all of your contacts, and manages all of your conversations, in one place. Of the two, I find Trillian more capable because it has an iOS client which allows you to continue synced conversations between your Mac and iPhone/iPad. It is very powerful and it is one of my most-used apps. No group chat though.
iMessage/Messages - This is Apple’s entry into the scene. The Mac client builds on the old iChat model and tries (and ultimately fails) to combine the old paradigm with the new. It supports cross-device chat for iMessage conversations but if the user is on one of the other protocols or devices (like Android), you’re out of luck. I love that Apple completely routed around the text messaging monopoly held by the carriers and the way it falls back on text messaging if the device has no data connectivity is a work of genius. The Messages app has a serious bug that causes it to re-order entire conversations randomly. Continuity issues aside, the conversation sync feature is powerful and useful. If your devices are registered with iMessage/iCloud, a conversation can be continued seamlessly across all of your devices or machines. Facetime is integrated as well for voice and video chat. It is Apple-centric however and I doubt Apple will make it an open protocol anytime soon. If they fixed the message-reorder bug, this would be a major contender. It is so comprehensively powerful I’d gladly shun my Android friends (more) to consolidate on the platform. Group chat is well-implemented and I use it daily.
Google/Gtalk/Google+/Hangouts - Google, as usual, has made a mess. Gtalk was built on an open protocol (XMPP) and was easily integrated into chat clients like iChat, Trillian and Adium. As Google marches forward with Google+, it waves goodbye to consistency and convenience, replacing them with a Creepy Uncle hug to the integration between its half-baked, proprietary Hangouts effort and Google+ interface design fiascos. Google has decided to start pushing its closed protocol and combine it with its Gtalk “product”. I wouldn’t be surprised it if moved users over to their closed protocol in the coming months and shut down their XMPP service. Hangouts does support group chats and seems to aim squarely at making that a focus. Today, after extensive testing with Hangouts, I noticed that all of my Circles are now mashed up in my normal Gtalk user list on all clients. Some of these faults could be redeemed if the Hangouts app was good, but it isn’t. At times, the chat delay is pronounced, I had issues with lack of sound during some video conversations, the interface lacks some very basic options and the iPad app is a stretched-out version of the iPhone interface. It is a shame. After a few minutes, I thought the app held promise. After about an hour, I was slightly frustrated but bemused. After a few days of use, I couldn’t delete it fast enough. The tech press was trumpeting “Google wins with voice chat and synced messages” last week while Apple users have been using these features since the release of iOS6. The state of Google chat is bad, folks. Really bad. “Open always wins” though. Yup. Ok.
Skype - Out of the Big Four, Skype has the worst chat interface. It is a trainwreck. Admittedly, its voice chat is very good; it is practically a standard across all of the businesses I work with day-to-day. Most of the time, however, I just need to send someone a quick text message and this app isn’t the one I’m going to do it in.
Social Networks (Twitter and ADN) - Twitter and ADN have private (or “direct”) message capabilities. Unfortunately, both of these are at the mercy of two different potential issues. The first potential issue is the social network’s ability to handle and support direct messaging. Twitter has downplayed its direct message capability and even floated the idea of doing away with it at some point (hard to feed ads to direct messagers, I guess). It clearly isn’t a focus for them so I’d rather avoid getting caught out by building a reliance on it. ADN has a rich direct/private messaging capability but it seems dependent on the quality and consistency of the client. As ADN relies heavily on the support of third party development, they also rely heavily on the developers understanding and ability to exploit the full potential of the protocol. So far, in testing, I’ve had spotty results. While you can successfully send messages back and forth to a user, it doesn’t seem to work very well for conversations that stream back and forth quickly. Twitter’s implementation is the inferior of the two but it is also the most ubiquitous so its a case of “pick your poison”. ADN has some interesting efforts like Project Amy which integrates ADN with Apple’s iChat/Messages app. I tested it but have yet to put it through heavy paces. In a cursory test, it seemed to work surprisingly well. ADN supports group conversations you can use apps like Patter to take advantage of them. If ADN were more universal, its great third party developer support coupled with smart considerations from its attentive owners would make this a nice contender. No voice or video chat though (yet).
One thing is clear – user status is going away. In the old days (last year), the ability to mark yourself “Away” or “Extended Away” was seen as a key feature for a chat client. These days, with device-synced conversations coupled with the fact that we are now used to disjointed and discontiguous text messaging, it seems less important than ever. I am happy to see it go since it was easy to forget to change your status. I gave up trying years ago.
There is no clear winner here. As I mentioned before, the user is the real loser because the pitched battle for users and a lock-in model serve to create a wide range of favorites with each user deciding on what is their most important feature and then trying to convince all of their friends that their solution is the best. Out of all of them, Apple has the most comprehensively thought-out messaging model but it is plagued with a few serious bugs. Facetime serves the voice/video spectrum and the iMessage protocol (with its smart switching between text messaging and online-based chat) does an admirable job of syncing conversations amongst all of your Apple-based technologies.
And there is the problem – what about people who use Windows all day at work? If they can’t access chat on the desktop easily and take those conversations with them, it presents a large hurdle to building a consensus. This is the main reason why I end up using Trillian so much – it spans desktops, platforms and devices for users who aren’t me. After all, if you had the best chat client but no one to talk to, what fun would that be?
For now, my solution is going to be the Gtalk XMPP protocol via Trillian in order to span my desktop and iOS devices regardless of my chat partner’s choices. For friends who have Apple devices on both the desktop and devices, it makes sense to consolidate on iMessage, despite the occasional bugs in message continuity. The bugs will eventually be fixed but what will remain is the best platform from top to bottom. The real challenge will be convincing all of my friends to use it. For my Android-using friends, there’s always email…
As much as I think my friends who use Android make bad choices in life, it doesn’t mean I never want to talk to them. ↩
What was a once a manageble 20 users is now up to 108 people I almost never talk to. Nice job, Google. Thanks for letting me know this was going to happen. ↩
I do have to praise its consistency however as it has the worst chat client on all platforms, without exception. ↩
Have fun with that. ↩