Tag Archives: tweetbot

Jack Dorsey to lead Twitter again

Three years ago today I posted my last personal tweet. That time and distance away from mainstream social networking has given me a new perspective on the importance of independent microblogging. It has shaped where I write and what tools I build.

But Twitter remains as fascinating as ever. Just a few weeks ago, the board seemed unsure about letting Jack Dorsey split his time between Twitter and Square:

“The responsibilities of running Square, which Dorsey reportedly refuses to give up, may now stand in the way of a Steve Jobs-esque return as Twitter’s full time chief executive. In June, its board took the unusual step of publicly declaring that it would only consider candidates ‘who are in a position to make a full-time commitment to Twitter’, a thinly-veiled reference to Dorsey’s preoccupations.”

Then they backed away from that:

“That declaration, as it seems to have turned out, has been a largely empty one. The idea that Dorsey might return gained steam among people both inside and outside the company over the past few months even though he had no intention of leaving Square. He even referred to the companies as his two children when discussing the dilemma, according to a source.”

Today they officially announced that Jack will return to lead Twitter. Of all the recent articles, my favorite is this one from Recode, a long profile on Jack’s role and changing attitude:

“He seems to be a completely different man than the one who returned to Twitter in March 2011 as executive chairman and product czar. Former colleagues recall a man looking for payback for his 2008 ouster; loyalty was key, and many who were loyal to Twitter’s other co-founder, Ev Williams, were booted from the company. Back then, Dorsey would routinely sit in on meetings without saying a word. When he did speak, his contributions were so abstract that few understood what he was talking about. In some cases, he’d simply write a single word or two up on the whiteboard.”

And it goes on, showing how Jack has matured as a leader. Everyone will be watching what he does, and how Twitter evolves. Every article written about an upcoming Twitter feature will mention Jack’s involvement, no matter how insignificant. He’s a big part of the story now.

Ev also wrote about the official announcement:

“Twitter is bigger and more important to the world than we ever dreamed when we started. And it still has incredible, unrealized potential. It will not be easy to unlock it. But we have thousands of smart, creative people working every day to make the company great. And Jack has already demonstrated the ability to inspire the team and think boldly about the next phase of Twitter.”

The greatest challenge for Jack will be figuring out how to take whatever those thousands of employees are working on and turn it into actual user-facing features that ship to customers. Federico Viticci, reviewing the new Tweetbot 4 release last week, wrote about how Tapbots has built something more ambitious than the official Twitter for iPad app, even though Twitter has a much bigger team:

“On the other hand, Twitter for iPad – long ignored by the company – has emerged again with a stretched-up iPhone layout presented in the name of ‘consistency’. It’s a grim landscape, devoid of the excitement and curiosity that surrounded Twitter clients five years ago.”

I still run Tweet Marker, which was created during that period of innovation that Federico refers to, but my focus now is on indie microblogging and the open web. I’m content to watch Twitter from the sidelines and wish Jack the best of luck.

Layered glass

Nate Barham describes iOS 7 as layered glass:

“The best developers will see iOS as an operational model, not a visual one. Imagine a Tapbots app that, instead of removing the cute ‘I’m a twitter robot in your phone!’ aesthetic, doubles down on it. Zooming metal plates, ratcheting gears not shadowed from without but appearing from within the device, only now it isn’t a robot-esque layer over the stock controls, the UI becomes the character that the developer envisions—even more so than it has ever done before.”

I really like this post, but I’m not totally sold on the paragraph quoted above. Done right, it could be brilliant. But this is a very difficult thing to pull off, keeping the playful spirit of Tweetbot with a lighter, minimalist iOS 7 UI.

And related, if you missed Christa Mrgan’s recent Macworld essay, she also covers how iOS 7 will use depth and motion to switch from “faux 3D to real 2.5D”, with an example from Adobe’s After Effects. Makes me wonder if designers will need new prototyping tools.

Tweetbot + Twitterrific

The second app to support “Tweet Marker”:http://tweetmarker.net/ has arrived, and it’s a great one: “Tweetbot”:http://tapbots.com/software/tweetbot/. I love using Tweetbot on the iPhone and Twitterrific on the Mac and iPad. Seeing these apps work together just makes for a better Twitter experience.

Here are a few tips to keep in mind while using apps that support Tweet Marker:

Turn it on! First things first: enable Tweet Marker in both apps on every device you plan to use Twitter on. MacStories has a good summary of this (with screenshots) for “their coverage of Twitterrific”:http://www.macstories.net/mac/twitterrific-4-3-syncs-timeline-position-with-tweet-marker/ and “again for Tweetbot”:http://www.macstories.net/news/tweetbot-1-6-gets-tweet-marker-timeline-sync/.

What syncs? Only the main timeline and mentions sync between the apps. While working with these developers, we made a decision to change how Twitter lists sync after Twitterrific had already shipped. So while both apps think they are syncing lists, the format on the server is not compatible between the two. A future version should fix this.

