What can the NExT do that the VivoKey Apex cannot?

sorry nope… not correct.

The thing that the Apex cannot do is be an NTAG216 chip. When you ask “what can chip A do that chip B cannot”, that includes the entire scope of all possibilities… including applications that specifically look for the NTAG216 chip, either by profiling the memory structure of the chip it’s talking to, or issuing the ADPU command GET_VERSION:

Nowhere is this more infuriating than 3rd party devices… the marketing for the device might talk about supporting “ISO14443A” tags, but in reality they only support a very specific subset of devices within that specification because of the unique command sets or memory structures involved, none of which have to do with any of the ISO14443A standard or its parts.

5 Likes