Only just saw your reply, thanks Trevor.

It looks like this will support just what I need. In my case, I'm
going to have a small number of item classes, but each item the user
buys will be unique. The uniquifying data will be small - just a
couple of dozen bytes at most and acts as a natural key for any
further item data.

It looks like the In-app Billing API provides everything I need :)

Tom.

On 4 February 2011 02:41, Trevor Johns <[email protected]> wrote:
> The primary problem is that the developer payload field is limited in size.
> Whatever data you put there has to travel through our entire billing system.
> Save the content to a datastore somewhere (either on-device or on a
> third-party server), then put the record ID in the developer payload field
> and you'll be fine.
> --
> Trevor Johns
> Developer Programs Engineer, Android
> http://developer.android.com
>
>
> On Wed, Feb 2, 2011 at 2:11 PM, tomgibara <[email protected]> wrote:
>>
>> I've just finished reading the preliminary documentation for in-app
>> billing.
>>
>> If I've understood correctly, as part of the billing request you can
>> supply:
>>
>> * ITEM_ID which is limited to a small number of pre-registered product
>> ids
>> * DEVELOPER_PAYLOAD unconstrained - but with caveats?
>>
>> and these are the only two pieces of data you can send to identify the
>> product being purchased. But even the DEVELOPER_PAYLOAD appears to be
>> off-limits; the documentation contains the following (rather cryptic)
>> advice:
>>
>>  We recommend that you do not use this field to send data or content.
>>
>> I take this to mean product data/content, but that's no more than a
>> guess, and if that's the correct interpretation, why? The result seems
>> to be that you can't sell individuated items.
>>
>> I was hoping to use the in-app billing system to allow purchases of
>> dynamically generated designs from my forthcoming Metaglow
>> application, but this doesn't appear to be possible without operating
>> some sort of 'credits purchase' system which I think would provide a
>> very poor user experience and which isn't what I want to give users.
>>
>> Can anyone shed light on this?
>>
>> --
>> 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
>
> --
> 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

-- 
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

Reply via email to