High-Speed Single Scanning

What is SparkScan?

For most people integrating scanning for the first time our pre-built component SparkScan is the best and quickest place to start. It includes a pre-built scanning interface that floats on top of any native application.

This bundles multiple scanning features together and addresses many common challenges associated with scanning on smart devices.

SparkScan Quickstart Guide
Run SparkScan Samples
Learn More About SparkScan

Run SparkScan Samples

There are both simple and advanced SparkScan samples available on our Github repository.

ListBuildingSample	ReceivingSample

A simple sample that demonstrates how to populate a list of scanned barcodes using the Scandit SparkScan API.	An advanced sample that shows how to share scan data between MatrixScan Count and Spark Scan to populate an item list.

SparkScan Quick Start Guide

Add the SDK to your App

Prerequisites

The latest stable version of the Android SDK (for example through the latest Android Studio).
An Android project with target SDK version 23 (Android 6, Marshmallow) or higher.
A valid Scandit Data Capture SDK license key. You can sign up for a free test account at ssl.scandit.com.

Note

Devices running the Scandit Data Capture SDK need to have a GPU or the performance will drastically decrease.

Add the SDK

Scandit Data Capture SDK is distributed as AAR libraries in the official Scandit maven repository.

You will always need to add a reference to com.scandit.datacapture:core, which contains the shared functionality used by the other data capture modules. If you’re using textcapture-related functionalities, make sure to also add a reference to com.scandit.datacapture:text-base. In addition, depending on the data capture task, you will need a reference to:

com.scandit.datacapture:barcode (ScanditBarcodeCapture API) if you want to use barcode-related functionality such as barcode capture or MatrixScan.
com.scandit.datacapture:parser (ScanditParser API) if you want to parse data strings, e.g. as found in barcodes, into a set of key-value mappings.
com.scandit.datacapture:text (ScanditTextCapture API) if you want to use text recognition (OCR) functionality, often combined with barcode scanning to deliver simultaneous barcode and text capture.
com.scandit.datacapture:id (ScanditIdCapture API) if you want to scan personal identification documents such as identity cards, passports or visas.

You can safely remove barcode, parser, text or id dependencies if you are not going to use their features.

Gradle

Add mavenCentral() repository in build.gradle file:

repositories {
  mavenCentral()
}

Add the necessary artifacts as dependencies to the app’s build.gradle:

dependencies {
  implementation "com.scandit.datacapture:core:[version]"
  implementation "com.scandit.datacapture:barcode:[version]"
  implementation "com.scandit.datacapture:parser:[version]"
  implementation "com.scandit.datacapture:text-base:[version]"
  implementation "com.scandit.datacapture:text:[version]"
  implementation "com.scandit.datacapture:id:[version]"
}

Latest [version] is 6.19.0 and can be found on Sonatype.

Note

The core module depends on okhttp version 4.9.2. If your project already implements a different version of okhttp (within the supported version range specified in the requirements page), make sure to exclude the group from the gradle implementation of the core module.

implementation("com.scandit.datacapture:core:[version]") {
  exclude group: "com.squareup.okhttp3"
}

Maven

Add the mavenCentral repository in pom.xml file:

<repositories>
  <repository>
      <snapshots>
        <enabled>false</enabled>
      </snapshots>
      <id>central</id>
      <name>Maven Central</name>
      <url>https://repo1.maven.org/maven2</url>
  </repository>
</repositories>

Add the necessary artifacts as dependencies:

<dependency>
  <groupId>com.scandit.datacapture</groupId>
  <artifactId>core</artifactId>
  <version>[version]</version>
</dependency>

<dependency>
  <groupId>com.scandit.datacapture</groupId>
  <artifactId>barcode</artifactId>
  <version>[version]</version>
</dependency>

<dependency>
  <groupId>com.scandit.datacapture</groupId>
  <artifactId>parser</artifactId>
  <version>[version]</version>
</dependency>

<dependency>
  <groupId>com.scandit.datacapture</groupId>
  <artifactId>text-base</artifactId>
  <version>[version]</version>
</dependency>

<dependency>
  <groupId>com.scandit.datacapture</groupId>
  <artifactId>text</artifactId>
  <version>[version]</version>
</dependency>

<dependency>
  <groupId>com.scandit.datacapture</groupId>
  <artifactId>id</artifactId>
  <version>[version]</version>
</dependency>

Latest [version] can be found here.

Get a License Key

Sign up or Sign in to your Scandit account
Create a project
Create a license key by specifying your bundle ID

If you have a paid subscription, please reach out to support@scandit.com if you need a new license key.

Additional Information

Note

If you’re using androidx.fragments dependency and have the situation where a scanning fragment navigates to another scanning fragment with an incompatible mode, make sure you’re using version 1.3.0+ of the dependency. If not, you may run into an incompatible modes error, as the new fragment gets resumed before the previous is paused and for some time incompatible modes may be enabled in the DataCaptureContext at the same time. This results in sessions being empty of any result.

Note

On Android, the Scandit SDK uses content providers to initialize the scanning capabilities properly. If your own content providers depend on the Scandit SDK, choose an initOrder lower than 10 to make sure the SDK is ready first.

If not specified, initOrder is zero by default and you have nothing to worry about.

Check the official <provider> documentation.

Get Started With SparkScan

In this guide you will learn step by step how to add SparkScan to your application.

Roughly, the steps are:

Create a new Data Capture Context instance.
Configure the Spark Scan Mode.
Create the SparkScanView with the desired settings and bind it to the application’s lifecycle.
Register the listener to be informed when new barcodes are scanned and update your data whenever this event occurs.

1. Create a New Data Capture Context Instance

The first step to add capture capabilities to your application is to create a new Data Capture Context. The context expects a valid Scandit Data Capture SDK license key during construction.

DataCaptureContext dataCaptureContext = DataCaptureContext.forLicenseKey("-- ENTER YOUR SCANDIT LICENSE KEY HERE --");

2. Configure the SparkScan Mode

The SparkScan Mode is configured through SparkScanSettings and allows you to register one or more listeners that are informed whenever a new barcode is scanned.

For this tutorial, we will set up SparkScan for scanning EAN13 codes. Change this to the correct symbologies for your use case (for example, Code 128, Code 39…).

SparkScanSettings settings = new SparkScanSettings();
HashSet<Symbology> symbologies = new HashSet<>();
symbologies.add(Symbology.EAN13_UPCA);
settings.enableSymbologies(symbologies);

Next, create a SparkScan instance with the settings initialized in the previous step:

SparkScan sparkScan = new SparkScan(settings);

3. Setup the Spark Scan View

The SparkScan built-in user interface includes the camera preview and scanning UI elements. These guide the user through the scanning process.

The SparkScanView appearance can be customized through SparkScanViewSettings.

SparkScanViewSettings viewSettings = new SparkScanViewSettings();
// setup the desired appearance settings by updating the fields in the object above

By adding a SparkScanView, the scanning interface (camera preview and scanning UI elements) will be added automatically to your application.

Add a SparkScanView to your view hierarchy:

Construct a new SparkScan view. The SparkScan view is automatically added to the provided parentView (preferably an instance of SparkScanCoordinatorLayout):

SparkScanView sparkScanView = SparkScanView.newInstance(parentView, dataCaptureContext, sparkScan, viewSettings);

Additionally, make sure to call sparkScanView.onPause() and sparkScanView.onResume() in your Fragment/Activity onPause and onResume callbacks. You have to call these for the correct functioning of the SparkScanView.

@Override
protected void onPause() {
    sparkScanView.onPause();
    super.onPause();
}

@Override
protected void onResume() {
    sparkScanView.onResume();
    super.onResume();
}

4. Register the Listener to Be Informed When a New Barcode Is Scanned

To keep track of the barcodes that have been scanned, implement the SparkScanListener interface and register the listener to the SparkScan mode.

// Register self as a listener to monitor the spark scan session.
sparkScan.addListener(this);

SparkScanListener.onBarcodeScanned() is called when a new barcode has been scanned. This result can be retrieved from the first object in the provided barcodes list: SparkScanSession.newlyRecognizedBarcodes. Please note that this list only contains one barcode entry. When a barcode is scanned, it is possible to emit a sound and a visual feedback via SparkScanView.emitFeedback().

@Override
public void onBarcodeScanned(
    @NonNull SparkScan sparkScan, @NonNull SparkScanSession session, @Nullable FrameData data
) {
    // Gather the recognized barcode
    Barcode barcode = session.getNewlyRecognizedBarcodes().get(0);

    // Emit sound and vibration feedback
    sparkScanView.emitFeedback(new SparkScanViewFeedback.Success());

    // This method is invoked from a recognition internal thread.
    // Run the specified action in the UI thread to update the internal barcode list.
    runOnUiThread(() -> {
        // Update the internal list and the UI with the barcode retrieved above
        this.latestBarcode = barcode
    });
  }

Learn More About SparkScan

UI overview

The SparkScan’s UI is minimal, meant to be overlayed on top of any application without the need to adapt the existing app - while offering the best user experience.

Three main elements compose the UI:


Mini preview: A small camera preview screen giving a visual confirmation while aiming at the code. This is placed in the top right corner, where the phone camera is located. Its size depends on the scanning mode enabled.	Trigger button: A large-sized floating button that users can drag up and down to position it in the most convenient and ergonomic place. This eliminates the need to look at the screen to trigger scanning.	Settings Toolbar: A quick-access toolbar that includes controls of settings (like the torch, haptics feedback etc.), scan modes (like switching to continuous scanning, enabling the target mode etc,) and more. More info on the scanning modes in the following section.

