69 karma · joined September 2, 2019
This is exactly why I use e2ee in my app. I sleep better knowing that the keys to the castle are not solely in my hands, but rather with each user. They will always have a say in how their data is used because they ultimately control access.
People should also look for end-to-end encryption tools as they can provide some protections immediately.
The tap cards do not have a QR code printed on them because I create an access key dynamically when you activate the tap card.
As for adding info to the phone contacts, this is a tricky situation. Right now, I do not sync the contact info from received cards into the contacts on the phone. This is because the contacts on the phone are a shared resource that other apps can access, and I don't want people's contact info to leak. I do support caller identification, so you will see a person's name rather than just a number when they call for all of the numbers on your received cards. But, this isn't as robust of an experience as having all the info in the phone's contacts.
For sharing with others who don't have the app, the link you send lets them see your card's contact information on the neucards' website which they can act on. So, for example, I typically share my phone number, linked in profile, twitter handle, etc. and that works faster for me than just giving someone my number and texting them the rest. Also, by using card types, you can set up multiple cards (Professional, Personal, Friends, Minimal, etc.) and then have more control over what info you share initially.
I'm very much hoping to add Android and making neucards as universal as possible. Open sourcing would definitely help with that, but I'm taking a wait and see approach. The physical nfc tags were just added and if people embrace them, then it would make that approach more viable.
https://developer.apple.com/documentation/security/complying...