Jaiku vs Twitter – the revenge (UPDATED)
So Google’s purchase of Jaiku has happened and I am delighted.
It is a bit of the VHS versus Betamax battle – but where the better format wins!
Jaiku is a much more accomplished, micro-blogging tool. It offers post comments/threads, groups, post/comment rss feed, external feed importing, embedable post icons, groups and fantastic mobile functionality (there’s probably a load more too!).
The one thing it has always lacked is a vast user-base, which Twitter has in abundance. Yet Twitter has almost NO functionality other than erm…search and rss.
As a predominantly mobile application, with a larger customer base, one can’t help wonder why Google hasn’t bought Twitter instead (to go with the Gphone no doubt!)
I sincerely hope that Google’s purchase of Jaiku really opens the application up to the users it deserves – it is significantly better than Twitter and the more users it gets, the better.
Update: The irony of Robert launching a conversation about Jaiku on Twitter was not lost on me, nor was the use of Friendfeed to carry out the conversation ;-). Robert used FF to discuss why Jaiku has not taken off as a Micro-blogging tool, when the always-down and featureless Twitter remains so popular.
The discussion ranges from “horrible green colour” to “closed network” (but surely on this basis, any network that requires a login is closed?” but I see so many compelling reasons FOR Jaiku, namely and not exclusive to:
Fantastic mobile client
Feeds (image and text)
Great UI (for threaded conversations)
As I suggested earlier this week, FF’s room feature may in fact spell the end for Jaiku (although many would argue that Google was the end for them!) but the direction of the conversation is absolutely turning towards FF as the bridge between the gap.
Twitter = Frequently down, featureless, massive user base
Jaiku = Occasionally slow, feature-rich, few users
Friendfeed = Always-up, good speed, growing (quickly) community, feature-rich