@Lokki Indeed... easy-peasy, lol :-)
Totally understand... Appreciate your feedback, and look forward to more idea sharing.
Thanks... would be happy to share some ideas with Chris. I appreciate it!
Yes, I was thinking of the ring body. I don't know the name of this specific material, and it may be more of a coating than anything... but it has that "silky smooth plastic" feel (looks like the material from the outer piece of this). I would bevel the edges of this ring, and if it didn't add too much cost, finish off the bevel in a darker tone than the face of the ring (for added contrast). Depending on color, you could make the ring blend in (flesh tone), or stand out (aqua blue) and draw some attention.
I'm Jason... good to meet you :)
My thought it is... market it as an affordable, sportier line of rings. Have someone else, like me, take it to market it under a different brand name. I'm guessing this idea is nothing new, but I think that if you paired this design, with the functionality I mentioned here, you would have something that a lot of people would spend $10 or $20 for. In fact, if the delivered cost-of-goods was low enough, maybe you could afford to discount to early adopters, to really ignite the sales.
I also have some fairly cool ideas for how to sell it.
Do you have any part of your team based in the US? I'd be very interested in chatting more.
@johnyma22 Have you considered using a flexible, durable elastomer material similar to what's used in many fitness trackers? I'm a designer/marketer (with a touch of developer), that's envisioning a new/unique product line. Would love to chat more and share my ideas. New to the forums/NFC ring, but I'm guessing you're the founder?
Hey @Lokki, thanks for the reply and explanation!
Yeah, that makes sense... encrypt the passwords within the application (held locally/securely on the device).
Exactly my thoughts... instead of scanning a fingerprint, the Ring is "scanned". Disabling this remotely (shutting down the ring, so to speak) would be a great security feature. I've been wanting to develop this for a few years now, but never had a good way to wrap an NFC tag around my finger (until discovering this!)
In my opinion, a wearable authenticator is a much better idea than a fingerprint (something you have vs. something you "are"). And a non-powered ring is the perfect implementation (also, biased). With my knowledge of existing fingerprint scanners, they are limited to very specific authentication points... i.e. iPhone: access on the lock-screen. But what about the numerous websites and other native apps that require passwords? Sure, a native app can integrate the fingerprint scan, but how seamless is that? There will still be other points of access for that native app that will rely on a password.
This idea bridges the divide between accessible password alternative -and- passwords themselves. I had hoped to eradicate the world of passwords when I developed Passtouch, but yeah, not going to happen. I've since swallowed the pill of "stuck with passwords", but there is still a way to use them, without using them.
Hoping to find some support for the idea here... and maybe someone that would like to help prototype develop the app. I'm certainly ready to stop typing and start tapping.
New to the forum, so maybe I've missed mention of this... But, I would like to build an app that allows the Ring to authenticate the "release" of the appropriate (app/website specific) password. I don't know how data is stored and encrypted on the ring, but if possible, passwords could be stored on the ring and transferred into the app/sites active password field via some method of key press emulation (taking over the active, on-screen keyboard).
I think the magic here, would be activating key presses somehow, so that the active app essentially receives the password as if the user had pressed each key in succession.
This would solve one of the main problems with password use on mobile devices: 1) Hard to type longer/secure passcodes on teeny-tiny keyboards (and generally, it just sucks trying to remember 50 different passwords). It would also create an essentially universal & fairly frictionless password manager. Right now, every mobile password manager requires a complex master passcode. Well, that's just as annoying as typing my other longer passwords. And even the password managers that step in with their own keyboards, trying to fill-in the password for you (with copy-paste) still require use of the master code and additional taps to initiate the "fill"... just more friction for the user... who simply wants to get signed in quickly and securely.
Frictionless: Banking app sign-in screen, tap password field, tap ring -- signed in.