Now this isn’t a particularly big deal for us since we already had code in place, for Tweetbot 2.3, that removes the need for UDID. It was a simple matter of moving that code back into 2.2 and re-submitting to Apple. We had a fixed version updated and uploaded to Apple within 2 hours of getting this message and are once again waiting for approval. If you are an app developer and depend on UDID for any functionality it’s time to migrate away from it, sooner or later Apple will catch you.

Why did we use UDIDs? We used them only for our push notification services in order to be able to match up a given device to its push notification settings. This allowed us to restore push notifications settings after Tweetbot was deleted and re-installed. With this new change in place this is no longer possible, if you delete and re-install Tweetbot you’ll have to setup your push notification settings again. Your device’s UDID never went anywhere besides our push notification services and has never been shared with anyone.

• iPad graphics optimized for the new iPad’s retina display
• Streaming (when on WiFi with settings to disable it)
• The “new tweets” sound is now limited to mentions, DM’s, and new tweets via pull-to-refresh
• Double-tapping on the timeline tab button takes you to last read tweet before going to the top
• Improvements to the Tweetmarker service
• Camera+ 3.0 Capturing/Editing Support
• Bug fixes related to direct messages
• Many other bug fixes

Tweetbot for iPad is now version 2.1

Since we plan to release updates to both the iPhone and iPad apps in parity, we decided to bump the iPad version up to 2.1. Both apps share a lot of underlying code so it only makes sense that their version numbers are in sync.

Streaming

We are excited to announce streaming in Tweetbot for the iPhone and iPad. What is streaming you ask? Instead of pull-to-refresh to check for new tweets or waiting for the 5 minute auto-refresh to take place, tweets appear instantly in your timeline as they are published.

There are a few limitations to streaming which Twitter has put in place:

• Streaming only works over WiFi. Tweetbot will automatically turn streaming on and off depending on your network status.
• Streaming is limited to running on three versions of Tweetbot at a given time per user account.

iPad version ready for Retina

Tweetbot 2.1 for the iPad is now retina-ready for the upcoming new iPad. Just like you, we can’t wait to see how Tweetbot will look on the new retina display.

New Camera+ 3.0 Support

With the release of Taptaptap’s Camera+ 3.0, you can now use Cam+ to edit or take photos for Tweetbot. If you have Cam+ 3.0 installed on your device, there will be new options when you are in the menu to add an image to a tweet.

Fixed:
* DMs not working for iOS 4.x devices.
* Lists losing their positions.
* TweetMarker not working properly.
* Arabic, Thai, possibly other keyboards not functioning correctly.
* Video upload settings lost on restart.

We have no control over how fast Apple approves the update, but we’re hoping that it’ll be sometime late next week.

As with the original Tweetbot for iPhone, version 1.0 is about getting you a solid first version. We still have a lot of work ahead of us so we appreciate your support! We have a lot of great stuff coming in the pipeline.

We are anticipating some of you wondering why the app is not universal so let me briefly explain. As you know, releasing quality software takes a lot of time. We anticipated working on the iPad version for around 3 months. It turned out to be over 6. We love what we do, but the bottom line is Tapbots is a business and the end goal is for us to make a living. We are just 2 guys at this company both with a family/kids to take care of. We also think charging $3 for each version is fair considering most of the other universal twitter apps charge more. If you don’t have an iPhone or iPad, you aren’t stuck paying more for a universal version.

So that’s about it! We hope you enjoy the new app and we will be working hard on bringing you improvements. Buy Tweetbot for the iPad here!

Version 1.0.2

This is going to be a bug fix release. We’ve been working on this for a couple weeks now and it should be ready to ship off to Apple sometime this week. There’s over 2 dozen tweaks and fixes in this release, some of the major ones are listed below.

• Greatly improved performance when switching accounts.
• Profile view cleaned up to make it more obvious how to see a user’s timeline as well as including tweet count.
• Fixed performance slow down when app is running for a long time.
• Made it much more obvious that we have support for Read it Later and Instapaper.
• Added “Tiny” font size.
• Readability support.
• Posterous support.

