Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'd like to, but I don't think Zood Location meets the policy requirements for inclusion in F-Droid. Blockers are:

* Usage of the Google Maps SDK - the service needs revenue to be able to support running and maintaining it's own tile server

* Usage of push messages via Firebase - the zood server has no problem with a socket remaining open all the time with the Android app, I'm simply not sure what the impact would be on the battery.

* Usage of the FusedLocationProvider API - a code path needs to be added that would simply use the platform provided GPS access. It wouldn't be too difficult, but it would hurt accuracy and battery life.

* Usage of locationiq.com API - similar to the need for a Zood tile server, I would need to stand up my own reverse geocoding API somewhere so F-Droid wouldn't need an API key for locationiq

That all said, I do think it's a worthwhile endeavor to make the app F-Droid compatible. I just can't provide any guarantees about when that would be.



Regarding locationiq, you could provide an option when sharing to disable geocoding. There are many cases (eg: when hiking in the wild) where it provides little value.

This could be done in a querystring argument in the shared URL hash: &geocoding=false


Fair enough! Thanks again for the excellent answers, Zood looks really promising.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: