From 18fe537b0cb2fe172cdea27cee36494401e96dc3 Mon Sep 17 00:00:00 2001
From: fria <138676274+friadev@users.noreply.github.com>
Date: Fri, 26 Sep 2025 23:42:34 -0500
Subject: [PATCH] add google play services

---
 blog/posts/ios-vs-android.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/blog/posts/ios-vs-android.md b/blog/posts/ios-vs-android.md
index 8cf28722..95625481 100644
--- a/blog/posts/ios-vs-android.md
+++ b/blog/posts/ios-vs-android.md
@@ -173,3 +173,5 @@ GrapheneOS greatly expands on the permissions AOSP offers, giving highly granula
 GrapheneOS also implements a user-facing Network permission allowing apps to individually be granted network access.
 
 You would think with examples of these features already being implemented on *their own platform*, AOSP would go ahead and add them, but that doesn't seem to be the case. I'd like to see Android implement equivalent versions of these permissions to what GrapheneOS offers, the research and development work has already been done on how they should work, they just need to copy it.
+
+The stock OS you get on your phone suffers from a similar problem as iOS in that Google Play Services are [highly privileged](https://developers.google.com/android/guides/permissions#:~:text=Google%20Play%20services%20automatically%20obtains%20all%20permissions%20it%20needs%20to%20support%20its%20APIs.) in the system. GrapheneOS's [Sandboxed Google Play Services](https://grapheneos.org/features#sandboxed-google-play) provides to option to install it inside the standard app sandbox, preventing it from having any access outside what a normal app would have. This is a massive boost in security and privacy and is how Google Play Services should operate by default.