hi everyone, we are looking at incorporating NDEF capability into ChipVault. While we’re at it, wanted to ask the community for specific features that you want to see in the app.
please reply and post your feedback here - where we will be tracking communities’ requests.
I was away when the Android version was released.
When I get home, I will grab a couple of TEST CARDS and will get some testing done.
I already have an idea I want to try, and if its not there, I will put a request through
Forcing me to sign up / login to provide feedback.
Writing should be centre justified
When I try to enroll a card, it detects it, BUT it overlays all my other NFC apps
I had to screen record because the app blocks screenshots
Forcing biometrics, and does not give another option to unlock.
I dont have biometrics enrolled so Unfortunately I can’t do anymore testing sorry.
It actually ties into one of my questions for unlock.
Rather than Biometrics or Password, could we scan another card for authentication?
Samsung Galaxy S25 Ultra
One Ul version 8.5
Android version 16
I hope this helps
The security options seem to be controlled by the app and removed from the user.
This gives me Apple vibes.
It is one of the reasons I dont like Apple.
Suggestion.
Maybe here, you give the user the option of the security level THEY are comfortable with
replying to your 3rd scenario:
thanks for the sharing the feedback - we are looking into these.
Can you clarify what you mean by “Maybe here, you give the user the option of the security level THEY are comfortable with” - What options are you suggesting we give? We cannot not have a CMP gate. A CMP is provided by the use and is the master key.
Help me understand better of what you’re suggesting here so we can explore options.
replying to your 2nd scenario:
We are looking into enabling a fallback pin-code option in-lieu of an active biometric. Stay tuned…
replying to your 1st scenario:
we are looking into this and will come back w/ an update. Please stay tuned,
I haven’t watched the video yet. I should do that before making any comments because you might have covered it off in the video.
And I couldn’t get any further in my testing, so I don’t actually know what the limitations are just yet.
However what i’m suggesting is, something similar to the YubiKey model, where NFC can be used as an option to unlock the app.
The core security rules don’t change—the user still sets up a strong Master Password initially to protect the vault.
However, once that setup is complete, the user should get to decide how they unlock it day-to-day—whether that’s re-entering their full password, using biometrics, or tapping an NFC device (like a physical card or implant) rather than forced into a single method.
Again, I haven’t watched the video and I’ll do that shortly so apologies, if it’s already been covered in there
Thread 1 (NFC overlay) — FIXED & submitted for approval: reader mode is now held through the result screen, so Android’s “Choose an action” app-chooser no longer pops over a detected card. Verified on device.
thanks for submitting the bug
Thread 2 (forced biometrics) — FIXED & submitted for approval: unlock now falls back to your device PIN/pattern when no fingerprint/face is enrolled, ending the lockout. Verified on device.
thanks for submitting the suggestion
Really appreciate this, and I hear you on the Apple vibes — that’s the opposite of what ChipVault is meant to be.
A clarifying verbiage will land in the latest build and submission because of exactly this.
A “Why these requirements?” toggle on that screen: your Master Password isn’t a login in front of the encryption — it is the key. No server, no recovery, so its strength is literally your cards’ strength. The minimums are a floor for that reason, not paternalism; above it, how strong you go is your call. And unlock is no longer biometric-only — no fingerprint/face, no problem, you use your device PIN or pattern.
In complete transparency:
I won’t let the password drop below what I’d honestly call secure — with no recovery, that strands people. But a configurable posture above that line is what we’re looking at next, and I’d value your feedback. This is a tool for people who want control of their own hardware resident security and data — that’s the point - your data secured, on your card, in your pocket.
look forward to hearing from you.
love it - and it’s a natural place to land, since ChipVault already lives on NFC hardware. You’ve captured it right: the Master Password stays the root of trust, and how you unlock becomes your choice. We just took the first step on that axis — the next update (pending google’s review/approval), lets you unlock with PIN or biometric, your pick.
An NFC security-token unlock — YubiKey, card, or implant — is the next step on that same axis, and it’s on the roadmap. I want to be transparent about why it’s a larger and heavier-lift feature and not a quick toggle: unlike biometric/fingerprint or PIN, the OS gives us no built-in “unlock with a tapped token” primitive; consequently, doing it securely means building the token handshake ourselves.
We have it logged as a planned feature for future major release.
Sincerely thank you for the feature request
ChipVault 1.1.4 build 9 has been released in Google Play with these above detailed fixes.
Thanks
N0AGI
2 things
The erase/ wipe does not work
The other NFC apps still pop up afterwards
