2024-01-14 06:07 PM - edited 2024-01-14 06:08 PM
Hi,
I have a use case where I need to read and write to an NFC tag. The read and write operation will always be done by an MCU (via st25R) and not by any other device (eg:- android device).
Should I use the NDEF format for the data in this case ? What is the advantage of using NDEF ?
Solved! Go to Solution.
2024-01-15 12:42 AM
Hi Luke_abc,
The main advantage of NDEF is interoperability by giving semantic to the data. Android and Apple iPhones will read nowadays NDEF messages automatically. Android phones will know how to interpret most of the data contained in NDEF. iPhone will automatically open a few types of NDEF messages.
If you are using only one type of tag and only some proprietary data then probably no need to use NDEF, just make sure that your data is not by mistake interpreted as NDEF.
If you are using various different tags then it may become interesting to at least NFC Forum capability containers and maybe put proprietary TLVs into the NDEF file or use some mime-types. This helps you to manage different memory layouts, memory access etc. for most memory tags.
I hope this gives you some ideas what to consider.
BR, Ulysses
2024-01-15 12:40 AM
Hi,
NDEF (NFC Data Exchange Format) is a standardized message format used by NFC (Near Field Communication) devices to exchange data. The advantage of using NDEF over writing raw data on a tag is that NDEF provides a standardized way of formatting and organizing data, making it easier for different devices to read and interpret the data on the tag.
For the use case you have described, I believe there is not real advantage of using NDEF.
Rgds
BT
2024-01-15 12:42 AM
Hi Luke_abc,
The main advantage of NDEF is interoperability by giving semantic to the data. Android and Apple iPhones will read nowadays NDEF messages automatically. Android phones will know how to interpret most of the data contained in NDEF. iPhone will automatically open a few types of NDEF messages.
If you are using only one type of tag and only some proprietary data then probably no need to use NDEF, just make sure that your data is not by mistake interpreted as NDEF.
If you are using various different tags then it may become interesting to at least NFC Forum capability containers and maybe put proprietary TLVs into the NDEF file or use some mime-types. This helps you to manage different memory layouts, memory access etc. for most memory tags.
I hope this gives you some ideas what to consider.
BR, Ulysses
2024-01-16 08:15 AM
Thanks @Ulysses HERNIOSUS and @Brian TIDAL