Why does the iPhone show a banner instead of opening the link?
Because a tag is not consent. Anyone can place a tag anywhere, so the notification puts a deliberate step between an object you brushed past and something happening on your phone. It is a design decision rather than a delay to be worked around.
Why a step exists
A tag can be placed by anyone, anywhere, at no cost. A poster in a station, a sticker on a bin, a card left on a table.
Acting on one without asking means an object in the world can send a phone somewhere with no decision from its owner. The notification restores that decision.
Read that way, the banner is not an obstacle. It is the platform declining to treat proximity as intent.
What it costs a deployment
An extra tap, and the proportion of people who do not take it.
Some visitors will see a notification and ignore it, particularly if nothing told them to expect one. That loss is real and it is worth designing against rather than lamenting.
It also makes the experience feel slower than the same tag on Android 16 or earlier, which matters when both are demonstrated side by side to a client. From Android 17, an Android phone asks first too when the tag holds a web link.
Setting the expectation in advance, on the tag itself, recovers most of it.
The contrast with Android
Up to Android 16, Android acts on the tag directly, with no confirmation, and the action is immediate and unasked. From Android 17, the Android NFC basics guide says a tag holding a web link first shows an open link notification, and the link opens only when the user acts on it.
Neither behaviour is broken. They are different judgements about the same trade off between convenience and consent.
For anyone building a deployment, the practical consequence is that the same tag delivers different experiences on an iPhone, on Android 17 and on earlier Android versions, and a demonstration on one does not represent the others.
Show a client both, early. It is easier than explaining afterwards why iPhone users see an extra step.
Working with it
Make the destination obvious in the notification. It names where the tag leads, so a short readable address inspires more taps than a long opaque one.
Use a domain that means something to the visitor. A recognisable name in a notification is the difference between a tap and a dismissal.
Say what will happen on the tag itself, in a few words, so the notification confirms an expectation rather than raising a question.
And measure success as the outcome rather than the read. A tag that is read and whose notification is dismissed has not worked, and only watching real people reveals that.
Frequently asked questions
Can I skip the banner?
No. It is a deliberate step in the background path, and there is no setting or content that bypasses it.
Does it appear when reading through an app?
The application path has its own interaction managed by the system. The banner is specific to the background path.
Does Android show one too?
For a web link, from Android 17: the tag shows an open link notification, and the link opens only when the user acts on it. Earlier Android versions act on the tag directly.
Does a shorter URL help?
It helps the notification read clearly, and a recognisable domain matters more than length. People tap what they recognise.