TrivialDrive vs TrivialDrive V2? - android

Why are there two versions of TrivialDrive?
https://github.com/googlesamples/android-play-billing
Which version should be the main reference project for learning in-app billing? What's the difference between the versions?

A little searching shows that Trival Drive V2 sample has a shared build.gradle file:
https://github.com/googlesamples/android-play-billing/blob/master/TrivialDrive_v2/shared-module/build.gradle
which has the following line:
compile 'com.android.billingclient:billing:dp-1'
Looking at the documentation here:
https://developer.android.com/google/play/billing/billing_library.html
Shows that Google just released a new version of the Billing Library release dp-1:
Starting with Play Billing Library release dp-1 (June 2017), the minimum
supported API level is Android 2.2 (API level 8). The minimum supported
In-app Billing API is version 3.
And specifically calls out changes to the minimum support Android API and In-app Billing API.
Given the Trivial Drive V2 sample app(s) has a Wear 2.0 example - this version has billing support on Wear 2.0 apps.

TrivialDrive_v2 demonstrates a new way of integration with Google Play Billing.
It's based on the latest release of Play Billing library (currently 1.0) and tries to promote the best practices of integration with it.
TrivialDrive sample was kept for those that still use an integration via AIDL file (e.g. C++ developers).

Trivial Drive V2 is refreshed sample for new release of Google Play Billing Library. See that link: https://android-developers.googleblog.com/2017/06/money-made-easily-with-new-google-play.html

Related

Where can I find the sample project Trivial Drive (Kotlin) which supports Google Play Billing Library version 5?

I'm learning Google Play Billing Library version 5 only for in-app items .
I have foud the official sample project Trivial Drive (Kotlin) only to support Google Play Billing Library version 4.
Is there a branch of Trivial Drive (Kotlin) to support Google Play Billing Library version 5? or is there other sample project of Kotlin to support Google Play Billing Library version 5 ?

Google Play Billing Unity plugin alternative

I'm new to Unity IAP. When looking for a way to integrate Google Play IAP into a unity project, I found the "Use the Google Play Billing Library with Unity" documentation which states:
The Google Play Billing Unity plugin will not be receiving updates moving forward. This means that the plugin will remain specific to Google Play Billing Library 3. Additionally, any apps that are updated after November 1, 2022 will no longer be able to use the plugin.
Does Google provide an alternative? Or should I just use Unity's IAP integration directly instead?
I came across the same text just now. I believe you are correct in your assumption that Unity IAP is the correct replacement for this, since according to their documentation UnityIAPGooglePlay the current version of this plugin already uses Google Play Billing v4, which is the minimum required version starting Nov 1.

Google Play Billing API for Xamarin .NET?

I need to use the Google Play Billing API, in an Android app that I am building with Visual Studio Xamarin.
All the documentation I've found references Android Studio and build.gradle, which I don't have.
I've searched high & low for a Visual Studio answer to this, but I must be missing something because I have found nothing.
Any suggestions would be welcome on how to use the Google Play Billing API, in an Android app.
Thanks

Android IABHelper vs Billingclient

In our android app, we are using in app billing using IabHelper wrapper library. Example
https://github.com/googlesamples/android-play-billing/tree/master/TrivialDrive
Now, Google added newer version of the library with lot of changes to it.
https://developer.android.com/google/play/billing/billing_library.html
Which version should we use? When will the Olderversion(v3) of the biller library expire?
As said on google official documentation, the AIDL way is/will not be supported anymore,
https://developer.android.com/google/play/billing/migrate
This topic describes how to migrate away from a billing integration
that uses the Android Interface Definition Language (AIDL). Accessing
Google Play's billing system using AIDL is deprecated, and all
integrations must use the Google Play Billing Library in the future.
This link also includes a guid to migrate from AIDL to the new billing library.

Does Google Play Services pre-release versions to developers?

I might be spoiled having worked on iOS for so long, but does Google release Google Play Service beta versions for developers prior to releasing the full versions to the public?
I'm currently working on an SDK project, and would like to test out the latest Google Play Services versions as early as possible, preferably before the full Google Play Services updates are released, to ensure that the SDK maintains functionality with the latest and greatest.
Am I missing something in the documentation? Is there a place where beta / test versions are announced before a full release?
does Google release Google Play Service beta versions for developers prior to releasing the full versions to the public?
No. They do the opposite -- they do not release the updated Play Services SDK until a preponderance of devices have been updated to be able to support it. If your app is using the new SDK, and it winds up on a device with an old Play Services Framework, part of your use of the SDK will involve prompting the user to upgrade their Play Services Framework.
They do an admirable job on backwards compatibility on the whole, so apps written using earlier versions of the Play Services SDK usually continue to work on devices with new versions of the Play Services Framework.
Is there a place where beta / test versions are announced before a full release?
Announcements about general capabilities are sometimes made on the Android Developers Blog, such as this post about the release of Play Services 6.5.

Categories

Resources