You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sharing a feature request - would it be possible to implement a connection performance monitoring into the SDK?
I am getting user feedback that at times the connection to firebase is slow and I would like to show them that this is not due to the app but likely due to their slow connection so that they don't keep staring at their phones thinking my app is slow. I already implement reachability but it's too binary (connection/ no connection) and doesn't help with signal strength/ data loss (as far I know).
I know I could implement some form of this myself but figured I would ask first if this something that (a) is already supported and just could not find documentation about (b) something you guys are planning on implementing in a not too distant future.
If the answer is no to both of these, I'd be curious what method would be best to test my connection speed (e.g., Http call to my Cloud Function or downloading a 10kb file from firestore?) and what's the best approach to calibrate what a "slow" connection is (e.g., a 10kb file taking more than x ms or sec to download).
Thanks for the help!
The text was updated successfully, but these errors were encountered:
Any update on if/ when such a feature would be exposed through the public API? I can tell from my console logs that the firebase SDK has some logic to identify when the connection is nonexistent, even when the phone (and open libraries like reachability) thinks that it is connected on a wifi/ cell network.
Hello,
Sharing a feature request - would it be possible to implement a connection performance monitoring into the SDK?
I am getting user feedback that at times the connection to firebase is slow and I would like to show them that this is not due to the app but likely due to their slow connection so that they don't keep staring at their phones thinking my app is slow. I already implement reachability but it's too binary (connection/ no connection) and doesn't help with signal strength/ data loss (as far I know).
I know I could implement some form of this myself but figured I would ask first if this something that (a) is already supported and just could not find documentation about (b) something you guys are planning on implementing in a not too distant future.
If the answer is no to both of these, I'd be curious what method would be best to test my connection speed (e.g., Http call to my Cloud Function or downloading a 10kb file from firestore?) and what's the best approach to calibrate what a "slow" connection is (e.g., a 10kb file taking more than x ms or sec to download).
Thanks for the help!
The text was updated successfully, but these errors were encountered: