split out section for disabling user apps

This commit is contained in:
Daniel Micay 2022-05-09 13:52:43 -04:00
parent 7f36bb2634
commit 18cd6dd0a4

View File

@ -88,6 +88,8 @@
<li>
<a href="#grapheneos">GrapheneOS</a>
<ul>
<li><a href="#user-installed-apps-can-be-disabled">User installed apps
can be disabled</a></li>
<li><a href="#broad-carrier-support">Broad carrier support without invasive carrier access</a></li>
<li><a href="#private-screenshots">Private screenshots</a></li>
</ul>
@ -312,13 +314,20 @@
flexible release cycle / process prioritizing security.</li>
<li>Added toggle for the Owner user to disallow secondary users from
installing apps based on the standard device management capability.</li>
<li>User installed apps can be disabled as you can do with system apps to
fully prevent them from running without losing their data or having the
inconvenience of needing to uninstall and reinstall them. An app that's force
stopped can't start itself but can be started by other apps while a disabled
app is completely disabled.</li>
</ul>
<section id="user-installed-apps-can-be-disabled">
<h3><a href="#user-installed-apps-can-be-disabled">User installed apps can be disabled</a></h3>
<p>GrapheneOS adds support for disabling user installed apps instead of only
being able to disable system apps. This allows users to completely prevent one
of the apps they've installed from being able to run without being forced to
uninstall it and lose their app data. This is much stricter than the standard
force stop feature which only prevents an app from starting itself and the app
will start running again as soon as another app tries to open an activity or
service it provides.</p>
</section>
<section id="broad-carrier-support">
<h3><a href="#broad-carrier-support">Broad carrier support without invasive carrier access</a></h3>