I am preparing to deploy a service based (account info / functionality provided via my server) app via the standard android market / google checkout approach, and am curious to see if anyone has had success or can propose suggestions on how to associate market purchases with individual devices.
The only definitive solution I can come up with is to integrate with checkout's order notification API, and have some sort of 'secret' sent back to the purchaser's email address. This, of course, is the sort of thing that is really annoying from the user's perspective. If there were some way to tie the purchase order with the account (ex: if market were to send the phones hardware id), all of this would be possible behind the scenes. Any thoughts are greatly appreciated. Also, for those who have sold apps in the market.... - Will we receive a 'new order notification' from checkout as soon as someone buys our app, or is it after the 24/48 hour period? Similarly, do we get the various state change events, if the user returns the app? - Do any of the checkout notification fields contain android specific notes / identifiers such that a market purchase can be identified from a non-market purchase? - Are there any fields that uniquely identify a device? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
