-
Notifications
You must be signed in to change notification settings - Fork 607
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
GPSLogger has been removed from the Play Store, and development has been paused. #849
Comments
As it is no longer on the Google Play Store as discussed mendhak/gpslogger#849
@mendhak First of all, thanks for sharing your precious work with the Community. |
As it is no longer on the Google Play Store as discussed mendhak/gpslogger#849
Thank you so much for your work over the years; GPSLogger has been an excellent and very flexible tool. I hope you can find some future for it, either yourself or with a new maintainer. Certainly understood getting fed up with it all though and if this is the end, well, thank you so much! |
…lay]" to "See Also"
I hope you will reconsider, our business is GPS-based and we always trust your App as the defacto standard when it comes to reliability, more power to you mendhak! |
GPSLogger has been my trusted companion through the years, from the first Android I owned, to today. I had different uses for it. Publishing routes, as a client for Nextcloud PhoneTrack and tagging pictures. It was always installed and lately, because of Nextcloud PhoneTrack, always running. While I am sad to see it go, I understand and support Menhac in this decision. It would be nice if the app could reappear on the Play Store, perhaps explicitly stating it won't support newer Android version but supporting older Android versions, as you correctly state that those aren't supported by many GPS Loggers. Many users don't know how to sideload an app. And those also often use older phones. |
The app is not available in the PlayStore anymore, see mendhak/gpslogger#849 Signed-off-by: Kai Kreuzer <kai@openhab.org>
The app is not available in the PlayStore anymore, see mendhak/gpslogger#849 Signed-off-by: Kai Kreuzer <kai@openhab.org>
Thanks a lot for your excellent work. |
@mendhak only just seen this. Do not understand why it has been removed from the Play Store, it's a FOSS GPS tracking app; not some privacy-violating app which surreptitiously sends your data to some unnamed party. It has been my prime GPS surveying app for many years so many thanks for creating it. Thank you for continuing to make APKs available. |
Just an update, for convenience I've made the latest version of the app available on normal F-Droid: https://f-droid.org/en/packages/com.mendhak.gpslogger/ Google Drive integration and Activity recognition have been removed as they make use of Play Services libraries, which is not allowed on F-Droid. I'll also update the top comment in this thread. PS - Thank you everyone for your comments. I do appreciate the support. |
The app is not available in the PlayStore anymore, see mendhak/gpslogger#849
I just found it at F-Droid and can I just say THANK YOU. |
The app is not available in the PlayStore anymore, see mendhak/gpslogger#849 Signed-off-by: Kai Kreuzer <kai@openhab.org>
No stress, buddy. I know exactly how you feel. |
The app is not available in the PlayStore anymore, see mendhak/gpslogger#849 Signed-off-by: Kai Kreuzer <kai@openhab.org>
I just saw this thread and thought I'd make a suggestion here: it may be worth considering making a paid Google Play version, while keeping the GitHub and F-Droid versions free. The reason being that many phones (Intune, corporate, etc.) simply do not allow installation from outside the Play Store, so there are people who cannot use your app no matter how much they want to—even those who are willing to pay for it. And of course the income might help with motivation on your side as well—especially if you make it a recurring subscription (e.g., $1/month) rather than a one-time payment. Of course money can't substitute for lower stress or higher energy, so perhaps this wouldn't make sense in your case. But I thought it might be worth mentioning in case it might be useful depending on your situation. Thanks for making the app! |
Just yesterday GPSLogger has again been unpublished from the Play Store (for the nth time, as usual without warning). Play Store removals are tricky business; I often don't see much reason given except vague statements and links to policy documents, and therefore these situations often require a lot of guessing, rework and resubmitting. These events are a highly stressful time as it's a race to quickly fix things and get the app back on the store.
In the past I've spent effort in getting the app reinstated, however I can't do that any longer; I no longer have the motivation and energy to support GPSLogger development and to deal with the Play Store's moving goalposts. My attention has been focused elsewhere over the past year, and this is evident by my slow replies lack of attention to issues and emails (sorry!). More importantly I am not willing to endure the stress that these store removals cause me.
The core of the issue (why it gets removed) has been that GPSLogger supports a lot of older devices and frameworks, whereas the Play Store is always trying to get everyone onto the latest versions. It's not obvious from here but a majority of GPSLogger users are on older devices. This has led to a lot of complexity in the codebase and inevitably (and expectedly) made it difficult to support and maintain while keeping up with the latest Play Store requirements and user feature requests and PRs and issues, and giving them the attention they deserve.
I'll keep trying to answer some Github issues and direct emails when I can, but still at a slow pace.
The latest APK is still available in releases section but will now require sideloading. It's under the 'Assets' link.
I've also now put the app on F-Droid.
Future options are unknown, I've been trying to mull these over... I don't want to hand the development, account and app over to potential future maintainers; in the unlikely event of someone else wanting to fork and republish, I'd rather the fork get republished with a different name. I say unlikely event, because as mentioned before, the codebase is complex and it might be easier for someone new to just start over. If the motivation and energy ever return I could consider moving to normal F-Droid (proper), which will require stripping out GDrive, Dropbox and a few other proprietary features.
tl;dr - Removed from Play Store, reason unknown. Low energy, high stress. Development on hold. APK is in releases or on F-Droid.
The text was updated successfully, but these errors were encountered: