TypingDNA Authentication API - Secure users by their typing behavior with free low-code API

@aleksandr_serdiuk Thank you Alex, it's great to see your encouragement, you're doing quite amazing stuff too.

@shane_lowe1 Great question! The technology needs a bit more text than just a word. The "same text" version works well with anything around 20-40 chars (e.g. email address+password). In the particular case of 30 chars, in our tests we were able to reach absolute 0% FAR in approx. 10,000, but that comes with some FRR (false reject). It also depends on how many previous samples one submits, the technology works even with just one or two, but starts shining at minimum of 3. In essence we can say the technology is comparable with face recognition based on regular camera (even better because regular camera based face recognition tech can be easily hacked). On mobile devices however, we're able to reach similar accuracy with about half the amount of text because we're also looking at telemetry data (device movement while the user is typing).

@raulpopa @hellobrent thanks! I appreciate your support. We're preparing to launch something very interesting in a few weeks again. Stay tuned!

@anant_garg Hey! We have recorders/SDK's for the web (JS), Java/Android/iOS/React Native as well as a Node client for server-side communication with our API's. They're all open source and up on our GitHub, let me know if you have any questions -- or have an additional platform in mind you think we should consider! It's important to us that we are present wherever people are typing, so be on the lookout for more platforms in the future. Side note: Very impressive product you've built with cometchat. You clearly are familiar with the struggle of abstracting complexity to simplify things for the user :) And kudos on the API docs!

@ashishrzk We certainly agree with your assessment over here! Thanks for checking us out.

@kyle_hunt1 @raulpopa

@essaygirlsdaily Hey Laura -- we chose to implement the API management features you listed ourselves. That is not to say everything was written from scratch, of course -- libraries are leveraged where it makes sense (Chart.js for the dashboard visualizations). The decision to not rely on a core API management service/provider is simply that it wasn't needed -- our team had a specific set of well understood requirements, and a preference to spend our time developing the right solution rather than configuring an off-the-shelf product to fit our needs (inevitably changing our requirements to fit the constraints of the service along the way). That said, we're always re-assessing the tech we use and aren't dogmatic about it -- if a feature on the API side were best addressed by a 3rd party service in the future, it would be considered. I hope that answers your question, it seems like a popular topic -- perhaps we should write a blog post in the future on our behind-the-scenes tech. Thanks

@ramiessaid, how would you describe the steps of the demo?

@brian_fritton Always happy to see such feedback. Is there anything you don't like about it? Or something you'd change about the demos, functionality, etc?