Visual automation
Android image matching automation
Image matching helps ScriptTap react to visible buttons, icons, status graphics, and selected screen regions when text or Accessibility data is not enough.
What it does
A script can look for a saved visual target or pixel condition on the visible screen, then continue, stop, tap, or branch based on what it finds.
How ScriptTap handles it
Image and pixel checks work from visible screen content. Screen capture is separate from Accessibility and follows the user-controlled Android capture flow. Selected areas and saved assets matter because tighter targets are faster and less fragile than broad full-screen searches.
Good uses
- Wait for a known icon or button state before tapping.
- Check whether a small visual indicator changed color.
- Use a selected area when an app does not expose useful UI element text.
Limits
Visual automation can be fragile when animations move, themes change, fonts scale, assets are cropped poorly, or timing changes. Use small areas, current assets, and explicit waits where possible.
Privacy and safety
Image matching reads visible screen content only after the user has granted screen capture for that session. It is not a hidden capture channel. See the Privacy Policy for current screen-capture disclosure.
Mini-workflow example
Capture a small "ready" button image, limit matching to the lower part of the app, wait until that button appears, then tap the saved target point and continue only after the next screen is visible.