From fad14f606360dd053c07c9229d7d86d5e2bc1fa3 Mon Sep 17 00:00:00 2001 From: Daniel Micay Date: Fri, 12 Nov 2021 11:31:01 -0500 Subject: [PATCH] simplify wording --- static/usage.html | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/static/usage.html b/static/usage.html index f40aa18c..5885b969 100644 --- a/static/usage.html +++ b/static/usage.html @@ -790,14 +790,14 @@ app sandbox. It also isn't used as a backend for the OS services as it would be elsewhere since GrapheneOS doesn't use Play services even when it's installed.

-

Since the Play services apps are simply regular apps on GrapheneOS, they get - installed by the user within a specific user or work profile and are only - available within that profile. Only apps within the same profile can use it and - they need to explicitly choose to use it. It works the same way as any other app - and has no special capabilities. As with any other app, it can't access data of - other apps and requires explicit user consent to gain access to profile data or - the standard permissions. Apps within the same profile can communicate with mutual - consent and it's no different for sandboxed Play services.

+

Since the Play services apps are simply regular apps on GrapheneOS, you install + them within a specific user or work profile and they're only available within that + profile. Only apps within the same profile can use it and they need to explicitly + choose to use it. It works the same way as any other app and has no special + capabilities. As with any other app, it can't access data of other apps and + requires explicit user consent to gain access to profile data or the standard + permissions. Apps within the same profile can communicate with mutual consent and + it's no different for sandboxed Play services.

The core functionality and APIs are almost entirely supported already since GrapheneOS largely only has to coerce these apps into continuing to run without