3 ms·

I think this is misleading. To me it seems the issue is that app developers are being forced to use the proprietary Firebase service, but they are NOT being for

by shawnz 7y ago

I think this is misleading. To me it seems the issue is that app developers are being forced to use the proprietary Firebase service, but they are NOT being forced to use a proprietary library from what I can tell. The library in fact DOES have an open source version available: https://firebaseopensource.com/projects/firebase/firebase-android-sdk/ https://firebaseopensource.com/projects/firebase/firebase-an...

Tepix 7y ago
Nope! firebase-messaging is missing from this open source version.
- evilDagmar 7y ago
  Sounds like an opportunity for someone to sit down and write one. The API and docs for it are fairly palatable and offer some very reasonable guidance on things like exponential backoff. It still doesn't mean that they're going to be able to go without a persistent notification if they want to run their own background service, but that's a change that everyone is required to deal with. "Secret" background services were abused egregiously by bad actors and sloppy coders alike in the past and it's time for that to stop. This carp some people are floating about it incurring "warning" is nonsense--if they looked at the developer docs they'd see how easy it is to avoid that happening.
icebraining 7y ago
From what I can tell, you need firebase-messaging, which doesn't seem to be on that list. Am I reading it wrong? Edit: seems I was reading correctly: https://github.com/firebase/firebase-android-sdk/issues/125#issuecomment-481566392 https://github.com/firebase/firebase-android-sdk/issues/125#...
- shawnz 7y ago
  Ah, thanks for the clarification.