How do you build a tag driven routine on Android?
With an automation application that recognises a particular tag and then runs a series of steps. The mechanism is the same everywhere and the manufacturer layer sitting on top of it is not, which is exactly where two Android phones stop behaving alike.
The shape of it
An automation application holds a rule: when this tag is seen, do these things. The tag itself needs to hold nothing more than something recognisable.
The steps are whatever the application can do, which on Android is a broad set and depends on the permissions you grant.
The tag can be blank of meaning, since the application recognises it rather than reading instructions from it.
That is what makes Android routines quick to build and personal to one phone.
How the tag is identified
Usually by the identifier the chip carries, which is unique and needs nothing written.
Sometimes by content written to the tag, which lets several tags share a meaning and lets you replace a tag without reconfiguring.
Identifying by content is the more durable choice, because a lost or damaged tag can be replaced by writing the same content to a new one.
Identifying by chip identifier means a replacement tag has to be reconfigured, which is a small annoyance that arrives at a bad moment.
The manufacturer layer
Several manufacturers add their own automation system alongside the platform's, with different capabilities and different names.
That is why instructions from one phone frequently do not match another, and why a routine that works for a colleague may have no equivalent on your device.
Battery optimisation is the other manufacturer specific trap. An automation application restricted in the background may stop responding without any visible change.
If a routine works and then quietly stops, battery settings are the first place to look rather than the tag.
Making it reliable
Exempt the automation application from battery restrictions, which is the single change that fixes most intermittent routines.
Keep the automation application allowed to receive tags. From Android 16, the first tag it receives brings a notification offering to stop it, and the NFC basics guide places the list under Settings > Apps > Special app access > Launch via NFC. From Android 17, open the application once after installing it, since tags are not delivered to an app that has never been opened or has been force stopped.
Test with the screen off and the phone locked, since tag dispatch generally needs an awake unlocked device and your routine inherits that.
Identify tags by content where you can, so replacement is a rewrite rather than a reconfiguration.
And write down what the routine does, because in six months you will not remember why tapping the bedside tag turns something off.
Frequently asked questions
Does the tag need content for a routine?
Not necessarily, since an application can recognise the chip identifier. Writing content instead makes replacing a damaged tag easier.
Why does my routine work on a friend's phone and not mine?
Manufacturers add their own automation layers with different capabilities. Instructions from one device often do not transfer.
Why did my routine stop working by itself?
Battery optimisation restricting the automation application in the background is the commonest cause, and it changes nothing visible.
Does it work with the screen off?
Generally not, since tag dispatch usually needs an awake unlocked device. The routine inherits that condition.