Shizuku lets your app use system APIs directly.

Forget about root shell, you can use APIs with higher privileges "directly". Also, Shizuku is significantly faster than shell.

## Background

When developing apps that requires root, the most common method is to run some commands in the su shell. This method has very big disadvantages:

1. **Extremely slow** (Multiple process creation)

2. Needs to process texts (**Super unreliable**)

3. The possibility is limited to available commands

4. Even if ADB has sufficient permissions, the app requires root privileges to run

Shizuku uses a completely different way.

## How does Shizuku work?

Shizuku guides users to run a process, Shizuku server, with root or ADB first. When the app starts, the `binder` to Shizuku server will also be sent to the app.

The most important feature Shizuku provides is something like be a middle man to receive requests from the app, sent them to the system server, and send back the results. So, we reached our goal, to use system APIs with higher permission. And to the app, it is almost identical to the use of system APIs directly.

## For apps that only need ADB permission

If your "root required app" only needs adb permission, you can easily expand the audience by using Shizuku.

## Notes for developers

Shizuku has detailed documentation to guide users. Only you need to do is to let the users install Shizuku.

ADB has limited permissions and different on various system versions. Before calling the API, you can use `ShizukuService#getUid` to check if Shizuku is running user ADB, or use `ShizukuService#checkPermission` to check if the server has sufficient permissions.

As of Android 9, the usage of the hidden APIs is limited for normal apps.