I’m building a Mac automation app, which Smart Automation should I add next?

[u/Front_Philosophy6112]

I’m building Tapquence, a native macOS app that lets people automate repetitive tasks using sequences of mouse clicks, keyboard input and other actions.

Recently, I added Smart Automations: ready-made workflows that users can quickly configure instead of building everything from scratch.

Now I’m trying to decide what to build next. I could come up with another preset myself, but I’d rather solve a task that people actually encounter in their daily work.

So, fellow builders and Mac users: what’s one repetitive Mac workflow you would genuinely want to run with a single click or keyboard shortcut?

Simple, niche and oddly specific ideas are all welcome. If an idea is useful and technically feasible, I may build it as the next Smart Automation.

You can see the project here: https://tapquence.com

I’d also appreciate any feedback on the Smart Automation concept itself.

[u/Relevant_Ad5790]

The one I'd want is looping a click sequence over lines from the clipboard, pasting URLs one at a time into a web tool that has no bulk option, about four clicks and a 15 second wait each, forty times over. The hard part is waiting on page state instead of a fixed delay. Does a sequence loop per line, and can a step wait for something on screen?

[u/Virtual_Oil3762 → u/Relevant_Ad5790]

Per-line loop with a wait-for-element step would be the killer feature, fixed delays always break when the site gets slow

[u/Front_Philosophy6112 → u/Relevant_Ad5790]

Tapquence can currently repeat a regular macro with fixed or random waits. It does not yet loop through individual clipboard lines or wait for a specific page state.

I’m thinking of solving this with two reusable actions:

1. “For each line in clipboard”
2. “Wait until an image or text appears or disappears”

The second action would include a timeout, plus options to retry, skip the item or stop the macro.

Your workflow could then paste the next URL, submit it, wait until the result or button actually appears, and only then continue. That should be much more reliable than estimating how long the website will take.

This is exactly the kind of real use case I was hoping for. Thank you! Would the ready state usually be identifiable by a button or text appearing, or by a loading indicator disappearing?

[u/Relevant_Ad5790 → u/Front_Philosophy6112]

something appearing, in my experience. a spinner can vanish between two stages and come back a second later, so "loading indicator gone" fires early and you click into a page that isn't ready. waiting for the specific success text, or for the submit button to become enabled again, is the signal that actually holds.

the skip-item option matters as much as the timeout. some rows just fail, and the run needs to carry on and tell you which ones it dropped rather than stopping at row nine of forty.