Earlier this morning, Iain Dodsworth, creator of TweetDeck, posted that the day could potentially be "manic". While he cautioned the day's updates would not be list-related, as many updates from his competitors have been over the last week, it was hinted it would not be desktop related either. That left the iPhone, as TweetDeck doesn't yet have a Web option. But the iPhone release was found buggy, was later pulled, and now the service, and its devoted followers, are once again in a holding pattern with Apple - which makes them the undesired middleman. And yes, that means the day is officially "manic".While I doubt few would want Apple's role as moderator to completely disappear, there should be some way to quickly post point releases or bug fixes for products that have previously been approved.
The Morning Started Off Well...
But Too Many Crash Reports Prompted a Pull...
And After Resubmission, All Wait for Apple.
For whatever reason, TweetDeck's quality assurance process did not catch that the new version of the application would crash as frequently as was reported, but once it was in the wild, it proved too much to accept. The next step was to pull the update from the store, resulting in false positives from would-be downloaders, myself included, who were told it was available, but that the item had been removed.
Now, after the team thinks they scrambled the troops and got a working version ready and submitted a few hours later, they have to wait for Cupertino to agree. The new version reportedly added Facebook support, which had previously been limited to the desktop application, as well as video uploading, integrated with 12seconds.tv, a new Landscape compose mode, trending topics support, a "Nearby" option that showed when Twitter friends were close, thanks to the iPhone's built-in GPS, and the option to open new links in Safari.
But we'll still have to wait, at least until Apple agrees their bug-free version is good enough. Until then, all we have is a video of the promised new updates (See below).
So what's the solution? Is this Apple's fault for forcing a wait, or TweetDeck's for bad code?