Yesterday I'd have said 110%, but I dunno... I'm getting this dreamy feeling that something wonderfully developer-friendly might be going on here. Not to mention owning that infrastructure that let folks also -run- back Android apps seems like it'd have value in itself, beyond just the dev PR.
The Church is meticulous about good record keeping (which is what makes them so good at genealogy in the first place), and every official member of the LDS church has a unique member identification number, used for things like tracking donations, ordinance records, and, of course, genealogy. Nowadays, the vast majority of these records are digitized and you can access them online through Church-owned-and-operated websites. If you happen not to be in the system yet (maybe you were baptized in the jungles of New Guinea and have only just made it back to civilization), it's pretty simple to meet up with a bishop or clerk who can verify your paper records and tell you what your membership number is, which will let you set up an account on Church websites.
So, to summarize, the Church knows who its members are, and knows how to associate them with online identities. When one of them wants free access to Ancestry.com, it's basically the same process as "Sign in with Google" and such- you tell Ancestry that you're LDS, Ancestry asks the Church's servers if you're telling the truth, and the Church's authentication system teels Ancestry to let you in.
You ask the membership clerk of your ward for your membership number, which you use to upgrade your familysearch.org account to an LDS account. Then ancestry.com uses OAuth to get access to your familysearch account.
Amazon now has Cloud Player Premium, which is very similar to iTunes Match.
"Import your music collection - even music purchased from iTunes or ripped from CDs. All imported songs we match are instantly made available in Cloud Player and upgraded to high-quality 256 Kbps audio."
Are you still limited to method bodies? It seems reasonable that the method signatures and object layouts couldn't be modified because that would invalidate a lot of code already in memory and that may already be optimized.