Barcode Scanning and Search: From Recognition to Product Display

Barcode Scanning and Search: From Recognition to Product Display

Imagine: a user opens the camera, points it at a barcode — the app must recognize the code, find the product in the database, and display the result in milliseconds. At first glance, the task is simple, but in practice, the capture → recognition → query → display pipeline can become a bottleneck. Without proper architecture, the time from scanning to displaying the result exceeds 2 seconds, leading to user abandonment. We have implemented this functionality for over 30 projects. Experience shows: if the architecture is not thought out in advance, the project risks getting bogged down in rework. Let's break down how to do it right and without surprises.

Platform capabilities for recognition

iOS: AVFoundation with AVMetadataObjectTypeEAN13Code, UPC-A, QRCode, and a dozen other types. Or VisionKit — VNDetectBarcodesRequest with VNBarcodeObservation, convenient for processing static images from the gallery. DataScannerViewController (as of iOS 16) is the simplest path: one class, built-in UI, support for all types out of the box. Apple documentation: AVFoundation.

Android: ML Kit Barcode Scanning (com.google.mlkit:barcode-scanning) — works offline, supports 1D and 2D codes. Or ZXing — a proven library, but on weak devices ML Kit is 2–3 times faster than ZXing, especially for Data Matrix recognition.

The choice depends on the minimum OS version and offline requirements. On Android, ML Kit requires Google Play Services; on devices without GMS (Huawei), an autonomous bundled model is needed. We select the stack for each specific project — this guarantees stability on any device.

Why search is harder than scanning

Scanning itself is a few lines of code. The complexity lies in the search architecture.

Deduplication of results. The camera recognizes the same barcode dozens of times per second. Without debounce, the request goes to the server 50 times before the user moves the camera away from the shelf. Solution: throttle on the last recognized code with a delay of 800–1000 ms.

Offline search. If the product catalog is available locally, searching via SQLite or Room (Android) / CoreData (iOS) with an indexed barcode field takes 1–5 ms. Without an index on a table of 100,000 products — 300–500 ms even on a flagship device.

Unknown code. The user sees a message if the barcode is not found in the database. Fallback to Open Food Facts API or GS1 lookup, or just a message — this is a product decision, but it must be incorporated into the architecture in advance, otherwise you will have to redo the flow.

Example: search with debounce on iOS

private var lastScannedCode: String?
private var searchTimer: Timer?

func handleScannedCode(_ code: String) {
    guard code != lastScannedCode else { return }
    lastScannedCode = code
    searchTimer?.invalidate()
    searchTimer = Timer.scheduledTimer(withTimeInterval: 0.8, repeats: false) { [weak self] _ in
        self?.performSearch(barcode: code)
    }
}

How we handle different barcode types

Depending on the scenario, we connect the necessary parsers. Below is a table of common formats we work with.

If the technical specification does not specify specific types, we clarify in advance. Including support for all types without necessity is not worth it: it slows down recognition and complicates the code. It is optimal to limit to the three most requested ones.

How to implement offline search without delays

For offline mode, we use indexed databases: CoreData on iOS and Room on Android. The barcode field is indexed, which gives search speed of 1–5 ms for 100,000 records. Additionally, we cache query results in memory (NSCache / LruCache) so that repeated search for the same code does not access disk. If the product is not found locally, we move to the fallback.

Development process: from analysis to deployment

1. Requirements analysis (1–2 days) — clarify code formats, need for offline database, fallback strategy, target audience.
2. Design (1–2 days) — select libraries, design search architecture (debounce, cache, indexes), define API contracts.
3. Implementation (3–5 days) — write scanning code, integrate with local database and backend, implement fallback.
4. Testing (1–2 days) — test on a library of 200+ test barcodes, including rare formats and damaged codes.
5. Deployment (1 day) — publish to App Store / Google Play with configured App Review and tests.

For iOS, the minimum supported version is iOS 13 (VisionKit is available). If iOS 12 support is required, we use only AVFoundation. For Android — minSdk 21 (ML Kit is available from API 19, but we recommend 21+). ProGuard/R8 rules (to keep barcode classes) are provided in the distribution.

Comparison of recognition libraries

Why trust us with development?

We have been doing mobile development for many years. During this time, we have implemented over 30 barcode scanning and search integrations for retail, warehouses, and logistics. We use proven libraries and frameworks, automate pipeline testing. We deliver each project with documentation on available APIs and maintenance recommendations. Savings on development from scratch can reach 40% when using ready-made components.

What is included in the result

• Configured recognition for selected formats.
• Search architecture with debounce and caching.
• Integration with backend or local database.
• Fallback handling for unknown codes.
• Source code with comments, build and deployment instructions, help with publication in App Store / Google Play.

The development timeline for a basic version is 1–3 days for one search type, up to 5–7 days for a comprehensive solution with an offline catalog. The cost is calculated individually after clarifying the code types and search architecture.

Get a consultation on your project — we will assess the complexity and offer a suitable solution. Contact us to discuss your task.

Hardware Integration: BLE, NFC, IoT, and HomeKit

When the goal is to connect a smartphone with a physical device, half the problems are not in the code but in the firmware, BLE service characteristics, and protocol delays. As mobile developers, we work at the intersection with the firmware team — without understanding the stack from the bottom up, the outcome is unpredictable. That is why we always start with an HCI log and the GATT specification. The Apple Developer Core Bluetooth Framework document is a mandatory read, but we also rely on empirical logs. Configuring MTU, handling background reconnections, and resolving GATT queue overflows require real protocol knowledge, not just tutorials.

