Developer Iwo Banaś is not having a good week. The free version of his SCR Screen Recorder app, which we featured on Android Police last month, was unceremoniously kicked off of the Play Store for "Violation of the System Interference provision of the Content Policy." Exactly what that means is outlined in a Google Support document: basically it says that ads can't impersonate portions of the Android interface or imply that they're something that they're not, like a fake virus warning or Facebook message.
One of the great things about Android's ecosystem is the number of indie developers who are able to enter the market successfully, providing a great product and inspiring would-be developers to join in. For many though, Android development in general is a mysterious topic. How an app or game goes from an idea to an entry in the Play Store is unknown, but (thankfully) not unknowable.
Of course, considering how major development studios bring apps to life doesn't require too much thought – major companies like EA, Disney, or Rockstar have no problem hiring designers and developers to crank out and maintain polished apps.
On the night before Google I/O 2011, I posted an open call for any questions you might have had for Google core developers. And you delivered - within a few hours, we had over 50 questions of varying complexities, and I realized I was in trouble. Office hours are meant for developers asking dev questions, whereas most of the ones you've asked were about policies and availability. Still, I proceeded to ask away at office hours and at the end of each session, fearing being shunned forever.
On March 31st, the Android Developer Console, which developers use to publish their apps to the Market, started experiencing issues that ranged from 404s and disappearing applications to missing statistics and apps that no longer obeyed.
As more and more panicking developers chimed in with similar experiences to multiple support threads, the only response from Google so far came from an employee named Ash back on the very first day, apologizing for the inconvenience and then shortly after announcing that all issues had been fixed.
The Android dev team has generally been assumed to have a passive stance on rooting and unlocking Android devices. That is, do it if you want - we won't stop you. And there's certainly evidence abound supporting this - Google's Nexus One could be unlocked via a simple ADB (Android Device Bridge) command: fastboot oem unlock. The same is true of the Nexus S.
Of course, it only makes sense - Google doesn't want to put any unnecessary barriers between Android developers and the open source OS, especially on developer phones.