In-App Purchase - Revision history

Skalogryz at 04:03, 10 February 2017

2017-02-10T04:03:51Z

Skalogryz at 04:03, 10 February 2017

2017-02-10T04:03:17Z

Skalogryz at 03:56, 10 February 2017

2017-02-10T03:56:33Z

Skalogryz at 03:56, 10 February 2017

2017-02-10T03:56:14Z

Skalogryz at 03:55, 10 February 2017

2017-02-10T03:55:45Z

Skalogryz at 03:53, 10 February 2017

2017-02-10T03:53:32Z

Skalogryz at 03:53, 10 February 2017

2017-02-10T03:53:15Z

Skalogryz at 03:53, 10 February 2017

2017-02-10T03:53:01Z

Skalogryz at 03:52, 10 February 2017

2017-02-10T03:52:11Z

Skalogryz: 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..."

2017-02-10T03:51:15Z

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

New page

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 implement any user validation.
A developer can always trust the System API on 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 a dedicated secure server to track of purchases.
|}
==See Also==
*[[Android]]
[[Category:Dev]]

@@ Line 13: / Line 13: @@
 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 have some fun and entertainment, they are not here for some spyware, but for a game
+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==
 *[[Android]]
 [[Category:Dev]]

@@ Line 11: / Line 11: @@
 | 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 an "own secure server" to track of purchases.
+It's also recommended to have an "own secure server" to track purchases.
 |}
 ==See Also==
 *[[Android]]
 [[Category:Dev]]

@@ Line 4: / Line 4: @@
 ! Feature
 ! Apple's [https://developer.apple.com/reference/storekit Store Kit] (IAP)
-! [Google Play In-app Billing https://developer.android.com/google/play/billing/index.html]
+! Google Play [https://developer.android.com/google/play/billing/index.html In-app Billing]
 |-
 | User Validation

@@ Line 4: / Line 4: @@
 ! Feature
 ! Apple's [https://developer.apple.com/reference/storekit Store Kit] (IAP)
-! Google Play In-app Billing
+! [Google Play In-app Billing https://developer.android.com/google/play/billing/index.html]
 |-
 | User Validation

@@ Line 3: / Line 3: @@
 |-
 ! Feature
-! Apple's Store Kit (IAP)
+! Apple's [https://developer.apple.com/reference/storekit Store Kit] (IAP)
 ! Google Play In-app Billing
 |-

@@ Line 8: / Line 8: @@
 | User Validation
 | Apple doesn't require a developer to implement any user validation.
-A developer can always trust the System API on the fact of who made a purchase.
+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 [https://developer.android.com/google/play/billing/billing_best_practices.html#payload Developer Payload]).