Fenix: Fennec migration: push subscriptions

Created on 12 Sep 2019  ·  6Comments  ·  Source: mozilla-mobile/fenix

Either carry them over, or re-register anything pertinent. We're currently lacking WebPush support in Fenix, so that's a thorn we need to deal with somehow.

E8 Migration P2

Most helpful comment

@grigoryk @jonalmeida @st3fan @vesta0 - Lina added a pretty detailed comment regarding the complexity involved in migrating the push notifications here: https://github.com/mozilla/application-services/issues/2048#issuecomment-572798531

We may want to consider passing on this and letting the users start fresh and resubscribe. It could potentially turn out to be a boost to our retention???

image
ref: http://info.localytics.com/blog/push-notification-survey-2018

All 6 comments

re-register anything pertinent.

We should consider that when we migrate push subscriptions. We notify the consumers that the subscription has changed.

It seems, from offline conversations, that FxA servers are capable of handling the registration renewals.

However, we will also have push subscriptions from web content (e.g. facebook, reddit, etc.) where we would be re-registering (autopush), and notifying all those sites via GeckoView that the push subscription changed (onpushsubscriptionchange).

Which would mean fennec users x number of webpush subscriptions would all go through the AutoPush servers and the site's servers. This could end up DDOS-ing our and their servers.

What would be nice, is if we could bulk import the Fennec subscriptions (which are written to disk that we can read from), and validate them on device with the minimal amount of subscription changes that are needed (PushManager.verifyConnection()?).

We're currently lacking WebPush support in Fenix, so that's a thorn we need to deal with somehow.

WebPush support is landing soon™ (before migration takes place), so this should be a valid concern.

@jonalmeida is https://github.com/mozilla/application-services/issues/2048 a dependency for this bug?

@jonalmeida is mozilla/application-services#2048 a dependency for this bug?

@st3fan Yes, this is the a-c equivalent for the a-s work.

@grigoryk @jonalmeida @st3fan @vesta0 - Lina added a pretty detailed comment regarding the complexity involved in migrating the push notifications here: https://github.com/mozilla/application-services/issues/2048#issuecomment-572798531

We may want to consider passing on this and letting the users start fresh and resubscribe. It could potentially turn out to be a boost to our retention???

image
ref: http://info.localytics.com/blog/push-notification-survey-2018

Closing this as WONTFIX. Added a note to our board to validate that re-subscription happens.

This was closed as WONTFIX, so I will move it to Done. Thanks!

Was this page helpful?
0 / 5 - 0 ratings