dm on Nostr: npub1w0h29…ruwua Sure, but isn't that battery cost amortized across all the apps ...

npub1w0h29g47254sgmjuaza0qj6cmvwd6qs9rffjyt34a4xs37rfu0sskruwua (npub1w0h…uwua) Sure, but isn't that battery cost amortized across all the apps that use FCM? In comparison, if your app brings its own independent push notification connection, that's one more connection and one more background process--with the associated CPU and radio wake-ups, etc. Right?

Put differently: if users already have FCM messaging enabled, they will notice ~zero marginal battery impact from adding one more FCM client, but they will notice a significant marginal impact from adding a new, non-FCM service.

What am I missing here?