Launching today

Phone Operator - Auto Clicker

Launching today

Precise Android taps, swipes, and reusable scripts

8 followers

Precise Android taps, swipes, and reusable scripts

8 followers

Visit website

Automate repetitive Android touch workflows without root. Phone Operator combines precise taps, double taps, four-direction swipes, per-action delays, visible random ranges, loop limits, and reusable mixed-action scripts. A movable, transparent floating controller stays available across supported apps. Free mode provides unlimited single-point clicking; lifetime Pro unlocks multi-action scripts and sharing. AccessibilityService is used only for gestures configured and started by the user.

Phone Operator - Auto Clicker gallery image

Free Options

Launch tags:Android

Launch Team

Framer AI AgentsDesign and publish professional sites with AI

Promoted

Maker

📌

Hi Product Hunt, I built Phone Operator after seeing how repetitive touch tasks create fatigue and how many auto-clickers hide timing or gesture behavior behind confusing controls. The hardest part was not dispatching a tap; it was making each action visible, independently configurable, and predictable across Android devices. The result supports taps, double taps, directional swipes, per-step delays, loops, random tap ranges, and mixed reusable scripts. The floating controller can be moved and made more transparent, so users can still see the underlying app. AccessibilityService is used only to execute gestures the user configures and starts. The app does not read passwords or collect screen content through that service, and it includes device-specific permission guidance. I would especially value feedback on script editing, visual action markers, and Samsung, Xiaomi, and Huawei compatibility.

Report

6d ago

Forum Threads

p/phone-operator-auto-clicker

•

3d ago

How should Android automation apps explain AccessibilityService?

Android touch automation needs AccessibilityService to dispatch user-configured gestures, but the system warning is necessarily broad.

For Phone Operator, I currently show a disclosure before opening Android settings, explain what the service does and does not do, require the user to start every run, keep a visible stop controller and foreground notification, and provide a direct path to disable the service. Scripts stay on the device unless the user explicitly shares one.

I am trying to balance meaningful consent with an onboarding flow that does not overwhelm first-time users. For Android users and developers, which signals matter most before you would grant this access: no screen-content collection, local-only scripts, a visible stop control, a short test mode, or something else?

I will use the feedback to improve the permission guide and onboarding.

p/phone-operator-auto-clicker

•

6d ago

What makes Android touch automation predictable across devices?

Building an Android auto-clicker taught me that dispatching a gesture is the easy part. The harder problem is making every action understandable and predictable for the user.

For Phone Operator, I have been using four design rules:

1. The marker must show the real action. A tap marker should display the configured random radius, while a swipe marker should show direction and distance without moving during execution.

2. Every step needs independent settings. Timing, delay, repeat count, random range, and swipe distance should belong to the individual action instead of a global template.

View all

Android touch automation needs AccessibilityService to dispatch user-configured gestures, but the system warning is necessarily broad.

I will use the feedback to improve the permission guide and onboarding.