Visible, camera-readable and easy to explain; static or resolver-based depending on the programme.
Start a project NFC or QR?
Start with the use case.
QR and NFC are access technologies. The right choice depends on interaction, material, data architecture, security and lifecycle.
Tap interaction with an identifier stored in an IC; performance must be engineered around metal and construction.
Using both can add accessibility and resilience, provided both resolve to one controlled identity model.
Choose the carrier after defining the service.
A technology list is not an architecture. Interaction and assurance must be designed together.
Camera scan, tap or both.
Metal, antenna geometry, stack and reading distance.
Model, batch or item-level destination.
Static access, controlled resolver or cryptographic verification.
NFC does not automatically mean secure.
Standard NFC identifiers and cryptographic ICs provide different assurance levels. Security also depends on provisioning, key management and backend verification.
A physical identity programme begins with the product, its service journey and the evidence it must carry.
Discuss a project