This was raised during Devoxx event, but when having a flacky connection, it looks like app startup can sometimes be waiting a long time with a white screen.
I tried resolving early the promise to see if starting the app without any signed in user could be problematic or not, and how the app would behave if it was the case.
I found some really weird behaviour coming from Firebase...
But I assume we should :
Not consider that signInAnonymously() should block app startup
At some point, we should show a spinner telling that it looks like user is having a flacky connection and we're not able to anonymously authenticate him (proposing to refresh the app, or to disable data connection to be completely offline)
This will be far better than the infamous white screen :-)
This was raised during Devoxx event, but when having a flacky connection, it looks like app startup can sometimes be waiting a long time with a white screen.
This seems to be due to the
signInAnonymously()called during startup which is blocking app startup if firebase is not able to resolve anonymous user at startup.I tried resolving early the promise to see if starting the app without any signed in user could be problematic or not, and how the app would behave if it was the case. I found some really weird behaviour coming from Firebase...
But I assume we should :
signInAnonymously()should block app startupThis will be far better than the infamous white screen :-)
Vidéo demonstrating my findings : https://drive.google.com/file/d/1xigjcO3Y9OES7mN9wLka-bXo6th2Y06J/view?usp=sharing
The infamous white screen™ is a reference to @xhanin's talk at Devoxx :-)