Use one account in 1000 devices - android

we have a business where we have developed an android platform in 1,000 devices inside taxis.
For this, we need to login 1,000x into play store.
We have used one account so far (test#gmail.com) but it seems that often it automatically logs out on many devices, even though it should permanently be logged in, to receive software updates.
We currently tried to log in around 80 devices, but about 40 of them get logged out of Play Store.
Is the issue that we can't login multiple devices with 1 account or what can be the problem?
Are we able to use one account and keep them logged in on all devices?

From Google Play Terms of Service
Limits on access on Devices. Google may from time to time place limits
on the number of Devices and/or software applications you may use to
access Content (for more information, please visit the Help link for
the relevant Content within Google Play). Google may record and store
the unique device identifier numbers of your Devices in order to
enforce such limits.

Related

Firebase analytics not providing logged events from all users

We currently have about 10,000 android devices of those 10,000. About 8,800 of those devices are running Android 7.1.1. On two of the eight applications installed on these devices, we decided to use firebase analytics to be able to collect useful data about how users are using our applications.
Upon looking at the data that was collected in the first week. App_open, a number of events that are being logged from the device. The results did not seem reflective of our user base.
The number of users who had information being logged was roughly about 800 users.
Its should be noted that we do not use the google play store to release and update our application and use the device manufacturer's store to upload and update the applications on these devices.
I know that the information that is collected or logged from the device is cached and posted by google play services.
However, I cannot seem to find a reason why there is such a great disparity in actual and expected results. I was expecting feedback from roughly 8,800 devices.
There are few reasons:
10k devices doesn't mean that they use your app, according to this article apps have in average 29% retention rate within 90 days but it can be much lower(from my experience it can be less then 2%), so in fact at least 70% of users not using your app.
The users that use your app doesn't updated to latest version with analytics.
Also you need to keep in mind that 800 users some of them are new users that just downloaded the app, firebase analytics show all the statistics so in few weeks you will see your retention rate.

Android payment on each device

I have a app that the ambition is to be executed on multiple devices on the same account. The problem is that it payments must be made by per amount of devices it is installed on. Or a Payment like 1-10 devices, 11-20 devices.
At the same time, the ambition is to be able to use Google Play to make it possible to push out updates on the app to all devices at once. But that is in conflict with the Google Play's terms of payments.
I only found how to restrict the app on some devices, but not how to make it possible to take payments per device.
Limit (Restrict) app installations per account (detemined by unique devices) in Android
Are there a solution to make payments per device, and still use Google Play, or are there any other solution?

Android/Google Advertising ID - Is this method of gaining user consent to store permitted?

I'd like to store the Google Advertising IDs from users of an Android app I have, so that at a later date I am able to work with an ad network to target our users based on the information I have about them (for re-engagement, etc).
The Google guidelines around this state:
"Association with personally identifiable information or other identifiers.
The advertising identifier must not be connected to personally identifiable
information or associated with any persistent device identifier
(for example: SSAID, MAC address, IMEI, etc.) without the explicit consent of the user."
How can I gain consent of the user for this? My first thought was a tick box to say 'We have updated our privacy policy, please accept the updated terms to continue', however a 3rd party advertising agency has advised that I can simply update the terms on the Play Store, and that continued use would count as 'explicit consent'. I am concerned about this however, as people using auto-update will presumably never read the text on the Play Store, and this may contravene the guidelines.
Has anyone had any experience with this? This isn't an app I can really afford to get yanked from the Store, so I'd really like to be sure of the rules, rather than risk it and hope no-one notices (if indeed it is incorrect).
Many thanks.
I would do a popupbox with the updated Terms of Service or a link pointing to them with two options: Accept and Quit. This way you have shown them the updated ToS and didn't update them behind their backs.

How to transfer paid android apps from one google account to another google account

I am developing a SYSTEM app for android to manage user accounts on the device.
Is there a way to PROGRAMMATICALLY transfer paid user apps from one account to the other?
Any help is appreciated (even if the reply does not directly target a solution).
Google has this to say on transferring data between accounts.
http://support.google.com/accounts/bin/answer.py?hl=en&answer=63304
It lists certain types of data that CAN be transferred and certain types of data that CAN NOT be transferred. Unfortunately Google Play Apps falls into the NOT category.
It's conveniently titled: "Moving Product Data"
http://support.google.com/accounts/bin/answer.py?hl=en&answer=58582
You will not be able to do that. You can download apps again to the same userid account on different devices, but you cannot transfer those licenses to other userids.
There is no way to do this programatically - I don't think you can do that practically (except for trying to call customer support at the Play Store).
It's totally feasible now. Google now allow you to transfer Android apps between accounts. Please take a look at this link:
https://support.google.com/googleplay/android-developer/checklist/3294213?hl=en
You should be able to transfer the Application to another Username. You would need all your old user information to transfer it. The application would remove it's self from old account to new account. Also you could put a limit on how many times you where allowed to transfer it. If you transfer it to the application could expire after a year and force to buy update.

how to make an app that the buyer can install twice on one device?

I developed a remote app where the user has to provide an ethernet ID for the target device.
For users who have two of these devices I would like to give the possibility to install the app twice, one for each device.
But they should not have to pay for the second one (eg just selling the same app with different package-names might not even be accepted by Apple, while on Android it is possible)
Designing the app in such a way that it works with two devices would make it quite complex to use.
Is there a good workable solution for this for iPhone and/or Android?
Many thanks
From an iPhone perspective, this wouldn't be possible. Selling the app with different package names is a very poor solution for a number of reasons:
As you say, it wouldn't be accepted by the App Store (and would probably be eventually removed from the Android Market if it is just a duplicate app).
You have no control over which version of the app people download, and then need to keep track of this, which is overly complex.
2 versions of the app would be acceptable if the user has 2 devices, but what if they have 3? What if they had 10?
To me, this would seem like an issue that would be solved by some sort of severside registration server which links up to some logic within the app in order to determine whether the user has made the necessary payment in order to use the app.
In other words -- and if I am understanding the concept of your app correctly (more explanation would be needed for a more complete answer) -- the user goes onto your site (or within the app) and creates an account, registering their Ethernet ID(s) and arranging any payment (or does this via in-app purchase). You could even charge on a per-device basis and have this built in to the app via in-app purchasing.
So the app itself would be free, but in order to use the app they would need an account which has been registered with you in order to ensure it is only being used by paid users.
Not sure exactly what you trying to build but there are other apps (games & tools) have a client and a server app.
Usually people give the client app away for free, but charge for the server app.
Another way, you could do in-app billing so give the app away for free, but charge for the features in the app to unlock it.
Implement your own registration server that keeps track of registered/licensed devices a user has.
That would you would know that a user has bought the required upgrade that can be used with his/her registration on x number of devices.
Each device the user downloads the app onto and logs into their account.
The app could check check if they have purchased the licence on at least one of their devices, thus unlocking the features.
Not definitive, but those are the two ways I would look into if I were developing such an application
Any iOS app from the App store can already be installed on multiple devices, as many as are logged into to the same iTunes customer account. The customer only pays once for one to as many installs as they have devices on that same account.

Categories

Resources