Ian, thanks for the new API, it looks much better comparison to old one. May I point to few odd things I've found in new sample:
* MainActivity.onDestroy() does not call super.onDestroy() making app crash. * Security.verify() always return "true" not taking into account "verifyed" value. Also, may I ask you to comment (maybe here) on the question I've posted recently: http://stackoverflow.com/questions/13825533/in-app-billing-v3-reliability-flaw -Lev tiistai, 11. joulukuuta 2012 20.39.37 UTC+2 Ian Ni-Lewis kirjoitti: > > I think you may be confusing the client-side helpers for Google Play > Services with the actual Google Play Services interface. GPS is a service > and it is accessed like any service, via either intents or AIDL. Billing v3 > is simple enough that it doesn't really need any further client-side help. > But we made a sample anyway, mostly because we realize that things like > service lifetimes and background threads are hard to get right. > > For those who are wondering if you should switch: the answer is probably > "yes." IABv2 turned out to be very, very easy to get wrong. V3 is pretty > easy to get right. There are a couple things that v3 doesn't support yet > (subscriptions, mostly) but if v3 covers your needs, you should use it. > Ian > > On Monday, December 10, 2012 6:51:09 PM UTC-8, Nikolay Elenkov wrote: >> >> On Tue, Dec 11, 2012 at 11:00 AM, Nikolay Elenkov >> <[email protected]> wrote: >> > On Tue, Dec 11, 2012 at 10:16 AM, Nikolay Elenkov >> > <[email protected]> wrote: >> >> On Tue, Dec 11, 2012 at 9:56 AM, MathieuB <[email protected]> wrote: >> >>> Hello everyone! >> >>> >> >>> Today, the Developers blog announced a new version of the in-app >> billing >> >>> system : >> >>> >> http://android-developers.blogspot.ca/2012/12/in-app-billing-version-3.html >> >>> >> >>> Just wanted to discuss about it. How is it compared to implementing >> in-app >> >>> billing with v2? >> >>> >> >>> I did try the v2, and it was really non-intuitive and a really bad >> >>> experience overall. >> >> >> >> It may well be, but it (mostly) works. Considering the experience with >> the >> >> initial API, I'd wait a while before jumping ship to see how an where >> >> it breaks. >> > >> > The funny thing is that say: >> > >> > 'More robust architecture resulting in *fewer* lost transactions' >> >> And instead of doing another AIDL+Helper class, this should have >> really been integrated into Google Play Services. What's the point >> of calling it 'Google Play Services' if you can't use it to interact >> with the actual Play Store? >> > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