NOTE: Additional UI elements are available for developers to use if their app logic requires displaying errors or additional feedback while scanning. More information in Customisation and advanced capabilities.

Scanning Modes Supported

SparkScan offers different scanning modes, to optimally fit different use-cases and user preferences.

These modes change the workflow and the way the user scans the barcodes.
They can be toggled manually by the end users, or set a priori by the developer.

SparkScan offers two scanning modes:

Default mode: Ideal for close-range and fast paced scanning. This mode will display a small camera preview to aid with aiming.
Target mode: Ideal for scanning scenarios where precision is important. This mode will display a big camera preview with a target to precisely select the barcode to scan. This is useful when multiple barcodes are in view. As this mode allows you to choose the zoom level, it is also ideal for long-range scanning (e.g. to scan a label at the bottom shelf).

And two scanning behaviors:

Single scan: the user needs to trigger the scanner every time to scan a barcode. This allows for a more controlled scanning.
Continuous scan: Scan barcodes consecutively. The user needs to trigger the scanner once and barcodes will be scanned without any further interaction before each scan. This allows for a smoother experience when multiple barcodes need to be scanned consecutively.


Scanning Mode: Default.	Scanning Mode: Default.	Scanning Mode: Target.
Scanning Behavior: Single Scan.	Scanning Behavior: Continuous Scan.	Scanning Behavior: Single Scan.

NOTE: By default, scanning modes and scanning behaviors can be toggled by the end user acting on the setting toolbar - to allow for the maximum flexibility.
Developers can always change the initial configuration of the scanner or select a specific configuration removing the possibility to toggle it.
More information in Customisation and advanced capabilities.

Workflow Description

When SparkScan is started, the UI presents just the trigger button, collapsed on the side.
To start scanning, the user can:
- swipe to open the button, then tap on it.
- tap on the collapsed trigger button.


Swipe and tap to start the scanner.	Tap to start the scanner.

When the scanner is active, the mini preview becomes visible.
Depending on the scanning mode enabled, the workflow will behave differently:
- In Single Scan, upon scan the user will receive audio/haptic feedback confirming the scan, and the mini preview will display the scanned barcode for a small amount of time. The scanner will need to be restarted to scan a new code.
- In Continuous Scan, upon scan the user will receive audio/haptic feedback confirming the scan. The mini preview keeps showing the camera preview, ready to scan a new code.


Single Scan.	Continuous Scan.

Upon completing the scanning process (or to interact with the customer app layer), the user can tap in any area outside the trigger button and the mini preview. This collapses the scanner button back to the side, going back to the initial state.

Collapse the SparkScan UI.

Supported Devices

Runs on iOS and Android devices.

Supported Symbologies

SparkScan supports all of the major symbologies listed here: Barcode Symbologies except DotCode, MaxiCode and postal codes (KIX, RM4SCC, LAPA 4SC and USPS Intelligent Mail).

If you are not familiar with the symbologies that are relevant for your use case, you can use capture presets that are tailored for different verticals (e.g. retail, logistics, etc.).

For more symbology specific information, please refer to this link.

Customisation and advanced capabilities

SparkScan offers an out-of-the-box experience optimized for efficiency and a frictionless worker experience. This experience has been crafted after many user testing and with the product knowledge gained in the many years of Scandit.
While this out-of-the-box experience will suit most use-cases, we understand there are some special cases in which some configuration is still needed.
In this page, we collect the main customization and advanced settings you may need to customize SparkScan to obtain the best experience possible.

Advanced capabilities

Hold-to-scan gesture

In addition to the standard tap-to-scan interaction, in which the users tap the trigger button to enable the scanner, users can hold down the scan button to perform a hold-to-scan interaction. In this case, regardless of the scanning behavior (whether is Single Mode or Continuous Mode), the scanner will be active (scanning barcodes) as long as the button is pressed.

Developers can disable this gesture via SparkScanViewSettings.holdToScanEnabled.

EXAMPLE: to create a workflow in which only Single Scan is possible, developers will need to:

hide the single/continuous toggle via SparkScanView.scanningBehaviorButtonVisible.
disable the hold-to-scan gesture via SparkScanViewSettings.holdToScanEnabled.

Control the Scanner through a Hardware Button

Allowing the end user to control the scanner with hardware buttons can be useful if your users typically wear gloves. It can also improve ergonomics in some workflows.

SparkScan offers a built-in API to let you do this via SparkScanViewSettings.hardwareTriggerEnabled.

Trigger the Error State

