🎨 User Interface

The main user interface of Package Manager presents a simple yet elegant list view of applications, showing each application's icon, name, and package ID. Each item also includes an icon to open the application (if available). Long-pressing an item initiates batch processing by enabling a checkbox, instead of using the "open" icon on the right side. (More details are provided later in this article.)

Screenshot of the main UI of Package Manager

Other than the main title (app name), the top portion of the application includes three buttons:

1. Search – Search and categorize applications by name or package ID.
2. Sort – Sort applications by name, package ID, size, or installation/update date. This option also allows reversing the application list order.
3. Reload – Reload the entire application list.

The bottom navigation bar provides quick access to Exported Apps, Uninstalled Apps (requires Root or Shizuku), and the Settings menu.

Screenshot of the App Info page of Package Manager

Upon clicking an individual item in the app list, Package Manager opens a new page with several scrollable tabs (depending on the selected application). The first tab displays essential information about the selected application, including:

1. Version – Current version of the app
2. Package ID – The unique application identifier, resembling a Java package name (e.g., com.example.app). This ID uniquely identifies the application on the device and in app stores.
3. APK Path – The directory where the APK file(s) of the selected application are installed
4. Data Directory – The directory containing the app’s data files
5. Native Library – Directory storing the required native libraries for the app
6. Installation Dates – Dates when the application was first installed and last updated
7. Certificate – Details about the app’s signing certificate

In addition, this page provides several action buttons (some visible only on Root or Shizuku-supported devices), including:

1. Open – Launch the selected application
2. Explore – Extract and browse the contents of the selected APK. Users can inspect resources and other important files that determine the app’s behavior. It is also possible to export resources (e.g., app icon) to device storage with a few clicks
3. Disable/Enable – Disable an enabled app or enable a disabled app (Root or Shizuku-dependent feature)
4. Uninstall – Uninstall applications, including system apps with root or Shizuku permissions. On non-rooted/Shizuku supported devices, only user apps can be removed. Guidance is provided to remove system apps on non-rooted devices/Shizuku via ADB
5. App Info – Open the native Android settings page for the selected app
6. Google Play – Open the app’s page on Google Play (works only if the app is published there)
7. Export – Export individual APK files or app bundles to device storage. Exported files can also be shared via third-party apps
8. Reset – Reset the selected app’s data folder (root or Shizuku-dependent feature)

Screenshot of the Split APKs page of Package Manager

The second tab is applicable only for split APKs or app bundles. It displays a complete list of individual APKs with an option to export them individually or as a batch to device storage. This feature is especially useful as Google now encourages developers to distribute apps as bundles rather than single APKs. Users can selectively back up only the necessary APK files instead of the entire bundle. Additionally, it is possible to install app bundles or split APKs using Package Manager (more details are provided later in this article).

Screenshot of the Permissions page of Package Manager

The next tab (Permissions) appears for any app that declares at least one permission in its manifest file. Package Manager lists both "Granted" and "Denied" permissions for the selected application. This feature provides an easy way to review the permissions each app has, which is important for privacy and security.

Screenshot of the Operations page of Package Manager

The Operations (AppOps) page offers near-complete control over various operations handled by an application. Note that modifying some operations may affect the normal functioning of the app. For example, disabling the "Camera" operation for an app that uses camera hardware will permanently block its access. These features should be used only if the user fully understands the consequences. Some operations may also be unchangeable.

Screenshot of the Activity page of Package Manager

The next tab displays all the enabled activities related to the selected application.

Screenshot of the Manifest page of Package Manager

The final tab displays the manifest file (AndroidManifest.xml) of the selected application.