![]() ![]() This is pretty great to me as I’m not interrupted for things I really don’t care about. If I clear them on, say, my iPad, my phone will still show them hours later which can get highly confusing.Īs a positive Tweetbot doesn’t even try to notify you of what I call the “vanity notifications” including likes, retweets and all the other noise that doesn’t matter. Tweetbot also does a horrible job of syncing these notifications. If I’m on my main timeline I might’ve even seen the content there minutes before I’m notified of it and it appears in my Mentions tab. ![]() Tweetbot only notifies me of new messages (replies, DMs, etc) and does so with a lag of a few minutes or more. The native client can notify me of everything, instantly, on any device and does a great job at keeping those notifications in sync (if I clear them on one device it clears them everywhere). 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). 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. Personally we view this as a bonus.I use Twitter, a lot. You don’t get ‘In case you missed it’, you don’t get sponsored posts, you just get tweets from people you follow in chronological order. The first thing to be said about these apps – whether you view it as a feature or a peculiarity to third-party Twitter clients – is that they prune out quite a lot of Twitter’s timeline enhancements/junk (delete according to personal preferences). We’re not sure if this is a limitation on how far back Twitter lets other companies search its archives (the most recent result was a little over a fortnight old), or if they are imposing quote marks themselves (Tweetbot’s interface implies that it is). We ran a search for “Tweetbot vs Twitterrific” (without the quotes), and neither came back with any results, whereas Tweetdeck searching exactly the same term returned lots. One other thing: search is a bit funny on these apps. ![]() Someone planning to pay £7.99/$7.99 or more for a third-party app is probably a Twitter power user who is more than capable of exploring an app’s features for themselves. All of this may not bother you, of course. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |