screen_objects
screen_objects is a Python extension for Android UI automation. It finds saved image samples on
the current device screen, then checks, taps, swipes, counts, and calibrates those screen objects
through ADB.
It is implemented in Rust with PyO3 and built with maturin.
Requirements
- Python 3.8 or newer
- Rust nightly, as configured in
rust-toolchain.toml - maturin
- Android Debug Bridge (
adb) - An Android device or emulator with USB or wireless debugging enabled
Install
For local development:
pip install maturin
maturin develop
To build a wheel:
maturin build --release
Quick start
Put reference images in an objects directory. Each filename stem becomes an object name.
assets/
objects/
start_button.png
close_icon.png
Configure the device before performing any device operation, then load the objects:
from pathlib import Path
from screen_objects import Direction, SwipeSpeed, device_config, get_objects
device_config(serial="emulator-5554")
objects = get_objects(Path("assets/objects"))
if objects["start_button"].tap(timeout=10.0):
objects["close_icon"].swipe(Direction.Left, SwipeSpeed.Normal, duration=0.4)
device_config() uses adb from PATH by default. Pass the executable path when necessary:
device_config(Path("/path/to/adb"), serial="192.168.1.20:5555")
Use the serial shown by adb devices when more than one device is connected.
Samples and calibration
get_objects(path) loads every image below path and returns a dictionary of ScreenObject
instances. Image stems must be unique, including across subdirectories. The function creates or
updates objects.json next to the objects directory to store calibration data.
By default, an object is searched for anywhere on the screen. Calibrating it can improve matching:
objects["start_button"].calibrate()
Calibrate while the object is visible. This records a matching tolerance and continues to search
the whole screen. Use fixed=True when the object always occupies the same screen position:
objects["close_icon"].calibrate(fixed=True)
Regions
Regions constrain object matching to part of the screen. Store their reference images separately, calibrate the region first, then load objects with the same regions directory:
from screen_objects import get_regions
regions_dir = Path("assets/regions")
objects_dir = Path("assets/objects")
regions = get_regions(regions_dir)
regions["main_panel"].calibrate()
objects = get_objects(objects_dir, regions_dir)
objects["reward_badge"].calibrate(region="main_panel")
Region data is saved as regions.json beside the regions directory. Call get_regions() before
get_objects() when an application needs both collections.
Matching and actions
Lookups use a cached screenshot. Actions that change the device through this module clear that
cache. If the screen changes outside this module, call reset_screen() before the next lookup.
timeout is measured in seconds. The default, 0.0, performs an immediate lookup. A positive
value waits for a match until the timeout expires.
index selects a specific match and is zero-based: index=0 selects the first match. It can be
used with exists(), tap(), swipe(), and calibrate(). Objects calibrated with
fixed=True have one known position, so they do not support index, count(), or
tap_each().
# Check for a match for up to five seconds.
if objects["reward_badge"].exists(timeout=5.0):
# Tap the second match three times, waiting 0.2 seconds between taps.
objects["reward_badge"].tap(index=1, times=3, interval=0.2)
# Tap every match in the current screenshot and receive the number tapped.
tapped = objects["collect_button"].tap_each()
Required actions
Every lookup or action that can return False has a force_* form. It raises RuntimeError and
saves the current screenshot to screen-<device-serial>.png when no match is found.
objects["start_button"].force_tap(timeout=10.0)
objects["close_icon"].force_exists()
API reference
Object loading
get_objects(objects_dir: Path, regions_dir: Path | None = None) -> dict[str, ScreenObject]
get_regions(regions_dir: Path) -> dict[str, ScreenRegion]
ScreenObject
exists(timeout: float = 0.0, index: int | None = None) -> bool
force_exists(timeout: float = 0.0, index: int | None = None) -> None
tap(
timeout: float = 0.0,
index: int | None = None,
times: int = 1,
interval: float = 0.0,
) -> bool
force_tap(
timeout: float = 0.0,
index: int | None = None,
times: int = 1,
interval: float = 0.0,
) -> None
swipe(
dir: Direction,
speed: SwipeSpeed,
duration: float,
index: int | None = None,
) -> bool
force_swipe(
dir: Direction,
speed: SwipeSpeed,
duration: float,
index: int | None = None,
) -> None
count() -> int
tap_each() -> int
calibrate(
fixed: bool = False,
region: str | None = None,
index: int | None = None,
) -> None
tap() returns False if the object is not found before timeout. times must be at least one;
interval is the delay between repeated taps. swipe() begins at the matched point and returns
False when there is no match. count() returns the number of current matches, and
tap_each() returns the number of taps sent.
Device functions
device_config(
adb: Path = Path("adb"),
serial: str | None = None,
app: str | None = None,
) -> None
start_app() -> None
close_app() -> None
reset_screen() -> None
screenshot() -> None
tap_center() -> None
swipe_center(dir: Direction, speed: SwipeSpeed, duration: float) -> None
back() -> None
home() -> None
write(text: str) -> None
Pass app to device_config() to select an Android package by name. start_app() launches it,
and close_app() force-stops it.
screenshot() saves the cached or newly captured screen to screen-<device-serial>.png.
tap_center(), swipe_center(), back(), and home() send their respective device action.
write() enters text into the focused Android field. Call reset_screen() after an external or
text-entry action when a fresh lookup is needed.
Enums
Direction.Left
Direction.Right
Direction.Up
Direction.Down
SwipeSpeed.Slow
SwipeSpeed.Normal
SwipeSpeed.Fast
SwipeSpeed.Turbo
Development
Run Rust tests with:
cargo test
Build the extension into the active Python environment with:
maturin develop
Metadata
Release files for screen-objects 6.0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| screen_objects-6.0.1-cp314-cp314-win_amd64.whl | CPython 3.14 | CPython 3.14 | Windows x86-64 | Details |
Release files / screen_objects-6.0.1-cp314-cp314-win_amd64.whl
| Download URL | screen_objects-6.0.1-cp314-cp314-win_amd64.whl |
|---|---|
| Size | 415.7 kB |
| Tags | CPython 3.14 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
55f30b4a75f105275dfa6a85051c2e622918b72d36006044e9a10e1499b05756
|
|
BLAKE2b-256 checksum How to use checksums |
c6c7e261ee2c50bb7ca4c424199eb49991950f56ce7069496be2545f96bf33a4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logSecurity for screen-objects 6.0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 1 file in this release has been uploaded with provenance metadata.
Attestation for screen_objects-6.0.1-cp314-cp314-win_amd64.whl
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.