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
Starting October 15th, application with no explicit android.hardware.location.gps use in the manifest and requiring high precision location will be able to get installed on devices without a GPS.
It means that cgeo will be installable on devices where only network-derived location is available. Do we want this, or do we want to restrict (as I believe it is right now) cgeo to platforms with a GPS to ensure a good user experience?
The text was updated successfully, but these errors were encountered:
AFAIR we had this discussion in the past already where we introduced the explicit requirement.
From the support point of view I strongly vote for limiting the availability to GPS enabled devices due to:
In the past we always had users on support claiming c:geo not working, where it finally turned out, that the device did not have GPS. In addition we had quite a bunch of bad ratings on Google Play due to this. This has stopped finally after the change.
Now we have from time to time some users writing us, that they still want c:geo although they are aware that their device does not have GPS. I do link them to our direct APK download. Those users are aware of what they are doing.
Starting October 15th, application with no explicit
android.hardware.location.gps
use in the manifest and requiring high precision location will be able to get installed on devices without a GPS.It means that cgeo will be installable on devices where only network-derived location is available. Do we want this, or do we want to restrict (as I believe it is right now) cgeo to platforms with a GPS to ensure a good user experience?
The text was updated successfully, but these errors were encountered: