BarcodeScanning.MAUI vs IronBarcode: C# Barcode Library Comparison

Live Camera Scanning Pattern

The entire BarcodeScanning.Native.Maui API pattern is a XAML control paired with a C# event handler:

<scanner:CameraView x:Name="CameraView"
                    OnDetectionFinished="OnBarcodeDetected"
                    CameraEnabled="True"
                    BarcodeFormats="All" />

<scanner:CameraView x:Name="CameraView"
                    OnDetectionFinished="OnBarcodeDetected"
                    CameraEnabled="True"
                    BarcodeFormats="All" />

private void OnBarcodeDetected(object sender, OnDetectionFinishedEventArg e)
{
    var barcode = e.BarcodeResults.FirstOrDefault();
    if (barcode != null)
        ResultLabel.Text = barcode.DisplayValue;
}

private void OnBarcodeDetected(object sender, OnDetectionFinishedEventArg e)
{
    var barcode = e.BarcodeResults.FirstOrDefault();
    if (barcode != null)
        ResultLabel.Text = barcode.DisplayValue;
}

Private Sub OnBarcodeDetected(sender As Object, e As OnDetectionFinishedEventArg)
    Dim barcode = e.BarcodeResults.FirstOrDefault()
    If barcode IsNot Nothing Then
        ResultLabel.Text = barcode.DisplayValue
    End If
End Sub

This control gives users a real-time viewfinder embedded in the MAUI page. Barcode detection fires continuously as the camera feed is active. The UX is well-suited for consumer apps where "point and scan" is the primary interaction. The constraint is that this is the only interaction the library supports — requirements that extend beyond live camera detection in a MAUI context fall outside its scope.

Detailed Feature Comparison

BarcodeScanning.MAUI Approach

BarcodeScanning.Native.Maui wraps the native camera detection pipeline on each platform. On Android, ML Kit processes frames; on iOS and macOS, Apple's Vision framework processes frames; on Windows, ZXingCpp processes frames. The library surfaces this as a MAUI CameraView control with an OnDetectionFinished event. The application code never handles image bytes directly — it only handles the detected barcode values that emerge from the event.

private void OnBarcodeDetected(object sender, OnDetectionFinishedEventArg e)
{
    var barcode = e.BarcodeResults.FirstOrDefault();
    if (barcode != null)
        ResultLabel.Text = barcode.DisplayValue;
}

private void OnBarcodeDetected(object sender, OnDetectionFinishedEventArg e)
{
    var barcode = e.BarcodeResults.FirstOrDefault();
    if (barcode != null)
        ResultLabel.Text = barcode.DisplayValue;
}

Private Sub OnBarcodeDetected(sender As Object, e As OnDetectionFinishedEventArg)
    Dim barcode = e.BarcodeResults.FirstOrDefault()
    If barcode IsNot Nothing Then
        ResultLabel.Text = barcode.DisplayValue
    End If
End Sub

The consequence of this design is that there is no other entry point. The camera is not optional — it is the only input the library knows about. A server, a file, a PDF, or any non-MAUI host has no path into the library.

IronBarcode Approach

IronBarcode receives image data through its BarcodeReader.Read() static method. The caller provides the data — from any source — and the library decodes it. On MAUI, the data comes from MediaPicker; on a server, it comes from a form upload; in a desktop application, it comes from a file dialog.

// IronBarcode in MAUI: capture a photo, then read barcodes from it
// NuGet: dotnet add package IronBarcode
using IronBarCode;

private async void ScanBarcodeButton_Clicked(object sender, EventArgs e)
{
    var photo = await MediaPicker.CapturePhotoAsync();
    if (photo == null) return;

    using var stream = await photo.OpenReadAsync();
    using var ms = new MemoryStream();
    await stream.CopyToAsync(ms);

    var results = BarcodeReader.Read(ms.ToArray());
    foreach (var result in results)
        ResultLabel.Text = result.Value;
}

