search

mapswipe / mapswipe

MapSwipe mobile application
https://mapswipe.org
Other
149 stars 26 forks source link

Research switching to firebase-js-sdk #157

Open laurentS opened 4 years ago

laurentS commented 4 years ago

Describe the bug In #120, users are having problems with degoogled android phones, where they can't use the app at all.

App version Any v2.*

To Reproduce Just try to login...

Smartphone (please complete the following information):

Additional context This ticket is to collect notes about switching the firebase sdk from react-native-firebase to firebase-js-sdk which was used in v1.

Based on https://firebase.google.com/docs/web/setup#available-libraries and https://firebase.google.com/support/guides/environments_js-sdk the features we are using should be available, except maybe for analytics. However we had analytics in v1, so there might be a way to make it work. OAuth with OSM may or may not work, would need to investigate further.

There is no built-in offline support in firebase-js-sdk, so there would be a fait bit of work to fix that

laurentS commented 4 years ago

We discussed this with the core developers, and while it would be great to get rid of google trackers, we don't have the resources at this time to work on it (in practice, it means I am the only person developing the app as a side project, and there just aren't enough hours in the week). Several users have reported issues related to not having google services on their phones. If any of you is interested in helping out, this would be a very good place to do so. @MegaArthur @tkas @qeef @Rudloff

ghost commented 4 years ago

I am not an Android developer, therefore not sure about the question I have. I know that to enable Android phones without Google Services, the best is to release the app on F-Droid. F-Droid requires the source code to be open.

How may switching the Firebase client library help with getting rid of proprietary source code?