Really so what you're saying is that if Google builds the apps and distributes them, that's Okay but if Microsoft or any third party ISV builds an app using their public APIs and then distributes that is a blood-soaked hitchhiker?
Since Microsoft has been through the Anti-Trust wringer before, you can bet that this little problem will get all the attention they can dig out of it, in the press and with the DOJ lawyers and the FTC. If Google publishes an API and says "use it, it's open" and then somebody picks up that mantle and builds something using it only to have Google shut it down for fictitious reasons, then at that point you have to call bullshit on the whole openness agenda and "do no evil." When Apple pulled Google Maps out of IOS, Google cried foul because Apple has to approve all apps on their platform and yes, Apple's customers cried foul as well because the Apple Maps app sucked but it seems that Apple, Google and Microsoft are all in this little arms race of what they call "open" APIs and services but when somebody implements an API using them that happens to be another 800 lb gorilla you bet the games will start. Eventually if they don't play nice, it'll wind up in court with a long drawn out legal proceeding and while Google has dodged a few bullets of late, they won't dodge a bullet if MSFT comes back with documentation that Google is playing tricks to maintain a competitive advantage. After all, Google announced that they wouldn't be building apps for Windows Phone.