Bluetooth Low Energy is defined by the Bluetooth SIG (Bluetooth Core Specification). NFC standards are maintained by the NFC Forum (NFC Forum Technical Specifications). Matter is an open standard published by the Connectivity Standards Alliance.

Why Is BLE Integration the Most Common Failure Point?

Bluetooth Low Energy is the main protocol for wearables, medical devices, smart locks, and industrial sensors. Core Bluetooth on iOS and BluetoothGatt on Android implement the same specification but behave differently in edge cases. Our project statistics: over 70% of BLE support tickets are related to low-level GATT errors, not application logic. For any new project, we allocate time to analyze platform-specific quirks — simple code reuse between platforms never works for BLE NFC integration.

What to Do with Error 133 on Android?

Error 133 is the most common in Android BLE development. It is not a generic 'something went wrong' but a specific indicator of GATT queue overflow or improper closure of a previous connection. We fix it with two approaches. First, use a queue for GATT operations — write, read, and notification subscribe strictly sequentially via an operation queue. Second, always call disconnect() before close(). Our GATT operation queue reduces ATT_INSUFFICIENT_RESOURCES errors by 3 times compared to concurrent requests. Default MTU is 23 bytes. An MTU exchange request is mandatory for transferring data larger than 20 bytes. On iOS, MTU is requested automatically on connection; on Android, you must explicitly call requestMtu(). Without it, you cannot transfer, for example, an image or log through a characteristic. This approach saved one medical client $15,000 in rework costs over six months by eliminating random disconnections and data loss.

What Are the Key Differences Between HomeKit and Matter?

HomeKit is Apple's smart home ecosystem. For integration, the device must have MFi certification (or work via Software Authentication for Matter). The mobile app uses the HomeKit framework: HMHomeManager → HMHome → HMRoom → HMAccessory → HMService → HMCharacteristic. Matter (formerly CHIP) is a cross-platform standard supported by Apple, Google, Amazon, and Samsung. On iOS, Matter devices are added via MTRDeviceController; on Android, via Google Home SDK or Matter SDK directly. Advantage of Matter: a single device works with HomeKit, Google Home, and Alexa without reflashing, and configuration is 4 times faster compared to the proprietary HAP protocol.

For Flutter and React Native, we use flutter_blue_plus and react-native-ble-plx respectively — both are actively maintained and cover 90% of scenarios, but for background GATT notifications on Android, a foreground service is still required. Ensure deep linking (Universal Links on iOS, App Links on Android) is configured to properly wake the app when scanning an NFC tag or receiving a push notification from an IoT device. ATT (App Tracking Transparency) requirements usually do not apply to hardware integration, but if the app collects anonymous analytics, add the request. NFC reading on iOS is 2x more reliable for NDEF messages due to consistent session handling — we benchmarked it across 15 phone models.

NFC: Core NFC and Android NFC API

iOS supports NFC reading via CoreNFC since iOS 11, writing since iOS 13. Important limitation: the scanning session is active only as long as the NFCNDEFReaderSession object is alive and shows system UI. Background scanning is only available for apps with the entitlement com.apple.developer.nfc.readersession.formats and only for ISO 14443 (bank cards, passports) — and this entitlement is not granted to everyone. On Android, it is simpler: NfcAdapter.enableForegroundDispatch() catches tags in the foreground without system UI. Background app launch via NFC tag is implemented through intent-filter with ACTION_NDEF_DISCOVERED. Platform comparison for NFC:

How We Integrate BLE and NFC: Step-by-Step Process

1. Analysis — Obtain the full BLE GATT specification (list of services, characteristics, data formats) or HCI log from the firmware team. Without this, development turns into reverse engineering using nRF Connect or Wireshark over HCI.
2. Design — Define the connection architecture: GATT operation queue, background services for Android, reconnection on signal loss. Consider MTU negotiation and handling of ATT_INSUFFICIENT_RESOURCES errors.
3. Implementation — Code in Swift/Kotlin with platform specifics (Universal Links, App Links, push notifications via APNs/FCM for triggers). Use ProGuard/R8 (shrink) for Android code protection.
4. Testing — On real devices from day one. BLE emulator in simulators does not reproduce edge cases of reconnection, signal loss, MTU change. Use automation based on XCTest and Espresso.
5. Deployment — Upload to App Store Connect / Google Play Console with proper code signing and provisioning profile. For iOS — TestFlight, for Android — Firebase App Distribution.

For a tailored architecture design, contact our engineering team. We provide a free specification review within 2 business days.

What's Included (Deliverables)

• Source code of the mobile app with BLE, NFC, or IoT integration (Swift / Kotlin / Flutter / React Native)
• GATT protocol documentation (service and characteristic map)
• Load testing on 10+ real devices (error 133, reconnections, MTU negotiation)
• Analysis and resolution of edge cases (error ATT_INSUFFICIENT_RESOURCES, background connection loss, conflict with background fetch)
• Build and deployment instructions (code signing, TestFlight, Firebase App Distribution)
• One month of post-release support

We have completed 45+ projects with BLE/NFC/HomeKit. Our engineers are certified by Apple and Google, and each stage of work is recorded in an issue tracker linked to commits. We use an engineer-to-client approach: no marketing pauses, direct access to the developer.

Reach out to our engineers for a detailed proposal and get a consultation with a review of your specification. Order a turnkey integration — we will analyze the HCI log, check the GATT characteristics, and propose an architecture in 2 days.