Version 1.1

The main focus in this release is going to be Landscape mode. One of the thing that makes our apps special is that our entire UI is custom. This means our apps look like nothing else, it also means that we can’t just add a couple lines of code and get landscape support. We have to redesign a number of elements in our UI so that they work properly in landscape mode. This takes time and it’s the reason it didn’t make it into the 1.0 release. Once this is done we’re going to support landscape mode on the Post, Media and Web screens.

Native Push Notifications

This is a tricky issue. There’s the technical complexity of having to deal with hundreds of thousands of clients and two totally different services (Twitter’s and Apple’s) but that’s just a matter of time and elbow grease. The thing we worry about with this feature is the costs. We’re not a huge company like Twitter that has a server infrastructure already in place. We’re also not a backed by VCs and can’t afford to lose money and make up for it in “volume”. Servers cost money and bandwidth costs money. There are 3rd party services that help dealing with push notifications but they all charge either by messages or by the user. In other words push, specially in high volumes, isn’t free. I would hope even the people complaining about paying the $2 sales price wouldn’t want to see us lose money on each sale of Tweetbot.

All that being said we do plan to figure out what to do with native push notifications. Hopefully we can get the price per user down enough that it can just be a free feature for everyone. If not we may have to resort to a nominal yearly subscription fee for the service. We’re not looking to make money on push notifications but we also don’t want to lose our shirts on it either. In the meantime, Boxcar is a pretty decent alternative.

A Little Bit of Patience

I’m going to be blunt here–we’re slow. There’s only two of us and everything we do is very purposeful and requires a lot of testing to make sure things work right the first time. Add in all the custom UI, pixel-pushing, localization, beta testing and week long Apple review times and even small changes can seem like they take forever. Please be patient. We do hear your requests and will get to many of them.

Thanks for All the Support

So far Tweetbot has been our most successful bot launch by quite a large margin. It’s really gratifying to see all the hard work pay off with thousands of satisfied users. We’ve been inundated with notes of congratulations and features request. We can’t reply to all of them but we do read them all. Thank you.

What Makes Tweetbot So Special?

Yes, Tweetbot has all the polish and shine you’ve come to expect from a Tapbots app, but that’s not enough to convince everyone to try it. We needed to bring something new to the table.

The most important feature in Tweetbot is its powerful gesture system. This system makes interacting with tweets much more efficient. Want to reference the source of a conversation? Just swipe the tweet to the right. Did someone ask a question on twitter and you are interested in seeing replies? Just swipe to the left. Want tweet details? Double-tap a tweet. You can also double-tap links and a user’s avatar to go straight to the link or user’s profile respectively. Want to quickly block a spammer? Hold down on the user’s avatar for quick options. The same goes for accessing link options.

The second big feature is being able to use your lists as your timeline. Many other clients provide access to lists, but they don’t seem to make them any more important than Twitter does themselves. We wanted to make lists as useful as your main timeline. Sometimes you are following too many people and want to view tweets from smaller groups of people. Tweetbot makes them very accessible.

Another problem we wanted to solve was having more than 5 items in the tab bar. Many apps waste a tab with the “more” button. We decided to keep all 5 tabs as primary navigation and allow the user to quickly select a hidden tab item from either of the last two tabs. Just hold down on one of the tabs and select a new one.

Watch the video demo and learn more about Tweetbot.

Tweetbot is Missing Feature X!

Before you instantly dismiss Tweetbot from having every single feature on the planet, keep in mind that this is version 1.0. We have a big list of features that just didn’t make the first release. Some take longer than others or are just not as important. The bottom line is, we had to ship at some point. We felt Tweetbot in its current state made a good 1.0 and we decided to ship now instead of 2-3 months later. So please be patient with us as we continue to make Tweetbot a better client. Landscape support for composing, viewing images, websites, and videos is coming. We are also looking into our options for native push notifications. We’ve got a big list.

Launch…Crash??

