Bugzilla

Thank you for writing this up :markh!

I'll come back with some more thought-out analysis, but I wanted to briefly note a couple of other considerations.
-  Apple has support for background push notifications (I believe is newish, as there are some notes in and around firefox-ios that imply that **all** push notifications require UI. However, [background push notifications get throttled, and Apple recommends limiting to two or three per hour](https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/pushing_background_updates_to_your_app). That said, I'm sure there is a way we work with the limitation, given that our use case only adds value to the user if the app is foregrounded anyways (I doubt we'll be too sad if a user didn't get their synced tabs when the app was backgrounded!). We will however want to make sure we carefully navigate the limitations so we don't get flagged by Apple.

- Another infrastructure to think about is the FxA infrastructure. In order to send commands, we have to interact with FxA, which in-turn will forward the messages to push. We could possibly skip the FxA step, maybe we can have clients send messages to auto-push directly? This naively sounds OK, as I believe we don't want to persist and poll the push messages (since there will be so many of them!)

Thank you for writing this up :markh!

I'll come back with some more thought-out analysis, but I wanted to briefly note a couple of other considerations.
-  Apple has support for background push notifications. I believe is newish, as there are some notes in and around firefox-ios that imply that **all** push notifications require UI. However, [background push notifications get throttled, and Apple recommends limiting to two or three per hour](https://developer.apple.com/documentation/usernotifications/setting_up_a_remote_notification_server/pushing_background_updates_to_your_app). That said, I'm sure there is a way we work with the limitation, given that our use case only adds value to the user if the app is foregrounded anyways. I doubt we'll be too sad if a user didn't get their synced tabs when the app was backgrounded. We will however want to make sure we carefully navigate the limitations so we don't get flagged by Apple.

- Another infrastructure to think about is the FxA infrastructure. In order to send commands, we have to interact with FxA, which in-turn will forward the messages to push. We could possibly skip the FxA step, maybe we can have clients send messages to auto-push directly? This naively sounds OK, as I believe we don't want to persist and poll the push messages (since there will be so many of them!)