You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A new developer policy update by Google Play requires all apps with health features to register as an organization, which is not something I'm looking to do (there's a bunch of extra requirements: DUNS number [registering a business], support phone listing, etc).
I don't believe Trail Sense has health features, but it made me fill out the form for the Activity Recognition permission (pedometer). I provided details on how it is used in Trail Sense, and I'm hoping Google doesn't make Trail Sense subject to this new policy.
If it does (Google has not provided a timeline), then I will be disabling the Pedometer feature on the Google Play version of Trail Sense. I will need to investigate the following (not changing unless Google forces me to):
Removal of permissions for a build variant
Hiding of features for a build variant
My hope is Trail Sense won't be subject to this new policy and there is no difference between the F-Droid and Google Play builds, but I don't want to be caught off guard. I know this would be much less than ideal, but Google's policies have also been less than ideal as well.
A new developer policy update by Google Play requires all apps with health features to register as an organization, which is not something I'm looking to do (there's a bunch of extra requirements: DUNS number [registering a business], support phone listing, etc).
I don't believe Trail Sense has health features, but it made me fill out the form for the Activity Recognition permission (pedometer). I provided details on how it is used in Trail Sense, and I'm hoping Google doesn't make Trail Sense subject to this new policy.
If it does (Google has not provided a timeline), then I will be disabling the Pedometer feature on the Google Play version of Trail Sense. I will need to investigate the following (not changing unless Google forces me to):
My hope is Trail Sense won't be subject to this new policy and there is no difference between the F-Droid and Google Play builds, but I don't want to be caught off guard. I know this would be much less than ideal, but Google's policies have also been less than ideal as well.
The text was updated successfully, but these errors were encountered: