No-root automation
No-root Android automation
ScriptTap is built for phone-side automation without rooting the device, without using su, and without making a desktop companion part of the normal runtime workflow.
What it does
ScriptTap lets a user create scripts that tap, swipe, wait, read visible state, use variables, and react to conditions on the Android device. The automation stays in the user-created script and is controlled from ScriptTap's floating controls.
How ScriptTap handles it
ScriptTap uses supported Android permission flows. Accessibility is required for the floating control layer and for user-authored tap and swipe automation. Screen capture is separate and user-controlled when a script needs image, pixel, OCR, or screenshot evidence.
ScriptTap runs without root or su, and its normal script runtime operates directly on the Android device without a runtime ADB dependency.
Good uses
- Repeated setup flows that need taps, waits, and visible checks.
- Personal phone workflows where the visible screen is the practical signal.
- Black-box reproduction steps when a coded test harness is not available.
Android-supported operation
ScriptTap works inside Android's user-granted permission boundaries. Accessibility, screen capture, and exposed UI or visual signals provide the automation inputs, and scripts can be adjusted when a target app changes its layout.
Privacy and safety
User scripts run locally on the device unless the user chooses a feature such as private cloud sync, feedback, or user-directed AI export. Review ScriptTap's Privacy Policy for current data and permission details.
Mini-workflow example
Create a script that opens a repeated form, waits for a visible ready state, taps the next field, types a saved local value, and stops if the expected text is not visible.