// IronBarcode in MAUI: capture a photo, then read barcodes from it
// NuGet: dotnet add package IronBarcode
using IronBarCode;

private async void ScanBarcodeButton_Clicked(object sender, EventArgs e)
{
    var photo = await MediaPicker.CapturePhotoAsync();
    if (photo == null) return;

    using var stream = await photo.OpenReadAsync();
    using var ms = new MemoryStream();
    await stream.CopyToAsync(ms);

    var results = BarcodeReader.Read(ms.ToArray());
    foreach (var result in results)
        ResultLabel.Text = result.Value;
}

Imports IronBarCode
Imports System.IO

Private Async Sub ScanBarcodeButton_Clicked(sender As Object, e As EventArgs)
    Dim photo = Await MediaPicker.CapturePhotoAsync()
    If photo Is Nothing Then Return

    Using stream = Await photo.OpenReadAsync()
        Using ms As New MemoryStream()
            Await stream.CopyToAsync(ms)

            Dim results = BarcodeReader.Read(ms.ToArray())
            For Each result In results
                ResultLabel.Text = result.Value
            Next
        End Using
    End Using
End Sub

This code runs identically across the MAUI targets that can capture an image. For server-side use, the same BarcodeReader.Read() method accepts an uploaded file's byte array or a PDF path. The IronBarcode documentation covers all supported input types.

BarcodeScanning.MAUI Approach

BarcodeScanning.Native.Maui supports all four MAUI targets (iOS, Android, Windows since 3.0.1, and macOS Catalyst), but each target uses a different recognition engine: Apple Vision on iOS and macOS, Google ML Kit on Android, and ZXingCpp on Windows. Symbology coverage and decoding behavior differ across the three engines, so a barcode that decodes reliably on one platform may behave differently on another. Outside of MAUI — ASP.NET, console, WPF, WinForms, Blazor Server, Azure Functions — the library has no implementation. Teams that need barcode logic in both a MAUI app and a backend service must use a different library for the non-MAUI code.

IronBarcode Approach

IronBarcode's BarcodeReader.Read() call uses the same managed engine on every supported target, so behavior is consistent across Windows, Linux, macOS, ASP.NET, and any MAUI target that can capture an image and hand it to the reader. There are no #if WINDOWS blocks, no conditional dependency loading, and no stub implementations needed. For file and PDF inputs, the pattern is also consistent:

using IronBarCode;

// Read barcodes from a file the user selected
var file = await FilePicker.PickAsync();
if (file != null)
{
    var results = BarcodeReader.Read(file.FullPath);
    foreach (var result in results)
        Console.WriteLine($"{result.Format}: {result.Value}");
}

// Read barcodes directly from a PDF — no image extraction step needed
var pdfResults = BarcodeReader.Read("shipment-manifest.pdf");

using IronBarCode;

// Read barcodes from a file the user selected
var file = await FilePicker.PickAsync();
if (file != null)
{
    var results = BarcodeReader.Read(file.FullPath);
    foreach (var result in results)
        Console.WriteLine($"{result.Format}: {result.Value}");
}

// Read barcodes directly from a PDF — no image extraction step needed
var pdfResults = BarcodeReader.Read("shipment-manifest.pdf");

Imports IronBarCode

' Read barcodes from a file the user selected
Dim file = Await FilePicker.PickAsync()
If file IsNot Nothing Then
    Dim results = BarcodeReader.Read(file.FullPath)
    For Each result In results
        Console.WriteLine($"{result.Format}: {result.Value}")
    Next
End If

' Read barcodes directly from a PDF — no image extraction step needed
Dim pdfResults = BarcodeReader.Read("shipment-manifest.pdf")

The IronBarcode MAUI integration guide provides complete setup instructions for all MAUI targets. IronBarcode also supports server-side deployment in ASP.NET, Docker, Azure Functions, and AWS Lambda environments where BarcodeScanning.Native.Maui has no path at all.

BarcodeScanning.MAUI Approach

