Macros
Android Macro with Image Detection
A macro is a sequence of steps the device runs for you. With image detection, each step only happens when the screen is the way it should be, which turns a fragile sequence into a routine that holds up on its own.
- Visual builder, no code to write
- Every step has a condition and an action
- AND and OR logic, compound actions and variables
- The same idea on the phone and on the emulator
14-day free trial. Cancel anytime.
What it is
A macro that checks before acting
Macro is the old name for something simple: record a sequence of commands and have it repeat. The best known version on Android is tap recording, which stores where you tapped and at what interval, then plays it back. It works for short tasks on predictable screens.
The problem shows up when the screen stops being predictable. A load takes longer than usual, a notice appears halfway through, an item enters the list. The recording keeps running the whole sequence, into thin air, because it has no way of knowing something changed.
A macro with image detection fixes that by inverting the logic: every step carries a condition. Instead of "tap here after three seconds", the step says "when this button is on screen, tap it". The automation waits for the right state instead of betting on the clock.
Anatomy
How a macro is built
There is no scripting language and no text editor. You build the sequence in a list of steps and configure each one in a form.
- 01
Capture the screen
With the app or game open, you capture the screen inside the builder. Targets are cropped from that image, at the real resolution of the device or instance.
- 02
Crop the target
Select the button, the icon or the area that matters. That crop becomes the target the automation will look for. A target can also be text written on screen, or a color.
- 03
Set the condition
State what must be true for the step to run: the target is visible, it is not, it appears a number of times, the color matches. Conditions can be combined.
- 04
Pick the action
Tap, tap the image found, swipe, tap on text, press a system button, switch automations. The step joins the sequence, which runs in a loop.
Available blocks
The builder vocabulary
Actions are what the automation does. Conditions are what it checks first. The catalog is nearly the same in both apps: EmuloAgent adds emulator control, which only makes sense when the emulator is driven from outside.
Actions
Gesture
Device
Passwords
Flow
Custom
EmuloAgent only
Conditions
Detection
Context
Logic
What separates a sequence from an automation
Steps in a queue solve short tasks. What sustains a long routine is the ability to decide.
Combined conditions
A step can require several conditions at once, or accept any of them. Groups can be nested, which covers decisions like "if this is the screen and the button is active, or if the notice appeared".
Compound Action
A block that groups several actions under the same condition, where each inner action can still have its own. It is how you write a whole routine in a single step, and blocks can be nested.
Checking for absence
Waiting for something to disappear is as common as waiting for it to appear: the end of a load, a notice closing, leaving a screen.
Variables
They hold state between steps, as text, number or true and false. They are used to count repetitions, mark a stage as done or change the course of the flow.
Counting on screen
A condition can compare how many times the same image appears against a number, which lets you decide by quantity and not only by presence.
Switching automations
A macro can call another one and hand over control, or stop one that is running. Large routines get split into smaller parts, each with its own responsibility.
What it is for
What a macro with detection solves
It is not about clicking fast. It is about not having to be present to make obvious decisions.
The daily repetition
That sequence of open, collect, confirm and close that you do the same way every time. It is predictable work, and predictable is exactly what can be automated.
The waiting
A good share of the time in games and apps is spent waiting for something to finish. An image condition covers that with no guessing at timing: the next step only happens once the expected state shows up.
The lapse in attention
Long manual sequences fail from distraction. An automation that checks before acting does not skip a stage or hit the wrong button by accident.
The routine that runs alone
With conditions covering the predictable detours, an automation can loop for hours, handling what comes up along the way instead of breaking at the first surprise.
The scale
The same routine applied to several accounts or instances. Written once, replicated as many times as the machine allows.
The screen that defends itself
Keypads with shuffled digits exist to stop blind automation. Locating each key before tapping is what makes it possible to get through them without relying on position.
No coding
Why you do not need to know how to program
Automation is usually associated with scripting, and scripting is intimidating for good reason: it means learning a syntax before solving the problem. Here the path is different. You do not write what the automation should do, you assemble it.
The assembly happens over the real screen. You capture, crop what matters and pick from a list what to do. The concepts that would normally require code, condition, repetition, grouping and variable, show up as form fields and checkboxes.
That does not mean giving up capability. The same constructs that would be tedious in a script, such as a compound condition or a reused block, are still available, just filled in rather than typed.
- No syntax
- No quotes, semicolons or indentation. A poorly filled step shows up as an empty field, not as an error in the middle of a run.
- Targets come from the screen
- You do not describe the button, you crop the button. The target is the very image that appeared on your device.
- Test before trusting
- You can check a single step in isolation and see whether the target is found, before leaving the routine running on its own.
- Start on the simulator
- There is a controlled test app to practice with image, text, color and keypad targets, without risking it on a real application.
Questions
Frequently asked questions
Do I need to know how to program to create a macro?
No. The macro is built in a list of steps, and each step is configured in a form. Targets are cropped from the screen itself. There is no scripting language to learn.
How is this different from recording my taps?
A recording plays back positions and intervals, without checking anything. A macro with detection checks, before each step, whether the screen is in the expected state. In practice, the recording breaks when something goes off script, and the macro waits or takes another path.
Can the macro handle surprises?
Within what you anticipated. A notice that shows up now and then can become a condition that closes it, and a slow load is solved by waiting for the element to appear. What was not anticipated stays a surprise, and that is what the stop and notify actions are for.
Can I use the same macro on the phone and on the emulator?
Both apps use the same block vocabulary, but each keeps its own automations, and crops are calibrated for the resolution they were made at. In practice, you rebuild the targets in the new environment reusing the same step structure.
How many macros can I have?
Locally there is no limit: building, editing and saving are free. What varies by plan is the quota of automations stored in the cloud, which starts at 20 and reaches 200.
Can I share a macro with someone else?
Yes, on the plans that allow it. Sharing is done with a single-use code, and whoever receives it redeems the automation into their own account.
Keep reading
Other pages that go deeper on topics related to this one.
Auto Clicker with Image Recognition
How detection by image, text and color works under the hood.
Image Auto Clicker for Android Phones and Tablets
Automation inside your own phone or tablet, with no PC and no root.
Image Auto Clicker for Android Emulators
Driving BlueStacks, MuMu, LDPlayer, Nox and MEmu from Windows, in parallel.
Turn repetition into an automatic routine
Create your free account and build your first macro during the 14-day trial.
14-day free trial. Cancel anytime.