Re: [godot-devel] In app purchase apis

[Ariel Manzur <puntob@xxxxxxxxx>]

Do you mean get_product_list? Can you do that on Android? On iOS it wasn't possible last time I used it, the game is supposed to know the list of ids of its products (which makes sense)

On 15 January 2017 at 23:49, 박한얼 <volzhs@xxxxxxxxx> wrote:

I can work with Android - Google play store.

I've not worked with Amazon IAP.

I think base api should have set_product_info( list ).

because we should know the IDs and inquiry them to get to know it's purchased but not consumed.

then we can make it work like "restore_purchse( product_info )" for iOS.

2017-01-13 22:44 GMT+09:00 Juan Linietsky <reduzio@xxxxxxxxx>:

I think Unity has a sort of universal IAP API, does it not? we could use as reference

On Fri, Jan 13, 2017 at 10:43 AM, Rémi Verschelde <rverschelde@xxxxxxxxx> wrote:

2017-01-12 16:33 GMT+01:00 Ariel Manzur <puntob@xxxxxxxxx>:
> Hey guys, (I might not be able to be at the dev meeting today, so I'm
> writing here about the 2 topics I'd like to discuss)
>
> I'd like to standardize on a basic API for in app purchase implementations.
> We currently have the StoreKit implementation for iOS and Google Play for
> Android, and I think they're already vastly different. I don't expect them
> to be 100% transparent layers, where the game doesn't know what the backend
> is, some will have store-specific methods or responses, and on some cases
> the game might want to choose or query which backend it's using (like on
> Android there might be more than one available, for Google, Amazon, etc),
> but it'd be nice to have a base api that all stores implement in a standard
> way.

I fully agree, if we can have a common base with platform-specific
extensions (kind of how is done for the various flavours of InputEvent
or even the OS singleton), I think it would be cleaner code-wise and
simpler to understand for users (and simpler to document too).

> I think the 2 main issues are:
>
> - do we use signals, callbacks, or message queues? I think it's open for
> discussion, I like messages because it's easier on the native module side
> (calling a callback from java is not 100% safe at the moment), and sometimes
> the library has messages to dispatch right after the game launches, which
> could be before the any callbacks or signals are connected, so they would
> get lost.. On the other hand people seem to prefer the other methods
> - what is the base api for this? purchase(), get_product_info(),
> consume_product(), restore_purchase(), what else? and what about purchase
> receipts? I don't remember how those work..
>
> I can refactor the ios code, can anyone do Android? What about the other
> 'big' stores, mainly Amazon?

volzhs did some work on the Android IAP, he might be interested. (I
see he's now subscribed to the ML, he wasn't yet when you posted
initially).

Cheers,
Rémi