Were it just I who came to you with only my voice on this cold night, proclaiming the imminent release of a whole numerical version of a third-party mobile Twitter client in 2021, you really would have no choice but to send for the laws, for you’d be left no consideration other than my comprehensive descent into absolute insanity. 807 days ago, I told you lots about the history surrounding the development of Tweetbot 5, which I confidently described as “likely the last competitive third-party Twitter app for iOS.” After spending the past few months diving deep into iOS in preparation to review and reflect upon Apple’s current flagship handset, my eyes have been opened to the exponentially-increasing pace of the whole environment’s metamorphosis during the course of my lapsed attention. In the name of progress, I’ve done my best to make a point of looking back, too, yet something astonishingly personally relevant managed to slip past me until just last week: there is a sixth version of the Tweetbot app. At this moment, it is listed on the App Store as an “Early Release” version, though its predecessor can still be downloaded by those who’ve already purchased it in the past, like me.
Footnote: Though I was still able to find [a share link](https://apps.apple.com/us/app/tweetbot-5-for-twitter/id1018355599), it appears to be unopenable in a regular web browser, which will simply prompt you to open iTunes. This is an unusual practice - usually, pre-release versions of iOS apps can only be distributed through Apple’s developer beta testing infrastructure, though Testflight. Notably, Tweetbot developer company Tapbots was apparently required to take down Tweetbot 5’s store listing 30 days before releasing Tweetbot 6.
Footnote: I can’t think of any innocuous reason for Apple to do so. A month’s absence of a given software company’s flagship application sounds like a nerve-wracking punishment, nothing more. Discussed at length in this blog post written by someone I don’t have the time to look up, right now: https://mjtsai.com/blog/2021/01/26/tweetbot-6-for-ios/)
I can’t remember exactly why - though I suspect I was just fucking around on my phone before bed, bleary-eyed - but the implications of this next numeral passed me by the first time I saw and downloaded Tweetbot 6, two weeks ago. Perhaps it’s because the app didn’t appear to have any new features - in fact, it’s technically got less than 5, though those that have been removed - user-specified URL shortening, image hosting, and video hosting services - haven’t worked in a good while anyway. As my old fav, The Verge noted in their coverage of 6, blame for these omissions rests solely on Twitter, Inc., itself, who’s continued to hold its API development inordinately close-to-chest. I didn’t bother to find out about this, though, because my first assumptions upon poking around the new app - especially after encountering its new subscription requirement in order to use any of its substantive features - was that its developers had ceased any actual time investment into the app long ago, and that 6 was a new version in number and rudimentary visual updates, only, shoved out in hopes of peaking old, loyal users like myself enough to get us to download it, at least. In the disappointment I’d already expected, I closed and immediately deleted the app.
I’ve paused everything else to write you on this, though, because the story is actually much bigger. Had I investigated any further that first time, I would have discovered an odd amount of buzz coming from even the most mainstream of tech media in a simple search. (Yes, I am ashamed about it.) You’re still reading, but perhaps - as I was, originally - you are doing so from an appropriately-jaded, well-read perspective on software, generally, in 2021. Perhaps you’re looking at the search results, yourself, and wondering if you’re dreaming. Dedicated coverage of a fucking third-party Twitter client iteration??? At this point in history? What in fuck? I’m fairly certainly neither of us are, though: fucking Tweetbot made headlines on Engadget, TechCrunch, 9to5Mac, MacStories, iMore, MacRumors, and others. No, it’s not 2010 again. In fact, The Verge, at least, has never given up on Tweetbot. If my long term memory had been functioning, I would have remembered noticing its spot in “12 great apps for your new iPhone in 2020:”
Twitter is a vaguely terrible way to spend your time these days, but if you (like me) can’t tear yourself away from the social media service / entryway into hell, you’ll want Tweetbot, which actually makes using Twitter far less painful. Tweetbot shows you the tweets of the people you follow, in the order that they tweeted them. There are no ads or promoted tweets, powerful mute filters to block out unwanted noise, and (thanks to Twitter’s unfriendly API changes) no notifications to constantly ping you to come back to the app.
Here’s to Chaim for exposing me to a perspective I never would have otherwise considered: Tweetbot’s lack of push notifications as a positive. If you’re wondering, no, this new app does not yet include any additional notification integration, and it’s not clear whether or not it’s on Tapbots future roadmap for the app, or where. As for the reality of integrating Tweetbot 6 into your current Twitter use, I stand by my argument that deleting the native Twitter app isn’t really an option if you plan to ever view your notifications on your phone. The popular assumption (I assume) if you’re still reading is that you are a “poweruser,” meaning details about my own configuration are probably irrelevant. If by chance you’ve just downloaded Tweetbot for the first time, you should take the time to disable notifications for Tweetbot entirely, but leave them on for the native Twitter app, even if you decide to banish it to your App Library. Before I began any work on this review, I made sure to swap in Tweetbot 6 where the native app had been in my dock for several years, now. I originally pushed the native app all the way to page 6, but immediately found this extreme. Instead, I put it in the bottom-right corner in my second screen, as you can see in the screenshot below (which also serves as proof, if you needed it.)
[image:2CD36C54-0638-4286-A552-BD9F009087E9-13270-000005C082255A03/Photo Feb 10, 2021 at 150834.jpg]
I should also note how much my own engagement on Twitter has diminished in the past 3-5 years. Not to manifest tiny violins - in turn, my engagement on (and investment in) Mastodon has increased exponentially, and it’s of a much higher quality. I bring it up for context’s sake: I can afford to prioritize Tweetbot in my Twitter use because of how few daily notifications I get - a number which is unusual for someone who uses Twitter as much as I do. Inevitably, my own use is once again going to factor heavily in this work, as is the significance of my relationship with Twitter, generally, in my life. If you didn’t already know, I’ve met basically all of my friends since high school through Twitter. As of this moment, my private “Friends” Twitter List includes 149 accounts, and I’ve spent more than 10 years, now, reading almost every single one of their Tweets. I have been as critical of the service as anyone, but - whether or not either of us are willing to acknowledge it, wholly - I believe the intimacy of this arrangement to exceed that of any in-person relationship I have ever had.
Footnote: Though I have been trying unsuccessfully to write more on this dynamic for years, I still intend to do so, one day. Reading the random thoughts of these people seconds or minutes after they’ve popped into their heads for all this time has been an experience unique to the format Twitter pioneered, if not to the service, itself. I have no choice but to acknowledge that I am deeply invested in not just Twitter, but Twitter’s less-than-visible Lists feature, emotionally and intellectually. When I hit my follow limit, several years ago, Lists also became my single means of acquiring new connections on the network. If it were to be removed, I would lose this ability, entirely, as well as any reasonable means of communicating with any of my friends.
Perhaps you understand, now, why I have written and Tweeted so extensively about Lists. You should also understand just how miraculous the possibility of Tweetbot’s new future now seems, personally, unless you’re new to all of these ideas and don’t feel like reading that big olé Tweetbot 5 review of mine (which is fine.) Before I go into the history of Tweetbot, let me first share the single most telling feature in Tweetbot of Tapbots’ belief in using Lists and share some evidence of others’ present day belief in Tweetbot. Shamefully, I’ve spent several years - tens, if not hundreds of thousands of hours - using Lists in Tweetbot, oblivious to its upmost Lists integration: “Use Lists as Timeline.” Had I actually bothered to look at the support docs at any point, I would have discovered this long ago, which would have almost certainly made my given year. If you use Tweetbot and Lists, for the love of Gourd, please take a look. Here’s what those docs currently say, in full:
One long time Tweetbot feature is the ability to use any of your lists as your main timeline. To do this, all you have to do is hold down on the “Timeline” label in the navigation bar (in the timeline tab) and a menu populated with your lists will appear. Select one and that will become your current timeline. You can switch to another list or back to your main timeline any time by performing the same action.
Even after reading this multiple times, it still was not obvious to me what it was talking about, and I was unable to find precisely zero visuals on The World Wide Web of this action taking place, so I recorded and uploaded the video embedded above. Good God, how I wish I’d been a more detail-oriented young man! I’ll be privatizing my self-punishment from here on out, though, so bear with me.
[image:0D92D630-B045-4C2D-8890-37936ED81221-20653-000006DB7C9AFB41/Photo Feb 11, 2021 at 141603.jpg]
The discourse surrounding Tapbots’ recent announcement has already reached a higher decibel count than I would have ever expected, so it’s obvious there are plenty of users who still love Tweetbot, and you already know from the beforelinked stories that The Verge has also stood firmly by it as the preferred Twitter experience. It takes a wee bit of digging, though, to discover the subtle bets on both Tweetbots and Lists from no less than Apple, Inc., itself. In the official Apple Shortcuts Gallery, a curated list entitled “Twitter Better” includes “Open Twitter Lists” at number 1. In 5th position is “Open in Tweetbot,” and “Open in Twitter App” (3rd,) is configured by default to first ask you to choose between Tweetbot and Twitter’s native app, despite its title.
[image:20E8F15C-30C2-408C-92E6-4D04C3851D7C-312-00000001450A8C7C/Photo Feb 11, 2021 at 143957.jpg]
As for App Store rankings, the fact that Tweetbot 5 was forcibly removed from public listings makes it impossible to meaningfully judge recent popularity of Tweetbot on iPhone/iPad. Its MacOS-based sibling, though (called Tweetbot 3,) was the second most popular paid app on the Mac App Store as of February 6th, 2020. That’s the day I borrowed my Mom’s MacBook Pro for a short while to check up on MacOS Big Sur, when I downloaded the current version (3.5.2, if you wanted to know) of Tapbots’ desktop Twitter client and messed around with it enough to tell you that it’s as wonderful as ever. (Had I not switched back to Windows as my primary desktop OS a decade ago, I would use it every single day.)
[image:60337ED6-0F07-4C86-95AA-1F4779A3EE74-312-0000000A8CCEFD02/Photo Feb 11, 2021 at 150738.jpg]
I suspect most active Twitter users in 2021 would be even more surprised to discover Tweetbot’s remaining, discreet hold on today’s Twitter experience than I was, assuming most of them joined more recently than myself and those I regularly interact with. For the sake of this Post, I reached out to Tapbots with an interview request about “Tweetbot’s roadmap, Apple’s requirement that [they] remove 5 from the App Store 30 days beforehand, and why [they’ve] decided to take this (risky, imo) bet on making our lives better,” though I don’t expect a reply, which is fine. They did respond to my support request regarding hardware keyboard shortcut support very quickly, saying they’ll look into it. (Without being verbose, I’ll just tell you that if a near future update to the app fixes the F and ⌘ + R shortcuts, I will shit out my whole ass.)
[image:6C3FC3E9-DC98-4938-A437-6DF949DB5C0E-1377-0000004F6CECA7A3/Photo Feb 11, 2021 at 191851.jpg]
Before I dig into the controversy and hypotheticals surrounding what Tweetbot 6 might become, let’s take a moment to qualify it vs all of one’s options to interact with Twitter on iOS currently (as in, Feb 11, 2021 at 19:24.) It’s almost certainly premature to do so, but skeptical readers would note, I’m sure, that its listing on the App Store is “early release” in name only, that I have just spent money on this specific version, which should therefore render inert the normal exceptions a review would make for beta or pre-release software.
[image:D25D8893-2D04-4C2E-9D33-948FA41EBDB5-1070-0000003A02AFE409/Photo Feb 11, 2021 at 181459.jpg]
For as long as I can remember, both the MacOS and iOS versions of Tweetbot have always possessed a more-or-less undefinable (perhaps Apple Development- specific) quality that’s noticeably set them apart from their direct competitors. I didn’t fully understand why they “feel” so much more “right” until I started making my way through this list of all the interviews/podcast appearances by Tapbots’ iOS code wizard, Paul Haddad, who comments in variations the same argument for a very deliberate developmental pace. The first time, with a MacWorld journalist on some steps outside WWDC 2013, I assumed he was just tossing some self-deprecation around to casualize the interview:
Frankly, we’re slow at doing stuff.
Yes, you are, Tapbot… From a returning user’s perspective, it’s hard to understand what in Gourd’s name they’ve been doing. I listened and read through every Tapbots interview I could find - all but one with Paul, who has through the years continued to come across as a sensitive, well-read, even wise professional developer with a healthy, professional outlook on the work of his little (relatively) weathered company and its place within the warp speed nightmare that is the mobile software industry. I suppose I was expecting to find an explanation for what I saw initially as a minimal regard for Tweetbot’s history, in contrast to 6’s announcement. I wouldn’t find it, though, because in truth, I was sure I already knew it: Twitter made it clear over a decade ago - just after they’d purchased Tweetie and slapped their own name on it - that they had no intention of competing in the client space, so third-party developers were no longer welcome.
Developers have told us that they’d like more guidance from us about the best opportunities to build on Twitter. More specifically, developers ask us if they should build client apps that mimic or reproduce the mainstream Twitter consumer client experience. The answer is no.
As we point out above, we need to move to a less fragmented world, where every user can experience Twitter in a consistent way.
I’ve spent enough time in The App Space (read: Phone Dude Hell) to expect a lot of melodrama, largely without judgement, considering how generally awful the big vendors have made the whole situation. The business legality of the story was spiked into the mainstream conversation last year by controversy encouraged by Basecamp following some pretty toxic, retaliatory correspondence from Apple regarding their plan to subsidize their new email service, HEY. Frankly, I’ve found such stories - about clashes between big software companies over mediocre, uninspiring, and sometimes just downright bad software - ridiculously exhausting and less and less interesting, lately, as I’ve realized that the most innovative, quality work I have experienced has basically all come from the tiniest teams. The most groundbreaking projects and products I’ve bothered to show and tell, here - Unichar, Zalgo Generator, Bear, Toot!, Mastonaut, Mast, etc. - were all built by individual developers except for Shiny Frog’s Bear. (Their team currently numbers 16, by my count.) Each one of those hyperlinks eventually leads to a form of my same rant: why the fuck won’t tech media talk about genuine innovation anymore. 1
[Founder’s Talk Episode Embed]
As I read and listened through Tweetbot’s history for this work, it occurred to me that I might be neglecting to acknowledge an age old divide in development philosophy across platforms. In the singular instance both Tweetbot devs appeared together in a podcast interview - a Founder’s Talk episode from 10 whole years ago2 - Paul Haddad addressed the when is it gonna be done question in a comprehensive and particularly illuminating way:
I personally hate that question because, you know… it just will get done when it gets done… We’re definitely slow. We go over every screen, every detail over and over again until we get it right. That takes time, which is why we don’t talk about upcoming projects.
Every screen, every detail, over and over again. This sort of deliberateness (which I have personally been working on appreciating, as of late) is actually - as I have come to realize - Tweetbot’s defining feature, especially going forward. Out of all the third-party Twitter clients to come and go, Tweetbot has been overwhelmingly singled out as the favorite because of how aligned it is with the traditional priorities of the Apple space: thoughtful, deeply-considered robustness. Pardon the cliché, but it is the only one that has always felt native - as if it could have been published by Apple, itself. The iOS Poweruser Community has been “allowed”3 to drift away from these principles since iOS 12, especially, and its Pandora’s box-like integration of Siri Shortcuts (Workflow, by another name.) You may or may not be aware of the jailbreaking community’s continued efforts - I was certainly surprised to discover that the r/Jailbreak subreddit has nearly 600,000 subscribers.4
Let me acknowledge the very real possibility that tech media has never really been interested in what I’m referring to as “genuine innovation.” ↩
Some might say “encouraged,” though I still have no idea what Apple expected folks like myself to do with Shortcuts and even less of an idea what it expected the average iOS user to do with them. ↩
I decided not to go in-depth to catch up on what I’ve missed in the Jailbreaking space since my own brief experience, 10 years ago, but I found this Medium post to be an interesting skim in that direction, if you’re interested. ↩