Why Should You Avoid a Low Level Fingerprint SDK?
Some fingerprint SDK or finger vein SDK providers claim to offer a toolkit for the rapid
integration of a client/server fingerprint software or finger vein software system through ActiveX
and COM components. DON'T BE FOOLED. These fingerprint SDK toolkits still require the
development of a robust fingerprint reader software matching server as well as a deep
understanding of other vital elements such as exception handling and system optimization
(see Fingerprint SDK / Finger Vein SDK Comparison tab below).
Additionally, all low level fingerprint SDKs or finger vein SDKs ultimately require you to
tightly embed the fingerprint software within your application, which creates an immediate
disadvantage. When modifications or enhancements are made to either the host application or to the
fingerprint SDK / finger vein SDK, the host software must be recompiled with the fingerprint SDK
/ finger vein SDK, setting the stage for significant challenges with ongoing support and
maintenance.
|
Category |
Fingerprint/Finger Vein S D K |
Bio-Plugin™ |
|
Product Structure |
DLLs; building blocks to develop a system |
Complete system already developed, including high-
performance Fingerprint/Finger Vein identification engine |
|
Development Time |
8-12 months |
Less than 24 hours |
|
System Dependencies |
Host software always dependent on Fingerprint/Finger Vein
SDK DLLs. Need to
constantly recompile code. |
No system dependencies |
Documentation |
May not include needed information for some development
environments |
M2SYS supports a variety
of development environments and can provide sample code. Examples include: C++, VB,
.NET, Delphi, PowerBuilder, Java, Clarion, and web applications. |
|
Support |
Minimal vendor support, you are responsible for
developing and supporting the system on an ongoing basis. |
Dedicated M2SYS engineer involvement to ensure
successful completion of integration. Proactive ongoing support and
system enhancements provided automatically. |
|
Focus |
Commitment to developing, maintaining, and supporting
the Fingerprint/Finger Vein system will distract from concentration on your core product |
Remain focused on your core competencies |
Still not convinced? Consider the following challenges you will face with
a Fingervein SDK that can significantly hamper development
resources and prolong time to market:
|
Fingerprint/Finger Vein SDK |
Bio-Plugin™ |
|
Understanding the parameters involved with
Fingervein comparison, how they work, why they are significant, and how data needs to
be extracted from an image |
No knowledge required |
|
Data type mapping, database management, data synchronization,
exception handling |
No knowledge required |
|
System optimization to perform 1:N comparison for large
databases. Opening a record set from the database and matching one-by-one will not produce
fast results. |
High performance Fingerprint/Finger Vein server performs multi-threaded,
memory-based search for every request |
|
Handling poor image quality, bad image acquisition,
and unpredictable user input |
System already designed to address these issues |
|
Releasing a new version of your core software as you fix bugs
in your Fingerprint/Finger Vein module will lead to a serious version management problem and excessive
regression testing burden. |
Although appearing to your end users as having a seamlessly integrated
Fingerprint/Finger Vein module, your core software is completely separate. You can
independently release new versions of Bio-Plugin™ and your application.
|
Investing time and resources in constantly resolving
software defects and optimizing system performance to stabilize the Fingerprint/Finger Vein
module |
System has been continually optimized for the last
5 years.
M2SYS has learned from many different installations in various industry verticals
how to optimize and stabilize Bio-Plugin™ to handle any unpredictable situation. |
|