Your phone can run automations too — start with these

Desktop automation gets all the attention, but the phone is where the repetitive actions actually happen — it is the device you pick up eighty times a day. Both major mobile platforms now ship capable automation tools, and almost nobody uses them.

Start with these

• Arrival and departure routines. Location triggers that switch settings when you get to work or home — silence notifications, connect to the right audio device, open the app you always open. Free, invisible, and immediately noticeable.
• Charging as a trigger. Plugging in at night is a reliable daily event, so hang the nightly things on it: alarm confirmation, do-not-disturb, backup, tomorrow's calendar on screen.
• One-tap messages. A shortcut that texts a specific person a specific thing — running late, on my way, landed. Replaces roughly thirty seconds of typing with one tap, several times a week.
• Photo to document. Scan, crop, convert to PDF and file to the right cloud folder in a single action. This is the automation that ends the habit of photographing receipts and never dealing with them.
• Focus timer with a shutdown. Starts a timer, silences everything, and reverses all of it automatically when the timer ends. The reversal is the part manual focus modes always forget.
• Battery-level actions. Below twenty per cent, drop brightness, disable background refresh and turn on low-power mode without being asked.

The traps

Permission prompts kill automations. An automation that asks for confirmation every time it runs is slower than doing the thing manually. Check whether your platform allows the specific trigger to run without confirmation before building anything around it, because some categories always prompt.

Location triggers are battery-expensive and imprecise. They fire on a radius, not a doorstep, so expect them to trigger early and occasionally not at all. Use them for things where a false positive is harmless.

Long chains break silently. A twelve-step automation that fails at step four leaves you in a half-configured state that is worse than not running it. Keep chains to three or four steps and build several small ones instead of one large one.

What not to automate on a phone

Anything involving money, anything sending a message to someone other than a fixed recipient, and anything you would not want happening while the phone is in a pocket. Mobile automations run in contexts you cannot predict, which is exactly why the low-stakes, high-frequency ones are where all the value is.

Build one this week. Charging trigger, two actions, no more. If it survives seven days without annoying you, build the next one.

Measuring whether it was worth it

An automation is worth keeping if it runs more often than you think about it. That sounds glib, but it is the only test that matters on a phone — anything you have to remember to trigger has failed, because the whole value proposition was removing the remembering. Check after a fortnight: if it has fired thirty times and you have not thought about it once, it is working. If you have adjusted it four times, delete it.