Android Question Do you think the NXP TapLinx API has any "better" functions compared to the NFC library for B4A?

Mr.Marc

Member
Licensed User
I have not tried the NXP TapLinx API https://inspire.nxp.com/mifare/index.html because I have not been able to find a good and easy to understand android app development environment to run the API from.

I wonder if TapLinx can be run from within B4A and what value the NXP code could possibly provide?

I recently bought a couple of very cool passive (they do not require a battery) NFC wristbands from roxtron https://www.roxtron.com/rw27-wristband with MIFARE DESFire EV2 8K chips for 3 USD per wristbands. My understanding is that the Desfire EV2 8K chips are the best passive NFC chips with the largest amount of memory (8K) that exists to day.

That's why I started to use B2A (just yesterday) because I want to develop an android app for my wristbands. Since I want to integrate payment for the cryptocurrency xrp from ripple https://ripple.com/xrp/ encryption will be important for my app.

Since I don't really have any previous development experience except for Maple and VBA I am curious what the best way is to encrypt the payment code?

Since there is no way to authorize a payment on these passive NFC wristbands I want users of the android app to be able add NFC wearables that they own in the app and to generate encryption keys for the section of code that executes the xrp payment. The user should also be able to send such encryption key to other people that uses the app and that they trust and want to make a payment to. Other people then then simply decrypts the code and makes the payment by tapping an android phone with the app installed against the wristband.

Since this wristbands also will contain public V-cards I cant just encrypt all the code. I just want to encrypt the payment section of code and the section of code that opens a NFC door look.

Any input from any senior B4A developers with experience on the things I have raised in this post?
 

Mr.Marc

Member
Licensed User
I think I have discovered why there appears to be so little development being done with passive NFC NXP chips wearables. Because the greedy and evil payment card company Gemalto own part of the company that controls the official development environment for these chips https://www.mifare4mobile.org/. The API (NXP Taplink) on the other hand appears to be open access.
 
Upvote 0
Top