RPA
Also called: robotic process automation, mobile automation
RPA (robotic process automation) is software that performs interface actions the way a person would — tapping, typing, scrolling and waiting — rather than calling an API. On mobile it drives real apps through their real screens, which is the only option when no public API exists.
Where an API exists, use it: it is faster, more reliable, and does not break when a layout changes. RPA is what you reach for when there is no API, or when the API deliberately excludes the actions you need. Most consumer mobile apps fall into that category, which is why automation on phones is overwhelmingly interface-driven.
How it works on a device
The automation locates elements on screen — by accessibility identifier, by position, or by image matching — then issues input events through ADB or an accessibility service. A script is a sequence of those actions with waits between them, plus handling for the states that interrupt a flow: a permission dialog, a rate-limit screen, a feed that loaded slowly.
What separates workable RPA from brittle RPA
- Variable timing — fixed delays produce identical traces across every device running the same script.
- State handling — a script that assumes the happy path breaks on the first unexpected dialog.
- Per-device variation — the same routine should not execute identically on two hundred phones at once.
- Failure visibility — knowing which device stopped, and why, before the whole fleet drifts.
The timing point is the one that decides whether automation is worth running at all. Perfectly regular intervals are the clearest signal a fleet can emit, and they cost nothing to detect.