# Klick'r (Smart AutoClicker): Android automation that clicks on what it sees > Klick'r is an open-source Android auto clicker from Nain57/Smart-AutoClicker that triggers clicks and swipes on image detection, timers, counters and broadcast receivers. Its image-matching model is what separates it from coordinate-only clickers, and it is also where most of its limits live. **Nain57/Smart-AutoClicker** — An open-source auto clicker on images for Android - Repository: https://github.com/Nain57/Smart-AutoClicker - Stars: 3,637 · Forks: 619 - Language: Kotlin - License: GPL-3.0 - Published: 2026-09-23 · Updated: 2026-09-23 · Language: en - Canonical page: https://hysenlabs.com/projects/nain57-smart-autoclicker ## What Klick'r solves that a coordinate clicker does not A classic Android auto clicker repeats taps at fixed screen coordinates. That works until the target moves: a button shifts after an animation, a dialog appears one frame later, a list scrolls by a variable amount. Klick'r, formerly Smart AutoClicker, is built around image detection instead. The README describes it as "an open-source Android application designed to automate repetitive tasks effortlessly" with "unique image detection capabilities alongside traditional auto-clicking functionalities." In practice that means the trigger is not a position but a picture on screen, and the click follows whatever the app finds. The project names three audiences in its own words: gamers automating in-game actions, testers simulating user interactions, and anyone doing repetitive clicking. The second group is the one most other Android clickers ignore. A tester who wants to reproduce a tap sequence after a layout change gets less value from fixed coordinates than from a template image that survives the change. It also ships a Regular Mode, described as a "straightforward auto-clicking experience" for simpler repetitive tasks. That matters for evaluation: you are not forced into the image pipeline to get basic clicking, and you can decide per task which model you need. ## The trigger and action model behind Klick'r The README lists four trigger types: image detection, timers, counters, and Android broadcast receivers. Image detection is the one that shapes the rest of the design. You supply a reference image, and the app looks for it on screen; when it matches, the associated action runs. Actions are clicks and swipes, and the README says they are configured with "press durations, swipe durations, and positions," so a swipe is defined by its timing as well as its path, not just its endpoints. On top of triggers and actions sit the features the README groups under Advanced Automation: counters operations, Android Intents, and flow control. Counters are what turn a clicker into something closer to a script. A counter can gate how many times an action runs or drive branching, and flow control sequences steps rather than firing them in parallel. Android Intents let a task interact with the rest of the system instead of only the foreground app. Broadcast receivers as triggers mean an external event, not a pixel or a clock, can start a task. The repository layout backs this up at the module level: core/, feature/, smartautoclicker/, build-logic/, and a documentation/ directory sit alongside the Gradle files. This is a multi-module Kotlin project with a separate build-logic module, not a single-activity sample. The README also points to a wiki for questions, which is where the configuration detail lives rather than in the README itself. What the README does not give is the matching algorithm, the threshold semantics, or how detection scales with screen resolution. Those are exactly the parameters that decide whether your task works, and the README is silent on them. Treat the wiki as required reading before you commit to a design. ## Installing Klick'r from F-Droid or Google Play There is no build step required for normal use. The README carries two store badges, one for Google Play under the package id com.buzbuz.smartautoclicker and one for F-Droid at f-droid.org/packages/com.buzbuz.smartautoclicker/. If you want the F-Droid listing through the client, this is the package identifier to search for: ```bash com.buzbuz.smartautoclicker ``` Building from source is a separate path and the README does not document it. What the repository does show is a Gradle wrapper at the root, with gradlew and gradlew.bat, plus settings.gradle.kts and build.gradle.kts. That is enough to say a Gradle build exists, and not enough to say which JDK or Android SDK version it expects, because the README does not state either. For a first real task, the README's own framing is the right starting point: begin in Regular Mode, then move to image detection only when a fixed position stops working. The README describes Regular Mode as "designed for easy configuration and ideal for simpler, repetitive tasks," which is a reasonable definition of a first run. When you do move to image detection, the sequence the README implies is: capture or supply the reference image, attach a click or swipe action to it, set press or swipe duration, then add a trigger condition. The README also mentions interactive game tutorials that walk through automating a game step by step. If you are new to the tool, those tutorials are the closest thing to a guided first use that the README describes. ## Where Klick'r breaks down Image detection is brittle by nature, and Klick'r inherits that. Anything that changes the pixels of your target, a theme, a resolution change, an overlay, a compression artifact, can stop a match. The README does not document a tolerance setting, a confidence threshold, or a multi-scale search, so you cannot know from the README how much variation the matcher absorbs. That is a real gap for anyone planning long-lived automation. The second limitation is app-level blocking. The README links a dedicated release tag, obfuscation-start, with the line "You think an application is blocking Klick'r? Try the obfuscated version." That is an admission that some target apps detect and refuse the standard build. It is also a maintenance fact worth weighing: an obfuscated variant is a second artifact to track, and the README does not say how the two builds stay in sync. Third, this is Android only. The related search data shows people looking for smart autoclicker on PC, Windows, iOS, and macOS, and the README describes an Android application with Play and F-Droid distribution. There is no desktop or iOS build described. If your task is not on Android, Klick'r is the wrong tool and no amount of configuration fixes that. Finally, the README does not document rollback or version migration. Releases have moved quickly, with 4.0.3, 4.0.4 and 4.0.5 all dated within September 2026. Rapid patch releases are a good sign for fixes and a bad sign for configuration stability, and the README says nothing about whether a task saved in one version loads in the next. ## How Klick'r differs from macro recorders and ADB scripting The obvious alternative on Android is a macro recorder that captures your taps and replays them. The difference is in what the recording encodes. A recorder stores coordinates and timing, so it replays exactly what you did and fails exactly when the screen no longer looks the same. Klick'r stores a reference image and matches against it, so it can click a target that has moved. For a game with a consistent button graphic, that is a meaningful difference. For a fixed form in a fixed layout, it is extra work for no gain, and Regular Mode is the better fit. A second alternative is driving the device from a host machine over ADB, scripting input events and reading the screen from outside the app. That approach gives you a real programming environment and version control for your automation, which Klick'r does not offer in the same form. What it costs you is the device: ADB scripting generally assumes a connected host, while Klick'r runs on the phone itself. If you want automation that survives the phone being unplugged, Klick'r's model is the one that fits. Neither alternative is strictly better. The honest comparison is that Klick'r trades the precision of coordinates for tolerance to layout change, and trades a host machine for on-device execution. Whether that trade pays off depends entirely on how much your target moves. ## Licence, maintenance and the cost of upgrading Klick'r is GPL-3.0. For someone installing from Play or F-Droid, that is mostly invisible. For someone modifying the source or shipping a derivative, it is not: GPL-3.0 carries source-disclosure obligations for distributed derivatives, and the repository's LICENSE file is the authoritative text. This is a description of the licence, not legal advice, and the terms are worth reading directly if you plan to redistribute anything. The maintenance picture is current. The repository is not archived, and the last push was on 2026-09-09, with release 4.0.5 tagged the same day. Three releases landed in the first nine days of September 2026. That is an active release cadence, and it also means the upgrade surface is real: if you pin to a version, you are choosing to miss fixes that arrive within days. The upgrade cost that the README does not address is configuration compatibility. Nothing in the README states whether tasks created in 4.0.3 open correctly in 4.0.5, whether counters and flow control survive an upgrade, or how to revert if they do not. Given the release pace, that silence is the largest unquantified risk for anyone building non-trivial automation. Budget for re-verifying your tasks after each upgrade rather than assuming they carry over. ## Conclusion Adopt Klick'r if you are automating an Android app whose buttons move, change size, or appear at unpredictable times, and you are willing to tune detection settings until they hold. Do not adopt it if you need unattended reliability across OS updates or if your target app treats automation as abuse. Before relying on it, verify two things on your own device: that your target image matches at the threshold you set, and that the app you are automating does not block Klick'r, in which case the project points to its obfuscated release. The README does not document rollback or a migration path between versions, so keep your own copy of any configuration you build. ## FAQ ### How do I use Smart AutoClicker (Klick'r)? Install it from Google Play or F-Droid, then start with Regular Mode, which the README describes as designed for easy configuration and simple repetitive tasks. Move to image detection when you need to trigger clicks on a specific element rather than a fixed position, and use the interactive game tutorials if you want a guided walkthrough. ### What is a smart auto clicker? In this project's terms it is an Android auto clicker whose triggers go beyond fixed coordinates. Klick'r supports triggers based on image detection, timers, counters and Android broadcast receivers, and its actions include clicks and swipes with configurable press and swipe durations. ### Is an auto clicker illegal? The README does not address legality, so there is no basis here for an answer. What it does cover is a practical restriction: it links an obfuscated release for cases where an application is blocking Klick'r, which indicates that some target apps actively refuse the standard build. ### What is the most trustworthy autoclicker? That is a judgement the README does not make, and it offers no comparison with other tools. What it does give you is verifiable criteria: the source is open, the licence is GPL-3.0, and the app is distributed through both Google Play and F-Droid. ### Is auto clicker harmful? The README does not discuss harm or safety. It does note that some applications block Klick'r and points to a separate obfuscated release for that case, which suggests the main friction is target-app detection rather than device damage. ## Sources - [Issues](https://github.com/Nain57/Smart-AutoClicker/issues) - [License: GPL-3.0](https://github.com/Nain57/Smart-AutoClicker/blob/master/LICENSE) - [Nain57/Smart-AutoClicker on GitHub](https://github.com/Nain57/Smart-AutoClicker) - [README](https://github.com/Nain57/Smart-AutoClicker/blob/master/README.md) - [Releases](https://github.com/Nain57/Smart-AutoClicker/releases) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/nain57-smart-autoclicker