On top of that the native client doesn’t load all tweets if it has been a little while.ĭevice synchronization, more than anything else, is why I can’t leave Tweetbot. It jumps to the top or back to where I left off on the device, not where I left off on the other device. I simply cannot do this on the native client. It isn’t uncommon for me to, for example, close my computer and pick up my iPad to continue catching up on my timeline or a list. The native Twitter client displays individual tweets and threads better than Tweetbot but it is a complete failure at keeping my devices in sync. Finally, Tweetbot often misses images and other previews forcing me to open the tweet in a browser. Tweets aren’t grouped logically making threads hard to follow and many replies don’t show up at all on Tweetbot’s main timeline, even for people I’m following. I have set it that way on each and yet Tweetbot still misses too much. The Timelineīoth apps have the ability to display a chronological timeline (with the native client you have to select it as it isn’t done by default).
While each app has some advantages, as of today I am back on Tweetbot for the foreseeable future and here is why. Now that I’m back in the Apple ecosystem I’ve been going back and forth between the native client and Tweetbot on each of my devices (laptop, phone and iPad).
#Twitterrific push notifications android#
On Android I had tried the native client and a handful of other clients until I wound up on Fenix which was, at best, OK.
While I love the people on Twitter, the software available to access it has been something of a comedy of errors. I’ve tried to make a break for Mastodon, and do enjoy the network, but it has been an absolute failure at replacing Twitter, particularly over the last two years as we have primarily been at home. It’s my water cooler and my connection to the WordPress world.
0 kommentar(er)