A small percentage of users might have been disappointed to have Tweetbot crash on launch. If you are still running an iPhone 3G or 2nd Gen iPod touch, we are very sorry for this issue. There’s a bug in Apple’s compiler and we screwed up by not testing it enough and catching it earlier. But the good news is, we already submitted a fix for this and have asked Apple to kindly expedite the approval process. We hope it comes out soon. To reiterate, this only affects the older devices.

What Next?

We’ve had many people ask if we will do an iPad or Mac OS version of the app. The answer right now is, “We don’t know.” We will wait and see how things pan out regarding Twitter and the life of [new] 3rd party apps in general.

Thanks!

We truly thank all the alpha/beta testers and our localizers for their hard work, support, and feedback. We also thank our customers for supporting us over the past 3 years. We would not be able to live our dream creating great software without you.

So what are you waiting for? Grab Tweetbot now before the sale ends!

Not convinced?

Here are a few mentions about Tweetbot from various sources:

“Go buy it, trust me. I’ve been using beta versions for the past few weeks and it quickly became my favorite Twitter client.” — John Gruber, Daring Fireball

“It’s simply very well designed and great for power users — particularly those who use Twitter Lists.” — MG Siegler, TechCrunch

“Tweetbot was a risk for Tapbots, but they managed to build the best Twitter client for iPhone I’ve ever had.” — Federico Viticci, MacStories

“Tweetbot has more personality than any other Twitter client out there.” — Shawn Blanc

“If you spend a good deal of your life on Twitter, then you couldn’t find a more pleasant client to spend it with than Tweetbot.” — Matthew Panzarino, The Next Web

Version 1.2 lets you connect multiple devices to your Mac at the same time. If you copy something on the Mac it’ll show up on all your connected devices. If you Paste something from your iPhone/iPad, you’ll get the choice of either sending it to the Mac or to your other connected devices. It’s all pretty cool and should make life easier for all of us with multiple devices.

Pastebot has no eyes for you.

You may have noticed Pastebot v1.2 has an updated app icon. About 2 weeks ago we received a letter from a company claiming that our old Pastebot app icon infringed on their trademarked face logo. After consulting with different lawyers, we were given two simple choices. Try to settle with the company or spend upwards of $250k in legal fees to fight it. We feel that the logos, market and customer base are different enough that we aren’t infringing on their trademark, but we don’t want to waste our time and energy in a protracted legal battle. We want to focus on creating software. After much discussion we decided that the best solution for us was to just settle with the company. We originally suggested changing the color of our icon but that wasn’t sufficient enough. Removing the eyes was the only solution that didn’t make Pastebot unrecognizable and appeased the other party.

We’ve been asked not to publicly identify the company, so don’t ask us who it was. I will say that their trademark was issued before Pastebot was even started, so this isn’t a case of a company using trademark to extort another company. Trademark is also an interesting brand of law in which you have to proactively defend against anyone you think is infringing on your rights. So while we don’t agree that we are infringing on their rights, we understand where they are coming from.

We aren’t happy that we had to change the icon, but really didn’t have a good choice. I’m sure that most people won’t be crazy about the change, but by putting this behind us we can continue to focus on our next app.

App #0003 has finally launched! It’s been 6 long months since we started on this project. I don’t want to turn this into a long post about how we got here, because all that really matters is we made it and hope you’ll enjoy it. Pastebot is definitely different than our previous apps. Some would say it’s riskier. But there’s no other way to grow and move forward without taking risks. After all, who would have thought anyone could make a living creating software for mobile devices? Pastebot was a lot more work than our previous apps, but it also does so much more than them. We are happy with the results and hope you are too.

Visit the Pastebot Website for videos, screenshots, and more info

Download on iTunes

A Quick Thank You

We want to thank our customers for keeping us driven to make more apps. The reviews, emails, and twitter posts have really kept us excited about what we do. We also want to thank our beta testers for all the support and feedback they have given us. They truly helped make Pastebot a better product than it was. And last but definitely not least, we want to thank our localizers (Guy Parrot, Yuzuru Shiraiwa and Tobias Brummer) who have taken their free time to help translate our app into other languages.

Weightbot 1.4

So what’s new? Not much on the outside. OS 3.0 has enabled us to re-engineer the date and weight select scroll views so that they behave as they should. You can now scroll faster and enter weight data back 10 years. We’ve also added a few tap gestures to make things a bit easier. Double-tapping each end of the date view will quickly scroll you forward or back 30 days. Single-tapping the weight-select view will move you one-tenth of a number while double-tapping will move you to the nearest whole number. And that’s pretty much it for this Weightbot update. Remember, this update requires OS 3.0.

We also wanted to quickly mention that the updated graph views are still in the works.

Convertbot 1.4

Convertbot 1.4 is in its final stages of development. Here’s what’s new:

Calculator

We’ve gotten a few requests for the ability to do calculations in Convertbot so we added a simple calculator. We made this optional so if you don’t need this feature, you can still have the simple number pad. It’s disabled by default. As you can see in the screenshot, we had to make slight UI changes to the number pad for consistency.

(Click the image to view the full interface.)

Copy and Paste

You can now copy and paste numbers in Convertbot. To access this menu, just hold down the LCD for a second.

(Click the image to view the full interface.)

Other Options

Aside from the ability to enable/disable the new calculator, we’ve added 2 more options that may be useful to you. The first option is the ability to disable the automatic currency updater. This has been requested by many international travelers in order to conserve data consumption. We’ve also added the ability to limit decimal places for your conversion results.

A few new units will be added, but the final list hasn’t been determined yet. This next release of Convertbot will also be OS 3.0+ only. It should be submitted to Apple in about week or so.

The Data

When Convertbot launches, it grabs the latest currency conversion data from our server. Using the headers that Apple includes as part of every HTTP request and a couple extra ones that we throw in for reporting purposes we are able to see unique requests by OS and device version through each day of June. The average number of requests per day is ~3250. The number of iPhone devices is about 6 times greater then the number of iPod Touches. I also filtered out anyone not running Converbot 1.3 and then normalized each day’s numbers so that each day adds up to 100%. The reason I filtered out anyone running an older version is because those folks aren’t likely to be impacted by changing Convertbot to 3.0 only.

The Graphs

The data seems pretty clear. Prior to June 8th we have a fairly low adoption rate of ~3%. Starting on June 9 this jumps up to 6-8%, which can be directly tracked to the developer release at WWDC. Starting on June 17th we get a huge jump as all the non devs start upgrading. We’re currently running at an overall 75% upgrade rate which is pretty insane considering the number of devices and the fact that its only been 5 days.

Overall Upgrade Rates

This graph adds up both the iPhone and iPod devices and just measures overall upgrade rate for both devices.

iPhone Upgrade Rate

Given how many more iPhone devices there are vs iPod Touches it isn’t very surprising that this graph looks fairly similar to the Overall graph. The iPhone upgrade rate is a bit higher then the overall rate, currently sitting at 79%.

iPod Touch Upgrade Rate

This is somewhat more interesting and shows the impact of that annoying $10 fee that Apple charges for upgrades. While the iPhone upgrade is almost 80% the iPod Touch has just passed 50%.

Conclusion

It’s somewhat early to draw an overall market conclusion from our single sample. It’s pretty clear that at least our customers are upgrading to 3.0 at an incredibly fast pace. We’ll be keeping an eye over the next couple weeks and will update this post as needed with newer numbers. As I said before we don’t currently have any plans to make Convertbot or Weightbot 3.0 only, though they both have been submitted to Apple with some minor 3.0 bug fixes (which are still pending approval). However, our third app will be 3.0 only, as will anything else we do after that. So if you haven’t upgraded yet, what are you waiting for?

Quick Update

To answer some of the questions that have been asked in the comments. The Convertbot 1.3 update rate is ~87%, if you add in folks running 1.2 that goes up to ~94%. There are a few folks still running the original 1.0 version which I find quite interesting. If you add in the folks running all the older versions we are looking at 70-71% as far as the conversion rates to 3.0 goes. And for those folks running the older version the OS 3.0 conversion rate is only ~37%.