Offline support for Firebase read operations about ioweb2016 HOT 3 CLOSED

It should be possible to come up with a pretty generic solution for offline read support:

• Write to local offline cache when doing Firebase SET (both if user is signed in or not):
• Write to local offline cache when getting remote updates
• Then when user wants to register to get remote updates automatically trigger the callback with what we have in the local cache for that user/attribute.

from ioweb2016.

I've got code to wrap the Firebase reads in IndexedDB mostly done, and will file a PR for it in a bit.

One issue that I wanted to clarify was how we should handle the (common) case where the web app starts up completely offline, and therefore the OAuth 2 flow never completes, and therefore the Firebase listeners are never established?

I've also noticed that if you start up offline and then get a connection later on, the OAuth 2 flow isn't automatically retried. I am hazy on what happened last year, but I feel like we found a way to get the OAuth 2 flow to eventually complete in that scenario?

from ioweb2016.

We could listen for online events and kick off the fb auth flow that way?

from ioweb2016.