Tweetbot 1.2.1, 1.3 and the State of Push Notifications
There’s been a lot of questions about what’s to come so here’s a bit of an update on what is happening around here.
A little over a week ago, you should have gotten the 1.2.1 update. If you haven’t yet, you’d better get it soon. Twitter is changing the way users need to log into their service to make direct messages more secure. This required us (as well as all the other 3rd party clients) to change the login process. Basically we need to send you over to Twitter’s website to login and authenticate our app to access your account. That’s what 1.2.1 is all about. It should be a fairly painless processes, but we are aware that a few of you are having issues logging in. If you are having issues, here are some steps to take:
- Make sure your iOS system time is correct. Twitter won’t allow you to login if your time is incorrect.
- Remove all of your accounts and add them back again.
If you are still having issues, you can email us through our support page.
We are submitting Tweetbot 1.3 sometime this week. We don’t know when it will be available, but we will announce on Twitter once it does get approved. Here’s what’s new:
- Improved multiple account switching
- Local trends (can be set in the account settings)
- Improved recipient selector when creating a new direct message
- Ability to copy, delete, and translate direct messages (swipe on a thread to delete a whole group)
- “Add to List” feature improved and renamed to “Manage List Memberships”
- Added “go to user” feature in people search (shows when typing into the “Search People” box)
- Gaps now load above or below depending on position of gap when button is invoked.
- Compose Tweet from hashtag (by holding down on a hashtag in a tweet)
- Drafts button now displays # of drafts.
- Support for Favstar (hold fav button to invoke ‘tweet of the day’, double-tap profile tab to see your own favstar page)
- Various bug fixes
We know this is a big request and we are still working on getting a solution going. We’ve already explained how complicated and costly it can be to get it running as well as the ability to scale. But one thing we haven’t mentioned is the fact that Twitter needs to approve us for their streaming service. But getting approved is not nearly enough. Their streaming service is currently still in beta and they limit the amount of accounts we can stream so they can properly scale. So the bottom line is there are many components that have to come together for this to happen and we are working on it. It’s not a matter of turning on a switch and having it working for everyone. Complaints and bad reviews because of lack of push won’t make it happen any faster. :)
Tweetbot for iPad and Mac
Even though we answer this all the time, I figured I’d mention it again. At this time, we have no plans for an iPad or Mac version of the app. That’s not to say it won’t ever happen. Twitter is just a shaky platform for 3rd party developers right now and we don’t want to dedicate a lot of time into something that might become a bad business decision. We are going to wait a bit and see how things go.
Still not going to happen. It’s just not what Twitter is about and we don’t really want it in our app. But the beauty of the app store is if you really want it, there are 50+ Twitter clients that already have that feature. Take your pick! And no, we aren’t trying to be mean here. We are trying to build the best client experience we can for the majority of our users. We can’t and won’t even try to please everyone.