As a further note with custom builds, rooted phones etc. I don't think that there will ever be a hardware identifier you can trust 100%
-- RichardC On Oct 26, 8:37 pm, "nEx.Software" <[email protected]> wrote: > The Market is most definitely tied to the Account and not the Device. > I switch between devices all the time and am able to maintain my > purchased apps on each of those devices via the Market. > > On Oct 26, 12:35 pm, Wayne Wenthin <[email protected]> wrote: > > > Well then you won't like the market. I am almost positive (having went > > through 3 phones) that the market is tied in someway to the handset not the > > google account. As a developer I echo the idea of the original poster. > > Since my upcoming app requires a unique ID to be able to play I would love > > to have a report of the unique purchasers. > > > On Mon, Oct 26, 2009 at 12:09 PM, RichardC > > <[email protected]>wrote: > > > > Hi, > > > > As I user as well as a developer I don't like the idea of linking apps > > > a particualar device. > > > > My understanding is that applicatons I download are linked to my > > > Google account so if I change my phone (upgrade or replacement) once I > > > log back into the market I can re-download my free and paid for > > > programs. > > > > I would be most upset to find that an application I had legally bought > > > would not install onto a replacement phone and required me to purchase > > > it again. > > > > Just my thoughts, regards > > > > -- > > > RichardC > > > > On Oct 26, 3:35 pm, knavewave <[email protected]> wrote: > > > > 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? > > > -- > > Writing code is one of few things > > that teaches me I don't know everything. > > >http://www.fuligin.com > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