On iOS, BarcodeScanning.Native.Maui's underlying detection (Apple Vision) can return 13 digits for UPC-A barcodes. UPC-A is a 12-digit format; the extra leading zero matches EAN-13 encoding. The library passes this raw value through, and applications normalize it as needed. Applications that store UPC-A values in a database without normalization may accumulate records with a leading zero.

The documented workaround checks the format and trims the value:

// Normalize iOS UPC-A — strip the leading zero when present
private void OnBarcodeDetected(object sender, OnDetectionFinishedEventArg e)
{
    var barcode = e.BarcodeResults.FirstOrDefault();
    if (barcode == null) return;

    var value = barcode.DisplayValue;
    if (barcode.BarcodeFormat == BarcodeFormats.Upca && value.Length == 13)
        value = value.Substring(1);

    ProcessBarcode(value);
}

// Normalize iOS UPC-A — strip the leading zero when present
private void OnBarcodeDetected(object sender, OnDetectionFinishedEventArg e)
{
    var barcode = e.BarcodeResults.FirstOrDefault();
    if (barcode == null) return;

    var value = barcode.DisplayValue;
    if (barcode.BarcodeFormat == BarcodeFormats.Upca && value.Length == 13)
        value = value.Substring(1);

    ProcessBarcode(value);
}

' Normalize iOS UPC-A — strip the leading zero when present
Private Sub OnBarcodeDetected(sender As Object, e As OnDetectionFinishedEventArg)
    Dim barcode = e.BarcodeResults.FirstOrDefault()
    If barcode Is Nothing Then Return

    Dim value = barcode.DisplayValue
    If barcode.BarcodeFormat = BarcodeFormats.Upca AndAlso value.Length = 13 Then
        value = value.Substring(1)
    End If

    ProcessBarcode(value)
End Sub

The format check is necessary so that EAN-13 values beginning with 0 are not trimmed by mistake. PDF417 is separately documented in GitHub issues as "very problematic — most scans never occur" on the iOS/Android engines, which is relevant for shipping labels, driver's licenses, and boarding passes.

IronBarcode Approach

IronBarcode returns the standard 12-digit UPC-A value through its managed engine. PDF417 is a supported format. The generation side is also available through IronBarcode's API:

using IronBarCode;

// Generate a QR code
QRCodeWriter.CreateQrCode("https://example.com", 500)
    .SaveAsPng("qr.png");

// Generate a Code128 barcode
BarcodeWriter.CreateBarcode("ITEM-12345", BarcodeEncoding.Code128)
    .ResizeTo(400, 100)
    .SaveAsPng("barcode.png");

using IronBarCode;

// Generate a QR code
QRCodeWriter.CreateQrCode("https://example.com", 500)
    .SaveAsPng("qr.png");

// Generate a Code128 barcode
BarcodeWriter.CreateBarcode("ITEM-12345", BarcodeEncoding.Code128)
    .ResizeTo(400, 100)
    .SaveAsPng("barcode.png");

Imports IronBarCode

' Generate a QR code
QRCodeWriter.CreateQrCode("https://example.com", 500) _
    .SaveAsPng("qr.png")

' Generate a Code128 barcode
BarcodeWriter.CreateBarcode("ITEM-12345", BarcodeEncoding.Code128) _
    .ResizeTo(400, 100) _
    .SaveAsPng("barcode.png")

For applications where barcode data accuracy directly affects inventory lookups, point-of-sale transactions, or supply chain integrations, IronBarcode's consistent format handling reduces the need for platform-specific normalization. The IronBarcode barcode reading documentation covers format-specific behavior in detail.

Cross-Platform Engine Consistency Becomes a Requirement

MAUI applications that target iOS, Android, Windows, and macOS pick up three different recognition engines when they use BarcodeScanning.Native.Maui: Apple Vision (iOS/macOS), Google ML Kit (Android), and ZXingCpp (Windows). Each engine has its own symbology coverage and decoding behavior, so the same barcode may decode differently across platforms — and applications often add normalization layers to paper over the differences. When that maintenance overhead grows, or when QA reports cross-platform regressions tied to engine differences, teams sometimes migrate the barcode layer to a single managed engine that behaves the same way on every target.

