diff options
| author | Daniel Micay <danielmicay@gmail.com> | 2021-04-06 22:14:07 -0400 |
|---|---|---|
| committer | Daniel Micay <danielmicay@gmail.com> | 2021-04-06 22:14:07 -0400 |
| commit | d7bec67cccacb4b66e5c9f5ed1a7a1eb0e6220b8 (patch) | |
| tree | ee37855cdebbb9d95ad6a46281e56be414868cbe | |
| parent | eeeeed6b3d049a979222323a176502a93ca64568 (diff) | |
clarify why foreground FCM usage isn't common
| -rw-r--r-- | static/faq.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/static/faq.html b/static/faq.html index 0444e704..7665432c 100644 --- a/static/faq.html +++ b/static/faq.html @@ -1077,8 +1077,8 @@ notifications when they're in the foreground. Unfortunately, many apps don't implement a service to continue receiving events from their server in the background. On the stock OS, they rely on receiving events through Google - servers via Firebase Cloud Messaging (FCM) in the background, and sometimes - also in the foreground.</p> + servers via Firebase Cloud Messaging (FCM) in the background and sometimes + even in the foreground, although it doesn't have good reliability/latency.</p> <p>Polling is the traditional pull-based approach of checking for new events at an interval. This is badly suited to mobile devices for anything more than |