MotionObj

In SimplyTweet 2.3, you can now configure the sound that is being played when you receive a push notification. It's the only configuration which is done from within SimplyTweet, and not in the Settings app. The reason is technical: there is no way to preview the sounds if you do it in the Settings app. (I know Apple lets you do that in their own app, but I'm mortal).

There are 2 types of push sounds. "Not Active" refers to the sound played when SimplyTweet is either not running, or when it is running, but the screen is off. "Active" refers to the sound played when SimplyTweet is running and the screen is on.

That's it. Enjoy the bird chirpings! (There's a None sound if you really hate birds or any kind of sound.)

SimplyTweet 2.3 has been approved! There's quite a few of you who asked what's new. Those who have been using SimplyTweet for a while may have noticed that I always only put up a snippet of the changes in the App store description.

So here's a longer list:

1. UI changes across every theme, including re-arranging the account view
2. Every theme now has (the same) unread indicator
3. Re-arranged settings in Settings app
4. Various screens, including contact pickers, followers/friends lists and tweet/DM drafting views now has a dark background when using Twilight theme
5. Miles instead of km will be used in proximity search if your system-wide setting is as such
6. Better push handling - upon startup, if there is an application badge, meaning there was a push previously and SimplyTweet was not launched), the mentions and DM timelines will be autoloaded
7. Support for Twitvid.com
8. You can now configure a sound to play when you receive a push (what does it mean by active and not active push sounds?)
9. You can configure a sound to play upon sending a tweet/DM
10. You can now send DMs longer than 140 characters. They get broken up into shorter DMs in reverse order so it reads nicely anywhere. And in SimplyTweet, it tries to concat them together into a long DM. Try it!
11. Post.ly (Posterous) links now display inline if it is short enough.
12. Add support for TwitLonger viewing, similar to inline view for post.ly links
13. Updated icons
14. Favorited tweets are now indicated in timelines
15. When you add a link to Instapaper, the tweet text is now set as the summary

16. You can now delete attachments while drafting a tweet/DM. Hint: press the cancel button

    This is less than half the changes and doesn't include the bug fixes. Sounds good? Buy it at the App Store. Already have it? Help me to rate/review SimplyTweet 2.3 at the App Store.

SimplyTweet 2.2 has just been approved and someone commented that a bug which they reported was not fixed. Actually, I have already fixed it in my codebase and beta testers already have that fix in their hands for quite some time now. What happened?

iPhone applications are allowed to be downloaded from the App store only after going through an approval process. Every update has to be submitted to Apple for approval. Paid and free app go through the same process. Once a developer submits an update for approval, it usually takes 1-2 weeks for it to be approved or rejected. Apple says 94% of updates are processed within 14 days. (SimplyTweet 2.2 was rejected after 26 days, I'm in the top 6%, so unlucky of me). Now, the key thing is, for each application, you can only have 1 update submitted at a time, if you resubmit an update, be it voluntary (you want to fix something broken in that update) or the update was rejected, that update goes to the end of the queue again.

This means that if a developer submitted an update, and let's say it takes an average of 14 days to be approved (we never know, no estimated time is ever given other than the statistic above). On the 7th day, the developer somehow found out that there is a bug in that update. Let us say it is a very simple fix. If the developer decides to fix it and re-submit the update, he will need to wait a fresh 14 days again, i.e a total of 21 days. Again, we'll never know exactly how many days it will take, hence making the problem worse.

What I personally do for SimplyTweet is, unless it is a very critical bug, I will just let it through. Yes, I will have to allow an update with a bug to go through, hoping at the same time that it is not found in the review process, which it almost never does. You got to wonder what the review process is for. I need to do this because pulling the update back and resubmitting the fix doesn't put the fix into the hands of the users faster.

Thank you for contacting the iPhone Developer Program. Your application is currently in review.

Our records show that while your original binary was uploaded on 8/7/09, a new binary was submitted on 8/30/09. Just a reminder that if a binary is resubmitted, the application review process is reset and starts from the beginning.

Each application submitted to Apple has different capabilities, features, and complexity, which means that individual review times vary. Once the application review process has been completed, you will receive an email notification.

That was the reply I received today to my email sent 2 weeks ago asking if anything was wrong with my submission. They forgot to mention that I resubmitted because I was told to do so after 4 weeks of review because they do not like my keywords.

Total bullshit.

It's published a while back, for 2.0 (current version is 2.1, 2.2 is pending approval and was rejected yesterday, while work on 2.3 is finishing). But it is still the most comprehensive review I have ever seen.

Check out the review if you haven't, along with many other detailed reviews..