Biometric Standards
-
I asked a question in the Hardware & Devices group, thought I'll throw it in here as well: We are thinking of some Biometric integration into our app, and there seems to be some effort around standardization, does anyone have any first hand experience with an "open" API to biometrics? I would hate to have to code for each vendor etc... (Our app will probably be a public app, so we won't know which device to target...)
____________________________________________________________ Be brave little warrior, be VERY brave
-
I asked a question in the Hardware & Devices group, thought I'll throw it in here as well: We are thinking of some Biometric integration into our app, and there seems to be some effort around standardization, does anyone have any first hand experience with an "open" API to biometrics? I would hate to have to code for each vendor etc... (Our app will probably be a public app, so we won't know which device to target...)
____________________________________________________________ Be brave little warrior, be VERY brave
Adriaan Davel wrote:
I would hate to have to code for each vendor
HA! That's what I make a living doing! I don't know anything about the biometrics field but I can speak about the facility protection market. No vendors share APIs, this forces customers to buy their hardware and software if they want to use their products. The problems start when you want to mix and match products from different vendors that all have their own command and control software. None of them communicate with each other because every company is trying to push their own software solution. This introduces the need for integration solutions. The key to building one is to have an extremely flexible adapter layer so that new adapters can be added quickly. The goal of each adapter is to translate the data from a particular device into a common format that the rest of the application can understand so that it can remain vendor and device agnostic.
:badger:
-
Adriaan Davel wrote:
I would hate to have to code for each vendor
HA! That's what I make a living doing! I don't know anything about the biometrics field but I can speak about the facility protection market. No vendors share APIs, this forces customers to buy their hardware and software if they want to use their products. The problems start when you want to mix and match products from different vendors that all have their own command and control software. None of them communicate with each other because every company is trying to push their own software solution. This introduces the need for integration solutions. The key to building one is to have an extremely flexible adapter layer so that new adapters can be added quickly. The goal of each adapter is to translate the data from a particular device into a common format that the rest of the application can understand so that it can remain vendor and device agnostic.
:badger:
Hi Jimmanuel, Thanks for the response that I was not hoping for :) The problem I have is that being a public website it's almost impossible to know which drivers to load as I would have to know which biometrics the person has linked... It's starting to sound like I'm going to have to exclude biometrics...
____________________________________________________________ Be brave little warrior, be VERY brave
-
Hi Jimmanuel, Thanks for the response that I was not hoping for :) The problem I have is that being a public website it's almost impossible to know which drivers to load as I would have to know which biometrics the person has linked... It's starting to sound like I'm going to have to exclude biometrics...
____________________________________________________________ Be brave little warrior, be VERY brave
With a properly designed plugin architecture you could ask the user what they have plugged in and then load the proper driver. Another possibility would be to try to connect to a device using all of the interfaces that you've developed; if they've linked to one that you support then one connection attempt will succeed and then you know what they have :)
:badger:
-
With a properly designed plugin architecture you could ask the user what they have plugged in and then load the proper driver. Another possibility would be to try to connect to a device using all of the interfaces that you've developed; if they've linked to one that you support then one connection attempt will succeed and then you know what they have :)
:badger:
I'm thinking of having an "Identify" button (that will loop through my know drivers etc), and a drop down to select from. Asking users is normally quite a pain as you have to give them instructions on how to figure out on all the different operating systems etc (target market is the less technically skilled public :)) Thanks for the inputs
____________________________________________________________ Be brave little warrior, be VERY brave