NFC tags

An NFC tag triggers nothing by itself. It holds a few dozen bytes, and the only format both phone platforms read without an app is a link. The phone opens it, and the server acts: that is what lets you add a gesture without anyone having to update their phone.

⚠️ What is written is a public code, never a secret: a tag reads at four centimetres without your consent and copies for pennies. Identity comes from elsewhere, and that is what separates the three doors: the Android app, with the paired device's token; the browser, with the session already open; and the signed NTAG 424 DNA chip, which signs every read and works for a person with no account. Every gesture runs with the bearer's rights, never more.

The gestures shipped: open the record, take out and return equipment, book a room, record attendance, start a timer, walk a round of points in order, report a problem that opens a pre-filled ticket. A tag can ask a question before acting, or offer a menu.

It can also ask for a checklist: compliant or not, a measured value with its range, a choice, a note. This month's fire extinguisher, the fire door, the padlock. The record is immutable once written, the anomaly is followed through to its correction, and the register comes out as a PDF with the regulation's section at the top.

With no network, the tap is kept with its time and goes out when the signal returns, checklist included. A QR code printed beside it does the same work for a phone without NFC. Signed chips are prepared from the app, but the company key never goes down into a phone.

Comparable to A patrol-tour reader and its software, replaced by a one-dollar tag and the phone you already have

bf_nfc · Version 18.0.2.6.4 · Guide chapter · View the source · See it in the catalogue