> I don't know if there are any other APIs besides Push which follow that same pattern. According to microg.org, the main components are Google's push notifica

> I don't know if there are any other APIs besides Push which follow that same pattern. According to microg.org, the main components are Google's push notification API, the Google Maps API (embedding maps in apps), and Unified Network Location Provider (WiFI/cellular tower based location, provides fast initial loaction). The maps API replaces Google maps with mapbox, so no requests are sent to Google (?). MicroG uses Google for push and they need a device ID, but it is not connected to an account (and can be disabled). Network location does not use Google's services but instead use local location modules (e.g. from F-Droid). One of the default ones uses Mozilla's database of WiFi & cellular tower. So if I didn't miss anything the only component that Google can deactivate is Push. For apps like WhatsApp & Signal that's not a big problem as they are able to use WebSockets for push instead. Other Apps won't push which is inconvenient, e.g. Stem wouldn't push the 2FA code, so I'd have to open the app manually. But that is something I'll worry about if Google actually shuts push down. Over the last 2 or so years I watched unifiedpush.org and they make steady progress. They define how push components work together and now there are multiple push (hosted and self-hostable) "providers". Anyway, Element Android will support it & FluffyChat has support already (Matrix clients).