In the latest update, Google has rolled out a new update for its Play Store Developer API. The update is inside the shape of Version Three, which has added an entire set of new features for the builders to use.
Apart from the brand-new updates, version 3 supports the functionality of preceding variations, simplifying and improving workflow management.
Interestingly, updates in version 3 are added at the proper time, as Google will roll back versions 1 and 2 of the Google Play Developer API starting December 1, 2019. Thus, it becomes obligatory for all the developers to replace version 3 well before the said date.
To make it convenient for the builders, Google has already made Google Play’s goal API patron libraries available for Java, Python, and similar languages, like-minded with model 3 of the API.
In one of all Google’s blogs via, Vlad Radu, Product Manager, and Nicholas Lativy, Software Engineer, said,
“We wish you benefit from the new features of the Google Play Developer Publishing API and are searching for your persevered feedback to help us improve the publishing enjoyment on Google Play.”
Going forward, it will become important to jump on version three, as failing to do it may result in useless complications. The developers may also be required to “update unique code references to the API version.”
At least more than one plugin can already be used in version three of the API. If there are any issues with the plugins, even after updating to model 3, Google recommends the developer contact the protection crew.
For the builders still using version 1 of the API, the API projects must be linked with the Google Console before changing to model three.
Google Play Developer API is a platform where developers can perform functions like publishing and app-control responsibilities.
In the Subscriptions and In-App Purchases API, the developer can manipulate the in-app purchases and subscriptions. For Publishing APIs, it allows importing and app publishing and performs other publishing-related duties.
Version 3 of the API was first brought at some point in Google I/O ’18. Version 3 was meant to assist in “transactionally starting, managing, and halting staged releases on all tracks.” And it’s made viable through production, open, closed, and inner checking out.
