Visual automation
Android image matching automation
Image matching helps ScriptTap react to visible buttons, icons, status graphics, and selected screen regions by using captured pixel evidence.
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 to recognize pixel-based visual states.
Reliable visual matching
Use tight areas, current assets, clear contrast, and explicit waits to keep visual matches stable across animation, theme, font-scale, crop, and timing changes.
Privacy and safety
Image matching reads visible screen content after the user grants screen capture for that session. Capture remains user-controlled and follows the current Privacy Policy 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.