May 24, 2010 | by Andrew Kameka
For all the excitement of Froyo being unveiled at Google I/O and then delivered to Nexus One owners days later, it’s been an afterthought that Froyo is actually causing quite a few headaches where apps are concerned. As we saw when Android 1.5 (Cupcake) and Android 1.6 (Donut) were first introduced last year, certain apps have become spotty or downright unusable after the introduction of 2.2
Whether it’s the CoPilot Live navigation app, Rhapsody streaming music app, or Seesmic Twitter/Buzz client, several Twitter users are reporting that their must-have apps aren’t working since applying the update. The apps will likely be operational once developers are able to diagnose problems and release an update into the Android Market, but devs haven’t had much time to do that.
This episode of update-prompted app woes is a glaring reminder that Google is not giving developers enough time to test their apps on new versions of Android. Every time Google releases a new treat, the buffer between developers getting the SDK and consumers getting the update shrinks. The latest buffer lasted all of 48 hours. That just leads to frustrated devs receiving waves of complaints and support requests before they even get a chance to fire up the emulator and see what still works.
Google does a great job of getting new features to users, but the Android team needs to give developers a bit more time making sure their apps will be compatible with those features.