File Upload or PDF Processing Requirements Added

Mobile applications often begin with live camera scanning as the sole input method and later expand to accept uploaded images or documents. When a user needs to scan a barcode from a photo in their gallery, from an image received over email, or from a PDF containing shipment manifests or boarding passes, BarcodeScanning.Native.Maui does not have a code path for those inputs. Teams that reach this requirement boundary face a choice: add a second barcode library alongside BarcodeScanning.Native.Maui for file and PDF inputs, or migrate to a single library that handles all input types. Managing two barcode packages with different APIs and result types adds long-term complexity that a single-package solution avoids.

Server-Side Barcode Processing Introduced

Applications that scan barcodes on mobile often develop a server-side component — an ASP.NET API endpoint that validates barcodes, a background job that processes PDFs, or a cloud function that extracts tracking numbers from uploaded documents. BarcodeScanning.Native.Maui is a MAUI UI control library; it does not have a server-side implementation. A team that needs the same barcode reading logic on both mobile and server must use a different library for the server side. When the server-side requirement arrives, teams frequently evaluate whether consolidating to a single library that covers both mobile and server is preferable to maintaining two separate implementations.

UPC-A Data Normalization Becomes a Concern

The iOS UPC-A 13-digit behavior is not always caught during development. UPC-A barcodes scanned in development may appear to work correctly, but the leading zero from Apple's Vision framework can show up in the database when normalization is missing. Teams that discover 13-digit UPC-A values in inventory records, point-of-sale systems, or supply chain integrations may need both a code fix and a data correction step. Adding the documented normalization handles new scans; migrating to a library with consistent UPC-A output is sometimes preferred as a longer-term resolution.

PDF417 Document Scanning Required

PDF417 is the barcode format used in shipping labels, driver's licenses, and boarding passes in North America. These are common scanning targets for logistics, identity verification, and travel applications. BarcodeScanning.Native.Maui's GitHub issue tracker documents PDF417 as "very problematic — most scans never occur" on the iOS/Android engines. For applications where PDF417 reliability is a functional requirement, teams often evaluate alternative libraries.

Camera Event to MediaPicker and Static Read

The core structural change in migration is replacing the continuous camera event pattern with a MediaPicker capture followed by BarcodeReader.Read(). The OnDetectionFinished event handler, the CameraView XAML control, and the scanner: XML namespace declaration are all removed. In their place, a button triggers MediaPicker.CapturePhotoAsync(), and the resulting photo bytes are passed to BarcodeReader.Read(). This changes the user experience from a live continuous viewfinder to a system camera screen — appropriate for most business applications.

Thread Marshaling Changes

BarcodeScanning.Native.Maui fires OnDetectionFinished on a background thread, so all existing handlers that update UI elements wrap their updates in MainThread.BeginInvokeOnMainThread(). With the MediaPicker + async pattern used by IronBarcode, the continuation after await returns on the calling context, which is typically the main thread. In most cases the MainThread.BeginInvokeOnMainThread() wrappers can be removed, simplifying the event handler code.

UPC-A Normalization Removal

Any codebase that handled BarcodeScanning.Native.Maui's iOS UPC-A 13-digit behavior will have code that checks BarcodeFormats.Upca and calls Substring(1) to strip the leading zero. This code should be removed after migration — IronBarcode returns the standard 12-digit value, and leaving the normalization in place would incorrectly strip the first digit from valid UPC-A reads.

MAUI Permissions

BarcodeScanning.Native.Maui adds camera permissions to Android and iOS manifests automatically as part of its package setup. With IronBarcode using MediaPicker, the standard MAUI camera permissions in AndroidManifest.xml and Info.plist are required — the same permissions any MAUI app needs for MediaPicker.CapturePhotoAsync(). These permissions are typically already present in MAUI projects that use the camera for any purpose.