I've got multiple Android apps that are currently distributed via Google Play and the Amazon store. My goal is to automate the app upload process to minimize the time required to upload a new update. I've already done that for Google Play by using the Google Play Developer API.
Is there an equivalent API for the Amazon store for uploading new app versions or do I have reverse engineer the data send by the browser and develop an API library based on that?
I already searched but didn't found anything like that (except for the Amazon cloud deployment API).
I know this is a slightly older post, but since I ended up here I'll add my two cents.
It looks like there is an Amazon Developer Publishing API available here, but I'm not able to try it out yet because it requires developers to request API access. Once I hear back from Amazon, I'll update this answer with more details as to why it does or does not work well with my deployment.
Related
I'm developing an app for android in flutter. Only some people will use it so I do not want to upload it to PlayStore. The problem is, I can make it an apk and install it to devices but I can not update it. Is there a way or a program like TestFlight that I can also update the app for every devices using it?
Without uploading it is not possible, but you have the option to upload it and don't make it publicly available.
The Google Play Store equivalent of Apple's TestFlight is creating an application in the Google Play Console and set up a release that is available for testing and not available for production (live presence in the Store).
This way you app will not be publicly available and you have to add the testers manually, just as it is with TestFlight. New versions will be delivered to the user's who installed the test application. One limitation is that the users need a Google Account to participate in the resting.
You can read about the details here.
We use firebase to distribute test builds internally, check this: https://firebase.google.com/docs/app-distribution
I'm trying to fully automate the entire process of app publishing/updating to the play store by using google's API's.
So far I have found Fastlane tool which allows me to upload apk's files to any line (alpha, beta, production, etc.) but only upload them. There i don't have any other option than accessing the Google play console by web browser and review and publish them manually.
I have also looked at the google play developer API documentation and i haven't found any API related specifically to review and publish of the apps, all i have found are the API's for apk's uploads (via edits).
So my question is: is there any way to automate the process of review and launch of the app through API's?
Thanks in advance
I'm using Android Management API to turn several devices into kiosks for ticketing application. I was able to create an enterprise, enroll a couple of devices, install the app manually and control it via policies. It works just fine.
Now I want to publish my app to Play Store and I want it to be available for the devices enrolled to this enterprise only. As suggested here, I restricted the app to my enterprise in Pricing & Distribution > User programs > Managed Google Play and published my app. Then I added my app to Android Management API policy to get an automatic update. But the app still isn't visible on these devices and doesn't update. When I'm changing the package name in the policy to some existing app, the device is trying to download it. So it seems like a problem with my app in store.
Do I miss something? There are other Google APIs that solve private/enterprise distribution: Android EMM Developers or Custom App Publishing API but there is no information how do these APIs work together and if I still need to register to EMM if I'm using Android Management API? I thought that it should simplify this process, but I'm getting a bit confused.
Also to mention, the enterprise owner and the store owner is the same account.
The Android Management API and the EMM API do similar things. The EMM API currently has a few more features that are slowly being added into the management API. Try to stay with only one of them.
You seem to be doing everything right. Normally the best thing to do is contact Play Console support in this case. You can do this through the help menu in the Play Console, which is on the "?" question mark icon.
If you don't manage to get any help from them, ask them to route the question to the Play Enterprise team and say we asked you to in this StackOverflow answer. You'll need your app package name and enterprise id.
I want to publish a paid-for app on Amazon app store as well as Google Play. I plan on doing two separate builds for my app, one with the Google Play Licensing library incorporated and enabled (for submitting to Google Play) and one with the Licensing library disabled (for submitting to Amazon app store; Amazon has its own Licensing facility). Other than this, the two builds will be identical (same package name etc). Does anyone know whether or not this strategy is a feasible way to go?
A worry I have in particular is app updates. If a user purchases my app from Amazon app store and I publish an update to Google Play, would the user receive a notification telling them that an update is available for them from Google Play?
I currently have apps on both the google play market and Amazon market and have not come across any of the issues you have mentioned above. I am using ecplise and created the apk file using a certificate and used the same apk file for both Android markets.
As they are seperate markets and as you mentioend Amazon has its own authentication meaning google play updates are not an issue and therefore need to be done on both Markets.
Google Play vs Amazon Appstore
Finally, things to look out for is if you have any links referencing the play market you need to change these to the Amazon market, as Amazon will fail it otherwise (upload to Amazon market can take several days), hope this helps.
When you submit the android apk file to the Amazon app store it signs itself and publishes the app.
I uploaded by debug build (not even any signed apk) and amazon accepted it and the app is now in their app store. Amazon might have some sort of automated signing the application.
Make sure you've not implemented anything related to Google play
store.
Good luck!
I am writing an app and face the same situation, I found the best solution was to make your app into a library project and import it into two separate projects for release.
These separate projects would have any changes necessary for launching from a specific store but the bulk of your code would be in one library. That way any updates you do to the library will be carried across to both releases automatically on the next build.
So, I have a few little android apps now, and am thinking about releasing the in the Amazon App Store. However I have one fundamental question I don't see answered anywhere.
How is Licensing handled if you release the app on the amazon store? I am currently using the Google LVL licensing in my paid apps to ensure the user is licensed to run them. I assume that an app sold on Amazon, isn't going to have any connection to tell Google, hey, this app was purchased, they are licensed, so send them an OK TO RUN status when they launch it. Or am I mistaken?
Does Amazon have its own LVL type code? Or do you just have to forget licensing all together if you want to sell on Amazon?
Simply remove all LVL code from your app (making it unprotected), then select the copy protection radio button when submitting your app to Amazon. They'll add the licensing code to your app before resigning it and releasing it on the Amazon Appstore.
No store-provided licensing code works in other app stores. Many have rolled their own, with varying degrees of simplicity.
I have an app in Android Market. What should I do to ensure the app
works in the Amazon Appstore?
You should make sure that your app does
not include any copy protection functionality (you have the option to
apply Amazon’s DRM technology – see our FAQ on DRM). You should also
take a moment to understand the different signing options available to
you (developer signed or Amazon signed) and choose the option that
works best for your users.
Source