Feature shape
App Manager
App Manager should help advanced users understand what is installed without making risky package actions feel casual. Public wording keeps destructive or root-assisted actions behind app gates, backups, and support evidence.
Installed apps, package names, version context, labels, icons, APK source notes, and update state for troubleshooting.
Activities, services, receivers, providers, permissions, and exported state help users understand app structure.
Export or share workflows should keep ownership, storage, and sensitive-app limits visible.
Disable, uninstall, freeze, or system-level actions belong behind explicit warnings and recovery guidance.
| Best use | Troubleshoot app identity, collect package evidence for support, inspect app components, and understand what a package exposes. |
|---|---|
| Do not promise | Do not present App Manager as a universal debloater, malware remover, or root package editor for every device. |
| Play-safe language | File access, installed-app visibility, and package actions must be explained by user benefit and kept behind consent. |
| Support evidence | Package name, version, device/build, action attempted, and screenshots should travel together. |
| Admin boundary | Remote feature gates and risky action availability remain admin-controlled in Mission Control. |
User workflow
How this utility should feel in the app
A CRYA utility should be useful, explicit about risk, and connected to support evidence when something fails.
Search by app label or package name.
Review version, permissions, components, and exported state.
Use read-only details first; only use risky actions when you understand the result.
Keep recovery options before root/system package changes.
Send package evidence if support or app review needs it.
Related CRYA surfaces
Continue safely
Utility pages connect users to Toolkit workflows, docs, policies, and support without exposing protected admin controls.