Overview

Working with the Barcode SDK

The Vuzix M400 and M4000 includes a barcode scanning engine that supports the most common symbiology’s.

• QR

• EAN (8 & 13)

• UPC (A & E)

• Data Matrix

• Code 39

• Code 93

• Code 128

• Codabar

• ITF

• MaxiCode

• RSS-14

• RSS-Expanded

Developers may leverage this barcode engine in their own applications via the Vuzix Barcode SDK. Using the built-in engine provides a common experience with other applications on the device and ensures a consistent high performance.

There are three possible mechanisms to integrate the built-in barcode engine into your application. Each mechanism has the same features for interpreting and filtering barcodes but different integration details.

• Scanning via Intent - By far the easiest mechanism is to send an intent to open the built-in scanning user-interface. You will receive a result with the barcode contents. This only requires a few lines of code, and there is no option to customize the user experience of this approach.

• Embedding a Barcode Scanner in your app - If the default user experience associated with using the Intent does not meet your needs, you can easily insert a scanner fragment into your application. This allows you to have complete control over the messaging and experience. This is the most commonly used option.

• Scanning Raw Image Data - For complete control you may directly capture image data and process it for barcodes. This is sometimes done by developers who are capturing photographs for audit purposes and want to read the barcode from a saved image. It is also possible to call this periodically on a preview stream for complete control over all camera parameters. Most developers do not require this level of control.

Refer to the appropriate sub-section of this Knowledge Base article for details on the solution that best fits your needs.