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.

PSA: What every iOS app developer (and PR person) should know but doesn't by Jamie Young

I was just going to tweet this, but then I realized that it'd be a little over 140 characters. 

I've noticed a lot of my developer friends lately don't even know this. So, if you're an iOS developer, plan to be, or are marketing for an app that's coming out soon, you'll want to read this.

Being in the app press biz for over three years now, I know my ins and outs of covering apps as news and reviews. This includes dealing with promo codes...a lot. Sure, we do beta tests through Hockeyapp and Testflight, but in the end we always need a promo code of the official version of the app. 

Luckily, Apple does this awesome thing—though they don't seem to let you know about it for whatever reason: They allow you to set a release date for your app when you submit it for review. Instead of choosing for it to go live on the App Store upon Apple's approval, you can pick a release date far into the future. Whatever date you want; and you can always change it later. Then, once your app is approved by Apple, you have early access to promo codes. 

This is awesome for you on three levels. 

1) It allows you to have full control over when exactly your app will be released. Which is amazing because if you've ever submitted an app with Apple you know waiting for it to be approved so you know when it will go live is an excruciating process.

2) This helps you get maximum press exposure, as you can share these promo codes with the media early and get your app previewed (if you allow that, if not be sure you give the press a specific embargo date and time) and/or reviewed the exact day it's released—and we (the media) LOVE early access. I definitely appreciate the heads up, too.

3) This also seems to give Apple extra time to check your app out and decide if they want to feature it. And surely you don't want pass up that opportunity. 

Keep in mind, these promo codes allow full access to your app. The person given the promo code will download it from the App Store just as if it were live already—but it's not. Only the person with the promo can use the app and check it out. 

Neat, huh? 

One last thing: Yes, you can even get early promo codes for apps that will be free. This allows us to check out your app before it's released, just like any other paid app. 

Just wanted to share this little tip with the iOS community as I've noticed few, if any, developers I speak to know this is the case. And folks that do PR for apps are left in the dark too. 

Stay tuned for more free marketing advice! (Someone should pay me for this shit.)

UPDATE: Another great promo code tip. Thanks, @Chounard!

I popped the Finer Things Podcast's guest cherry by Jamie Young

I had the pleasure of being a guest on the Finer Things Podcast with David Chartier and John Morrison this week. I was their first guest, too! You can find it here.

We talked about what we like about iOS 7 and how it will affect the every day user.

Be sure to give these guys a listen! And don't forget to subscribe to and rate the Finer Things Podcast on iTunes.

iOS 7, briefly by Jamie Young

I'm just going to put this out there: This is probably the most excited I've been about an OS in a long time.

And I was actually surprised by this. I wasn't too excited in the months leading up to the keynote on Monday. But I also wasn't expecting this

Don't get me wrong, there are things I very much dislike about iOS 7 so far.  But I can save all of the mushy details for this fall. 

What keeps crossing my mind is, "This feels like a brand new thing. Like a brand new phone, with a brand new screen.'s not." I have to keep reminding myself it's not. That right there is good.

It's an exciting, shiny, new thing. Sure, it's different. Very different. Kind of...alive.

But hasn't everyone been complaining about Apple not creating anything new? "The same old shit." Well, here's new shit. 

This isn't the second coming of the iPad. But so far, I'm seeing a big step in the right direction. It will just take a lot of refining and pixel-perfecting before the leaves start falling off the trees.

"Design is not just what it looks like and feels like. Design is how it works." 

—Steve Jobs

Apple doesn't just do design for the sake of design. There's always a purpose. 

Have patience. 

P.S. If I hear one more dude who hasn't even used iOS 7 call it awful because it's "girly," I will throat punch him. In the girliest way possible, of course. And trust me: That will be awful.