An agent with a phone in its hand.

Three moves, on a loop.

An accessibility tree is just text, so an agent can read it. Every element comes back indexed, with its label, its class and the point to tap. The whole method is three moves repeated — and the third one is why it holds up.

[ 12] Marketplace            TextView    C
[ 13] Selling                TextView    C
[ 14] Create new listing     TextView    C
[ 15] Your listings          TextView    C
[ 16] Search                 ImageButton C

$ adbdrv tap "Create new listing"
tapped 540,1180  (TextView 'Create new listing')

Your phone, your machines.

Nothing to buy from anyone else and nothing to sign up for. You bring the phone and a computer; both are already yours.

What it will not do.

Worth reading before you buy, because these do not change with effort — they are how Android and the platforms work.

• Secure windows stay invisibleBanking apps, password managers and payment sheets have no accessibility tree, by design. Those tasks stay manual, and that is the feature.
• The phone has to be awakeA sleeping screen has nothing to read. The agent can wake and unlock it, but a locked phone shows it nothing.
• Driving the phone uses itUnless you use the hidden virtual display — Android 14 or newer with scrcpy 3 or newer — the phone's own screen shows exactly what the agent is doing.
• No app stays automatable foreverIt reads whatever is on screen, so when an app moves its buttons the recipes need updating. The mechanics are the durable part, not the button positions.
• Platforms watch for automationThe bundled skill's caps, human pacing, varied wording and approval gate exist for that reason. They are not optional extras.
• It is not a bypassSame app, same account, same IP, doing what a person would do — which is why it is the safe way round.

Source access, $4.99 once.