We want to do the same thing with Play services app compatibility that we did with the web installer.
The work on it hasn't started yet, but expect to be surprised by something that works far better than you could have imagined. I think we finally arrived at the right approach.
Conversation
Replying to
I just hope some brain storming goes on notifications at least as an option. I know your reasons not to support it but I feel at least people should have an option to choose to receive few critical alerts from the apps they rely on.
1
Replying to
Notifications are fully supported on GrapheneOS already:
grapheneos.org/faq#notificati
No progress required on that front. It was always working fine. You're confusing apps only supporting background push via Google's FCM service with GrapheneOS not supporting notification / push.
2
Replying to
Yeah, I meant the same thing. As we are already talking about play services, I thought it would be obvious but I should have specified FCM though.
Yes, it's not your fault if app dev uses FCM but it would be nice to support it if possible whenever you implement PS comparability.
1
Replying to
Our current plan for Play services compatibility is supporting running Play services in a sandbox with zero special privileges (no special SELinux policy, no privileged permissions, no whitelisted capabilities). The plan is implementing compatibility with Play services itself.
1
1
You would be able to install it as a regular app in the profile(s) of your choice. It wouldn't have any integration into the OS. The OS would only provide compatibility shims (no additional access) for the app id to have it working without any special privileges or integration.
i.e. our compatibility layer will be for Play services, not apps running Play services. The full API of Play services would be available and implemented. Features depending on having special access wouldn't work, but the vast majority of it doesn't need that. The OS won't use it.
1