Introduction
Most automations run from start to finish without asking you anything. That is ideal for silent background tasks, but it is the wrong design when a routine needs your judgement halfway through. Imagine a macro that prepares a message, gathers information, and then waits: should it send now, or should you check the draft first? Or a bedtime routine that dims the lights and then asks whether you are ready for the final wind-down step. In both cases, the macro should pause, show you a clear on-screen prompt, and continue only when you tap it. That pause-and-confirm pattern is what makes automation feel trustworthy instead of pushy.
MacroDroid’s floating text feature, combined with the Floating Text Clicked trigger, gives you exactly that pause point. Floating text is a small piece of text that sits on top of other apps, visible wherever you are on the phone. When you tap it, the Floating Text Clicked trigger fires, and a second macro, or a continuation of your routine, can run. Used together, these two pieces let you build interactive macros: the first macro does the preparation, shows the floating prompt, and stops; you tap when you are ready; the second macro does the rest. This guide explains the whole pattern, including how to avoid the common trap of leaving floating text on screen forever.
The pattern is worth learning because it solves a whole class of problems. Any routine that should not finish without your approval, any multi-stage task where the next stage depends on something only you can see, and any automation you want to run at your own pace rather than on a timer, benefits from a tap-to-continue step. It also gives you a gentle way to introduce automation to someone who is nervous about the phone doing things by itself: nothing completes until they tap, so they always remain in control.
Prerequisites
You need MacroDroid installed with the overlay permission granted, because floating text is drawn over other apps and Android blocks that by default until you allow it. Go to your phone’s settings, find the permission for drawing over other apps, and enable it for MacroDroid. You also need to decide what the floating text should say. Short, verb-like labels work best: Tap to send, Continue setup, or Ready for next step. Avoid long sentences, because floating text is meant to be glanced at, not read like a paragraph. Choose a colour and size that stand out against most backgrounds without obscuring important content, and pick a screen position that does not cover navigation buttons.
Before building, sketch the two halves of your routine on paper or in a note. Half one ends with showing the floating text. Half two begins with the Floating Text Clicked trigger and contains everything that should happen after the tap. Writing this split down first prevents the most common beginner mistake, which is trying to put the pause inside a single macro and wondering why the macro does not wait. MacroDroid macros do not wait indefinitely for a tap inside one run; the clean design is two macros linked by the floating text. Also decide what should happen if you never tap: should the prompt disappear after ten minutes, should it stay until you dismiss it, or should a separate timeout macro clear it? Having an answer before you build saves a later redesign.
Step-by-Step Setup
Start with the first macro, which you might call Prepare and Prompt. Add whatever trigger starts your routine, such as a time trigger, a shortcut, or a location trigger. Then add the preparation actions: gathering information, setting variables, adjusting settings, or drafting content. At the end of the action list, add the Display Floating Text action. Enter your short label, choose the position, size, and colour, and give the floating text an identifier if MacroDroid offers one, because a clear identifier makes it easier to remove exactly that text later. Save and enable this macro.
Now create the second macro, which you might call Continue After Tap. Its trigger is Floating Text Clicked. When you configure it, you will be asked which floating text it should listen for; select the identifier or text you just created, so that tapping other floating text does not accidentally continue this routine. As the first action of this macro, add Remove Floating Text, so the prompt disappears the moment you tap it and does not linger on screen. Then add the remaining actions: sending the prepared message, applying the final settings, or launching the next stage of the routine. This ordering matters. Removing the prompt first gives immediate visual feedback that the tap registered, even if the later actions take a second or two.
Finally, build the safety net. Create a small third macro, or add a timeout branch, that removes the floating text after a sensible period, such as thirty minutes, or when a cancelling event happens, like the screen turning off or a different macro starting. A floating prompt that never disappears becomes visual clutter and teaches you to ignore it, which defeats its purpose. Test the timeout as carefully as the tap itself, because a prompt that vanishes too quickly is just as unhelpful as one that never leaves. Save all three macros, enable them, and keep MacroDroid logging on while you test.
Testing and Verification
Test in three stages. First, run the preparation macro manually from inside MacroDroid and confirm the floating text appears exactly where you expected, with readable text and a sensible size. Move to another app and confirm it stays visible on top, since a prompt that only appears inside MacroDroid is useless for a real routine. Second, tap the floating text and confirm three things happen: the text disappears immediately, the continuation macro runs, and its actions complete. Check the system log for both macros to confirm the sequence and timing. Third, test the timeout path by starting the preparation macro and deliberately not tapping, then waiting for the prompt to clear on its own.
Also test the awkward cases. Tap the prompt twice quickly and confirm the continuation does not run twice in a harmful way; if it could, add a constraint or a variable check that blocks a second run within a few minutes. Lock the screen with the prompt visible, unlock it, and confirm the prompt is still there or has cleared according to your design, rather than being stuck in a strange state. Test with the phone in both portrait and landscape orientation, because a prompt positioned for one orientation can sit awkwardly in the other. If you share the phone with anyone, test while another app is in the foreground, such as a video or a game, to make sure the prompt does not block something important.
Troubleshooting
If the floating text never appears, the cause is almost always the overlay permission. Recheck it in system settings, and remember that some manufacturers add a second toggle for floating windows or picture-in-picture style overlays. If the permission is granted but the text still does not show, check that the preparation macro actually ran by looking at the log; the problem may be the first macro’s trigger, not the floating text action. If the text appears but tapping it does nothing, check that the Floating Text Clicked trigger is listening for the correct identifier. A mismatch between the displayed text and the trigger’s expected text is the most common cause, especially after editing the wording in one macro but not the other.
If the continuation macro runs but the floating text stays on screen, the Remove Floating Text action is either missing or targeting the wrong identifier. Move it to the very top of the continuation macro and verify the identifier matches exactly. If the prompt disappears but the continuation actions do not run, check the continuation macro’s constraints; a time or location constraint carried over from another macro can silently block it. If the prompt appears in the wrong place, adjust its position setting rather than compensating with a larger size, and test again in both orientations. Finally, if floating text survives a reboot or lingers after you delete a macro, remove it manually from MacroDroid’s floating text management screen, if available, or recreate a temporary macro whose only action is to remove that identifier.
Tips for Interactive Macros
Keep the tap prompt honest about what will happen next. Tap to send should send, not open three more confirmations, and Continue setup should continue, not restart the routine from the beginning. If the next step is destructive or hard to undo, say so in the prompt itself, for example Tap to send message, rather than hiding the consequence behind a vague Continue label. Use distinct wording for each floating prompt on your phone, so you never have two prompts visible at once with the same text and no way to tell them apart.
Use this pattern sparingly. A phone covered in floating prompts is worse than no automation at all, because every prompt demands attention. Reserve tap-to-continue for steps that genuinely need judgement, and let purely mechanical steps run silently. Consider pairing the prompt with a notification as a backup: if you miss the floating text, the notification reminds you that a routine is waiting. And always give yourself an easy dismissal route, such as a second floating option labelled Cancel, or a long-press behaviour if your setup supports it, so that waiting routines can be abandoned cleanly without opening MacroDroid.
Frequently Asked Questions
Can a single macro pause and wait for a tap by itself?
No, not reliably. The clean design is two macros: one that shows the floating text and stops, and a second whose trigger is Floating Text Clicked. Trying to force a single macro to wait indefinitely leads to fragile routines that are hard to debug.
Does floating text work over every app?
It works over most apps once the overlay permission is granted, but some secure screens, such as banking apps or lock-screen entry fields, may block overlays. Test your prompt over the apps you actually use during the routine, not just over the home screen.
What happens if I never tap the floating text?
That depends on your design. Without a timeout macro, the text stays until you tap it or remove it manually. Adding a timeout that clears it after a set period keeps your screen tidy and prevents stale prompts from confusing later routines.
Can I have more than one floating prompt at a time?
Yes, but give each one a distinct identifier and distinct wording, and use separate Floating Text Clicked triggers for each. Identical prompts make it impossible to tell which routine you are continuing.
Why does tapping sometimes feel unresponsive?
The tap target is only as large as the text itself, so very small text is hard to tap accurately. Increase the size slightly, add padding if the option exists, and position the prompt away from screen edges where taps are harder to register.


