My plea to Tapbots to fix the Tweetbot 3 app for iOS / by Jamie Young

I submitted the following via Tapbots' support form on June 13, over two weeks ago. I haven't heard back or seen any of the issues addressed. Anyone that knows me, knows how much I love Tweetbot, but also knows how important apps that work properly are to me (especially if it's affecting how I use Twitter). 

Hey Tapbots, 

I'm a huge fan of your apps, particularly Tweetbot; but ever since Tweetbot 3 was released, I've been pretty bummed: It now takes way more taps to accomplish simple tasks, I have almost 200 drafts (yes, I realize I'm psycho) in Tweetbot 2 I can't part with, and much more. So I decided it wasn't worth it just for the "iOS 7 redesign."

But just this week, I decided to try Tweetbot 3 for a third time. Give it another chance (I really want to like it; I really want it to work).

But nope. No can do. This time I unfortunately ran into new issues and issues I hadn't even noticed before. 

Because I love Tweetbot and I want to be able to finally use Tweetbot 3 (that I paid for) instead of its predecessor, Tweetbot 2, I thought I'd email you guys the bugs and issues with Tweetbot 3. You know, formally.  

- Drafts. Can I export these from Tweetbot 2 somehow into Tweetbot 3? Why are these not synced somewhere? They should also sync across all platforms (iPhone, iPad, Mac). There has got to be some solution here. 
- Replying to a tweet starts with a lowercase. This should not be the case. I am writing a sentence. The beginning of a sentence begins with a capital letter. Grammar nazi Jamie can't handle this; it makes me twitch. If some people prefer to begin their sentences with a lowercase letter, fine. But then make this an option (or toggle) in settings. Don't force improper grammar on us. Think of the children!
- I receive notifications twice anytime they happen. On top of that, I also get notifications three, sometimes four, times later. For example, recently I got a follow notification from 2 hours prior that I had already received from Tweetbot 3 twice when it happened. So, that's three notifications for the same god damn thing. You guys were nice enough to tweet at me twice with "fixes" for this, but neither of them worked whatsoever (resetting notification cache, turning notifications off for 10 minutes, then back on — not even sure how that would be a fix, to be honest). Clearly this is a big issue. And I know other users who have been experiencing the same for months.
- I used to be able to tap on the banner notifications for Tweetbot notifications and be taken to them within the app. But in Tweetbot 3, I am no longer able to interact with them whether I am in Tweetbot already or not. Ex. I'm reading someone's timeline in Tweetbot 3. Someone replies to one of my tweets from earlier. A banner pops up notifying me of this (twice, I might add - ahem). I tap the banner. It doesn't take me to my replies like it would in Tweetbot 2. Why was this feature removed? It was very helpful.

I'm sure there are more things that I'm forgetting, but these are the make its and break its for me.

So, Tapbots, please. I'm begging you, here. Fix up the app. Because, right now, Tweetbot 2 is far superior and works 100 times better. And I want to be able to use the app I paid for. 

I want to finally be able to use Tweetbot 3. 

Thanks for all you do. And kudos for reading this far. 

Maybe I should just get a refund.

I know there are others who are still using Tweetbot 2, as well, due to these issues and problems. Or maybe you've moved on to another Twitter app altogether. Either way, speak up! I want to hear from you, even if Tapbots doesn't.