You mean, why should you build a for-profit product while relying on someone else's not-for-profit API?

I'm guessing you shouldn't!

I've seen a lot of neat projects come from Google APIs, but that's as far as I'd taking it.

Relying on someone else's good will for the lifeblood of your company is insane.

1 exception, though: Getting started. I could see using Google to get off the ground and then switching to a more reliable API (read: paid for) afterwards.

Having been poor (not 3rd world poor, poor by American standards) I found the most difficult thing is leaving the poverty stricken network. You don't feel like you've made it until you reject the entire mindset. Until then, you feel like you've sold out. My mother still makes me feel guilty and shames me every time I see her. Until you've had a parent who shames you for doing better than they did, you'll never understand the trap. I tell my upper middle class neighbors about this and they can't imagine parents who wouldn't want their children to do better than them. While I still talk to my parents I've dumped the rest of the network. I protect myself and my family from my old network. Their whole way of thinking is poison. With many of them you risk violence, drugs, abuse, sexual abuse, racism, etc. Even if you trust one or two of them you can never trust who they will bring you or your family in contact with. No amount of mentoring or example setting has helped, it just breeds resentment. Their world view traps them right where they are and their rejection, resentment, and hostility to a better way of life creates their poverty and isolation. Sending them to Harvard isn't going to make a damn bit of difference. Well, MAYBE if you sent one or two, but if you sent enough, they'd just ruin Harvard.

I came to the conclusion many years ago that in America poverty is a contagious mindset, nothing more. But I do understand that it is a difficult mindset to escape due to social issues. In all honesty, in most cases the middle class and rich have good reason not to network with the poor.

Google has issued a pretty tepid statement to what appears to be a highly problematic situation.

In its complaint (http://www.ebayinc.com/assets/pdf/fact_sheet/2011_PayPal_DOC...), PayPal alleges in meticulous detail how its chief negotiator over some two years on a major deal with Google for mobile payments on Android brought the deal between the companies to within a hair of signing and then, at the end of the process, did a series of interviews with Google to take a position working on its mobile-payment system. Not only was this person the chief negotiator on that deal, he was also PayPal's senior executive in charge of this area for his employer. On the eve of the anticipated signing (October 31, 2010) after two years of negotiations, Google told PayPal it wanted a restructuring the deal even while it was giving the negotiator a job offer. The negotiator accepted the offer, notified PayPal and was confronted about how this step was seriously problematic from a legal standpoint. He then changed his mind and told Google no. The parties once again revved up the deal and got to a signing stage for the second time by February, 2011. At that point, Google changed its CEO and, with Larry Page back in that role, Google killed the deal and hired the PayPal executive to lead its work in the mobile-payment area.

In the midst of all this, you also have a second PayPal employee who had been hired by Google in 2009 and was under a legal restriction not to solicit PayPal employees for a period of one year. With that restriction still in effect (or so PayPal alleges), she was actively soliciting not only the senior PayPal executive mentioned above but (according to the allegations of the complaint), a series of other PayPal employees who were part of the mobile-payments group.

It is way too early to tell what happened here, but here are a few thoughts:

1. The complaint is incredibly detailed, with much specific evidence of communications and events that do not look good for Google or the individuals sued. This level of detail is highly unusual for a complaint of this type and suggests to me that this is a very serious case, well-prepared and meticulous (and, of course, when the lead attorney is named G. Hopkins Guy III, as he is, you just know you are in trouble).

2. Employees owe a fiduciary duty to their employers to act in the best interest of the company and playing both sides of the fence at the end of a major negotiation is almost certain to raise serious issues about whether such duties were breached. This is possibly an even more serious problem here than is the trade secrets case.

3. California does not recognize the "inevitable disclosure" doctrine by which a former employee can be enjoined from taking a position on grounds that it will be "inevitable" that he would need to disclose important trade secrets in order to perform his duties. That said, any such case involves highly problematic issues and it would not take much evidence for a court to look at the whole picture and say, "what the hell is going on here." Google may be treading on thin ice here.

4. This sort of conduct usually evidences a cynical power play by a major company along "might makes right" grounds. Here, though, it is hard to believe that Google would be that cynical. Nor is PayPal a small company without resources. This part remains puzzling.

5. The real test will come if, as I assume, PayPal seeks to get a preliminary injunction blocking Google from using its mobile-payment technology because it allegedly based on a misappropriation of PayPal's trade secrets. This is where the evidence on both sides will come out and it will be much clearer whether Google did in fact commit wrongs as alleged. Until then, it really is hard to tell.