How to switch apps? Most apps take the approach of saving the last-read position when the app is quit or sent to the background, and restoring it again when it is launched or brought to the front. You may need to change your default habits a little to get the most accurate behavior. When you know you are going to switch apps, just close your active Twitter client first before opening the next one. It may also help to wait for the app to download new tweets before scrolling or interacting with it.


After about a day of using Tweetbot, “I said”:https://twitter.com/manton/status/58723721728360448:

“Tweetbot gets nearly everything in the UI right. Love it. But.. it’s a basic client. I still think the future for third parties is features.”

I only got a few responses, most defending Tweetbot as something special. I agree, and there’s a lot to be inspired by from it. In an odd way, though, just being the best Twitter client isn’t enough.

“Marco Arment writes more”:http://www.marco.org/2011/04/18/ben-brooks-on-tweetbot (following a “post from Ben Brooks”:http://brooksreview.net/2011/04/appsuration/) about why Tweetbot isn’t for him despite being such a good client:

“A new Twitter client that essentially offers the Twitter app’s features, but in different places, isn’t enough of a difference for me to switch. If anything, it supports Twitter’s ‘don’t make full-featured apps’ position. Maybe they were right.”

The problem isn’t that third parties shouldn’t make full-featured clients; it’s that they shouldn’t make clients that have exactly the same features as every other client. If Twitter discourages all apps from being made just because many will fail, we’ll miss out on all the things Twitter will never add to their apps and platform.

I see three compelling reasons to use Tweetbot 1.0: the design, swipe for conversations, and related tweets. The last is actually in the Twitter API — I’ve been meaning to add it to Tweet Library — but it’s not yet documented outside of an email message to the dev mailing list. Congrats to Tapbots for being the first I’ve seen to add it as a high-profile feature.

Last September I wrote about “next-generation Twitter apps”:http://www.manton.org/2010/09/next_generation.html:

“I believe we’re about to see a third generation of clients that will go way beyond what the web site can do. There was worry when Twitter bought Tweetie that it would destroy the third-party Twitter market, and sure, some developers will fail or be discouraged from trying to compete against a free official product. But really what it does is raise the bar — that to succeed Twitter clients should be more than just a one-to-one mapping between UI and the Twitter API.”

I hadn’t announced Tweet Library yet when I wrote that. Now that I’ve shipped it, I believe even more strongly that we haven’t seen anything yet from Twitter apps. Tweetbot is a great 1.0 and my go-to app on the phone because it’s better in lots of small ways than anything else. But that it’s not for everyone is actually great news. I hope there are plenty of unique features still to come from a variety of other apps.

Consider this: Tweetie already “won” the market. No matter what we do as Twitter API developers, none of us can ever have the most popular Twitter app. This frees every app to focus on its core strength. For Twitterrific, that’s a unified timeline; for Echofon, that’s last-read sync; for Hibari, that’s keywords; for Kiwi, that’s themes; for my own Tweet Library, that’s curation.

What’s Tweetbot’s core strength? For now, overall user experience, not standout features. But I’ve been a Tapbots customer long enough that I’m excited to see where they take it.

For more Tweetbot discussion, check out “this collection of tweets I made”:http://tweetlibrary.com/manton/tweetbot1.0 about the launch.

Birdfeed, etc.

He snuck it in under a commentary on Alex Payne’s excellent “last post about Twitter”:http://al3x.net/2010/09/15/last-thing-about-twitter.html, but we now have a “Birdfeed postmortem of sorts from Buzz Andersen”:http://log.scifihifi.com/post/1144913920/in-a-way-the-twitter-platform-has-come-full. I’m particularly interested in where Buzz thinks the Twitter app market is going:

“Does this mean that there’s no longer room for third party Twitter clients? My suspicion is that people will continue to make them, but it seems to me that they’re already on the road to becoming increasingly uniform and commoditized as the Twitter experience is more sharply defined by Twitter itself (as my Birdfeed collaborator Neven Mrgan has suggested to me, Twitter clients are going the way of email clients).”

It seems nearly everyone thinks competing with Twitter’s official app is a bad idea. “Here’s Tapbots revealing Tweetbot”:http://tapbots.com/blog/business/say-hello-to-tweetbot shortly after the Tweetie acquisition:

“But this news changes things for us. We probably won’t be able to charge for the app anymore. Who’s going to pay for a Twitter client when ‘Tweetie’ is free?”

I think the problem isn’t trying to build any Twitter app. The problem is building a mainstream Twitter client. The official iPhone and iPad apps, plus the redesigned web site, are so good that it’s futile to go head to head with them. You can’t undercut on price, and they are so well coded you’d need a talented full-time team to out-engineer them.

As I said in “my last Twitter post”:http://www.manton.org/2010/09/next_generation.html, the trick is to look past the API. What would I want Twitter to add to the platform if I had my way? Design an app around that and you might have something interesting.

The theme in Buzz’s post that resonated the strongest with me is the emotional drain that building an app like this can have. The competition is intense. There’s a feeling that if you don’t have every little feature when you ship, you’ll be laughed out of the App Store. That is certainly on my mind, especially as “I intend to push the price”:http://www.manton.org/2010/06/10_ipad_apps.html in this market, and even with beta feedback I’m still not sure how my app is going to be received in the real world.