You may want to introduce logic in your app to show an error message when scanning specific barcodes (e.g. barcodes already added to the list, barcodes from the wrong lot etc.). SparkScan offers a built-in error state you can easily set to trigger an error feedback prompt to the user. You will be able to customize:

The text message
The timeout of the error message: the scanner will be paused for the specified amount of time, but the user can quickly restart the scanning process by tapping the trigger button
The color of the flashing screen upon scan. You can enable or disable the visual feedback via SparkScanViewSettings.visualFeedbackEnabled and you can control the color via SparkScanViewFeedback.
The color of the highlight for the scanned barcode.

An error example is here reported:

self.sparkScanView.emitFeedback(SparkScanViewErrorFeedback(message: "This code should not have been scanned", resumeCapturingDelay: 6, visualFeedbackColor: UIColor.red))

NOTE: you can have different error states triggered by different logic conditions. For example you can trigger an error state when a wrong barcode is scanned, and another one when a duplicate barcode is scanned. These errors can show different colors and have different timeouts.

NOTE: a high timeout (e.g. >10s) typically requires the users to interact with the UI to start scanning again. This is a good choice when you want to interrupt the scanning workflow (e.g. because a wrong barcode is scanned and some actions need to be performed). A small timeout (e.g. <2s) could allow the user to scan again without having to interact with the app, just momentarily pausing the workflow to acknowledge that a “special” barcode has been scanned.


	In this example, a first error is triggered when a “duplicate” barcode is scanned (in blue) - stopping the scanner for 2s. Users do not need to restart the scanner manually, as the timeout is limited. A second error is triggered when an “error” barcode is scanned, with a long timeout (60s) that requires the user to trigger the scanner again.

Increase the precision of your scanning workflow

In scenarios where numerous barcodes are close together or in crowded environments, accurately selecting the right barcode can be difficult. To address this challenge, a new workflow that incorporates an aimer in the camera preview is recommended so that users can precisely target and scan intended barcodes.

As a developer you can select two different SparkScan workflow by picking a SparkScanScanningPrecision value:

DEFAULT
ACCURACY

Depending on the selection, the behavior of the preview will be different.

Default workflow VS Accuracy workflow.

DEFAULT: the standard workflow for use cases in which the accurate selection of a barcode (e.g. long range scanning or many barcode close together) is occasional.

Preview only visible when scanning (hidden otherwise).
Two scanning modes:
- Default mode: Mini preview without aimer (barcodes can be scanned anywhere in the mini-preview).
- Target mode: big preview with an aimer to precisely scan barcodes far away or close together.

ACCURACY: the workflow for use cases where you mainly want to select a barcode (among many) or you need to look through the preview at all times (to ensure the right scan).

Preview always visible, scanning only active when tapping/holding the trigger button
Two scanning modes:
- Default Mode: Mini preview with an aimer, only scanning aimed barcodes to increase precision
- Expanded mode: big preview with an aimer in case you want to be more precise or you need to zoom in.

Accuracy mode example.

Customization

Customize colors and texts

All texts (guidance inside the trigger button and hints’ messages), colors and opacity of the SparkScan UI elements (trigger button, setting toolbar, toasts) can be customized to match the desired language and color scheme.

Please refer to SparkScanView for the full list of available parameters.

Move the trigger button to the upper part of the screen

The trigger button can only slide up and down on the bottom part of the screen, where it is easy to reach with the finger that holds the smartphone. This reserves space for the large camera preview on the top part of the screen in the target mode.
By default, the trigger button can be moved up and down in the bottom part of the screen - where is ergonomically reachable by the finger holding the smartphone. This also leaves the space for the big camera preview in the target mode.

If the trigger button blocks part of your application, you might want to move the scan button to the upper part of the screen. You can do this by using the SparkScanViewSettings.ignoreDragLimits option.

Effect of the ignoreDragLimits option.


Standard toolbar.	Toolbar with advanced modes icons shown.


Default icons shown.	Only two icons left.

High-Speed Single Scanning

What is SparkScan?

Run SparkScan Samples

SparkScan Quick Start Guide

Add the SDK to your App

Prerequisites

Add the SDK

Gradle

Maven

Get a License Key

Additional Information

Get Started With SparkScan

1. Create a New Data Capture Context Instance

2. Configure the SparkScan Mode

3. Setup the Spark Scan View

4. Register the Listener to Be Informed When a New Barcode Is Scanned

Learn More About SparkScan

UI overview

Scanning Modes Supported

Workflow Description

Supported Devices

Supported Symbologies

Customisation and advanced capabilities

Advanced capabilities

Hold-to-scan gesture

Control the Scanner through a Hardware Button

Trigger the Error State

Increase the precision of your scanning workflow

Add More Advanced Scanning Modes to the Setting Toolbar

Customization

Customize colors and texts

Move the trigger button to the upper part of the screen

Hide Controls from the Setting Toolbar