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.
So I presume for a novice user like myself, the app support of the should outweigh any potential missed features of the xNT.
For context, I want to use an implant for access to my vehicle and some custom hidden storage safes and so these will likely be custom arduino projects anyway. The main reason for wanting to wait for the Apex is for the security features, as my understanding is it would be possible to read the UID from the xNT and use this to create a cloned card (more likely to smash the window but hey ho).
Yeah I was considering this but because of the quarantine rules in the UK it would be difficult to get one implanted at the moment anyway. It sounds like the Apex isn’t far away so I think it would be worth the wait.
FYI, this is a very good reference page on the DT website ( Check out the whole page ) Videos and the product matrix ( Bear in mind the Matrix is not currently fully upto date but there is a great deal of information contained within chip-implants-101