QR Code Scanner Development for Mobile Apps

Developing QR Code Scanning in a Mobile App

We often encounter the task of integrating a QR code scanner into an existing app. At first glance, there are many libraries, but each platform imposes its own rules: on iOS, strict App Store limitations; on Android, fragmentation of devices and OS versions. The result: the app either freezes on scanning or parses data incorrectly. Over 5+ years, we have implemented QR scanners in 20+ projects — from retail to healthcare, using Swift, Kotlin, and Flutter. In this article, we break down how to build a fast, reliable, and modular QR scanner considering all nuances: from framework selection (Vision vs ML Kit) to correct routing by data type.

According to Apple documentation, using DataScannerViewController requires setting up an entitlement and adding NSCameraUsageDescription. On Android, the CAMERA permission is required in AndroidManifest.xml. Skipping these steps is one of the most common causes of crashes on first launch.

How to Quickly Implement QR Code Scanning?

Scanning is only the first step. iOS 16+ uses DataScannerViewController — a one-liner setup:

let scanner = DataScannerViewController(
    recognizedDataTypes: [.barcode(symbologies: [.qr])],
    qualityLevel: .balanced,
    isHighlightingEnabled: true
)

isHighlightingEnabled: true adds visual highlighting — users appreciate that. For iOS 14–15, you need the Vision framework: VNDetectBarcodesRequest for photos, AVCaptureMetadataOutput for live video. On Android, we use ML Kit: BarcodeScanning.getClient() with BarcodeScannerOptions. Specify FORMAT_QR_CODE to optimize speed — if you need all formats, remove the filter, but speed drops slightly.

ML Kit on Android processes QR 3–5 times faster than ZXing, and 2 times faster than Vision on iOS on mid-range devices (data from our tests on 10 models).

Comparison of iOS and Android Approaches

Why Content Parsing Is More Important Than Scanning Itself?

A QR code is a string. How you handle it determines UX.

• Starts with http:// or https:// → open in SFSafariViewController / CustomTabs.
• WIFI:S:NetworkName;T:WPA;P:password;; → connect to Wi-Fi (iOS: NEHotspotConfiguration, Android: WifiNetworkSuggestion).
• BEGIN:VCARD → parse with CNContactVCardSerialization (iOS) or VCardReader (Android).
• Internal app format → custom processing.

Regular expressions for type detection work but are fragile. ML Kit on Android automatically detects the type via Barcode.valueType (URL, WIFI, CONTACT_INFO, etc.). On iOS, VNBarcodeObservation.payloadStringValue returns the raw string — you must determine the type yourself. For Wi-Fi on iOS, you need com.apple.developer.networking.HotspotConfiguration entitlement — a hidden complexity.

QR Data Types and Their Handling

Gallery Handling: A Must-Have Minimum

Users expect to be able to pick a QR code from a photo, not just scan with the camera. Implementation:

iOS: PHPickerViewController → get UIImage → VNDetectBarcodesRequest on CIImage. Runs in background via perform.

Android: ActivityResultContracts.GetContent("image/*") → get Uri → InputImage.fromFilePath(context, uri) → BarcodeScanning.getClient().process(inputImage).

Common mistake: processing image on the main thread. For gallery photos, this blocks the UI for 200–500 ms. Always do it in a background thread. Our experience shows users notice delays as low as 150 ms.

Turnkey Development Process

1. Analysis — we study your app, target audience, and QR usage scenarios.
2. Design — choose the stack (ML Kit vs Vision, routing implementation), prepare a prototype with one code type.
3. Implementation — integrate scanner, parsing, gallery handling, deep linking.
4. Testing — on real devices with different OS versions, verify all QR formats.
5. Deployment — publish to App Store / Google Play, configure provisioning profiles.

What's Included

• Source code of the scanning module in Swift / Kotlin / Dart with documentation.
• Integration with your app's existing navigator.
• Handling of all common QR types (URL, Wi-Fi, vCard, custom).
• Gallery support.
• Testing on 5+ physical devices.
• Assistance with publishing (App Store Connect, Google Play Console).

Estimated Timelines

From 3 to 10 business days, depending on routing complexity and need for deep linking. Contact us so we can evaluate your project and provide an accurate cost estimate.

Our Experience

Over 5+ years, we have implemented QR scanners in 20+ apps, from retail to healthcare. We have worked with Apple certificates, ProGuard/R8 shrinking, Firebase App Distribution. We have experience navigating App Store review with custom entitlements. If you have a specific case — reach out, let's discuss.

Time savings for users on manual data entry reach up to 80% when using a QR scanner. Order a turnkey QR scanner module development. Get a consultation on integration and timeline estimation — contact us.

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.