Difference between revisions of "In-App Purchase"
(Created page with "Comparison of In-app Purchase APIs. {| class="wikitable" |- ! Feature ! Apple's Store Kit (IAP) ! Google Play |- | User Validation | Apple doesn't require a developer to imple...") |
m |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 3: | Line 3: | ||
|- | |- | ||
! Feature | ! Feature | ||
| − | ! Apple's Store Kit (IAP) | + | ! Apple's [https://developer.apple.com/reference/storekit Store Kit] (IAP) |
| − | ! Google Play | + | ! Google Play [https://developer.android.com/google/play/billing/index.html In-app Billing] |
|- | |- | ||
| User Validation | | User Validation | ||
| Apple doesn't require a developer to implement any user validation. | | Apple doesn't require a developer to implement any user validation. | ||
| − | A developer | + | A developer should always trust the Store Kit about the fact of who made a purchase. |
| − | | Google strongly recommends to verify who the user who did the purchase, by adding and generating extra information about the purchase (aka Developer Payload). | + | | Google strongly recommends to verify who the user who did the purchase, by adding and generating extra information about the purchase (aka [https://developer.android.com/google/play/billing/billing_best_practices.html#payload Developer Payload]). |
| − | It's also recommended to have | + | It's also recommended to have an "own secure server" to track purchases. |
| + | |||
| + | A few stackoverflow links a user id: [http://stackoverflow.com/questions/33033418/android-get-user-id-without-requiring-scary-for-user-permissions] [http://stackoverflow.com/questions/2245545/accessing-google-account-id-username-via-android]. An explanation of payload is [http://stackoverflow.com/questions/17196562/token-that-identify-the-user/17205999#17205999]. Trying to identify a user, should not scare the user away. After all, they're trying to be entertained. They are not here for some spyware, but for a game | ||
|} | |} | ||
==See Also== | ==See Also== | ||
*[[Android]] | *[[Android]] | ||
[[Category:Dev]] | [[Category:Dev]] | ||
Latest revision as of 23:03, 9 February 2017
Comparison of In-app Purchase APIs.
| Feature | Apple's Store Kit (IAP) | Google Play In-app Billing |
|---|---|---|
| User Validation | Apple doesn't require a developer to implement any user validation.
A developer should always trust the Store Kit about the fact of who made a purchase. |
Google strongly recommends to verify who the user who did the purchase, by adding and generating extra information about the purchase (aka Developer Payload).
It's also recommended to have an "own secure server" to track purchases. A few stackoverflow links a user id: [1] [2]. An explanation of payload is [3]. Trying to identify a user, should not scare the user away. After all, they're trying to be entertained. They are not here for some spyware, but for a game |
