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, OnDetectionFinishedEventArgs e)
{
    var barcode = e.BarcodeResults.FirstOrDefault();
    if (barcode != null)
        ResultLabel.Text = barcode.DisplayValue;
}

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

Private Sub OnBarcodeDetected(sender As Object, e As OnDetectionFinishedEventArgs)
    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 genuinely good for consumer apps where "point and scan" is the primary interaction. The limitation is that this is the only interaction the library supports — the moment requirements extend beyond live camera detection on iOS or Android, BarcodeScanning.Native.Maui has nothing to offer.

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, Apple's Vision framework 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, OnDetectionFinishedEventArgs e)
{
    var barcode = e.BarcodeResults.FirstOrDefault();
    if (barcode != null)
        ResultLabel.Text = barcode.DisplayValue;
}

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

Private Sub OnBarcodeDetected(sender As Object, e As OnDetectionFinishedEventArgs)
    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, a Windows machine — none of these have a camera in the sense this library expects.

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 on iOS, Android, and Windows MAUI. 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 does not support the Windows target in MAUI. This is not a temporary gap — it is a structural consequence of the library's architecture. The library wraps iOS-specific (Vision framework) and Android-specific (ML Kit) native APIs. Windows has neither. Teams building a MAUI application that targets iOS, Android, and Windows — a standard multi-target scenario — cannot use BarcodeScanning.Native.Maui as the barcode solution for all three targets. They must either implement platform-specific code for Windows separately or replace the library entirely.

IronBarcode Approach

IronBarcode's BarcodeReader.Read() call works on Windows, iOS, Android, and macOS MAUI targets without any platform-specific code. 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) returns 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 without correction. Applications that store UPC-A values in a database may accumulate records with a leading zero that does not belong there.

The documented workaround requires checking the format and trimming the value:

// Workaround required for iOS UPC-A — strip the leading zero manually
private void OnBarcodeDetected(object sender, OnDetectionFinishedEventArgs e)
{
    var barcode = e.BarcodeResults.FirstOrDefault();
    if (barcode == null) return;

    var value = barcode.DisplayValue;
    if (barcode.BarcodeFormat == BarcodeFormat.UPC_A && value.Length == 13)
        value = value.Substring(1); // strip Apple's prepended leading zero

    ProcessBarcode(value);
}

// Workaround required for iOS UPC-A — strip the leading zero manually
private void OnBarcodeDetected(object sender, OnDetectionFinishedEventArgs e)
{
    var barcode = e.BarcodeResults.FirstOrDefault();
    if (barcode == null) return;

    var value = barcode.DisplayValue;
    if (barcode.BarcodeFormat == BarcodeFormat.UPC_A && value.Length == 13)
        value = value.Substring(1); // strip Apple's prepended leading zero

    ProcessBarcode(value);
}

' Workaround required for iOS UPC-A — strip the leading zero manually
Private Sub OnBarcodeDetected(sender As Object, e As OnDetectionFinishedEventArgs)
    Dim barcode = e.BarcodeResults.FirstOrDefault()
    If barcode Is Nothing Then Return

    Dim value = barcode.DisplayValue
    If barcode.BarcodeFormat = BarcodeFormat.UPC_A AndAlso value.Length = 13 Then
        value = value.Substring(1) ' strip Apple's prepended leading zero
    End If

    ProcessBarcode(value)
End Sub

This workaround silently breaks EAN-13 barcodes that begin with 0 if the format check is omitted. PDF417 is separately documented in GitHub issues as "very problematic — most scans never occur," affecting shipping labels, driver's licenses, and boarding passes.

IronBarcode Approach

IronBarcode returns the correct 12-digit UPC-A value without manual normalization. PDF417 is a supported format that reads reliably. 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 correct format handling removes a category of production bug that BarcodeScanning.Native.Maui leaves in application code. The IronBarcode barcode reading documentation covers format-specific behavior in detail.

Windows MAUI Target Added to the Build

MAUI applications commonly start with an iOS and Android target and later add Windows as the application matures or as enterprise distribution requirements expand. When the Windows target is added, BarcodeScanning.Native.Maui becomes an immediate blocker — there is no Windows implementation and no workaround within the library. Teams in this situation must either maintain a separate barcode implementation for Windows using a different library, or migrate the entire barcode layer to a library that works consistently across all MAUI targets. The second path is operationally simpler and eliminates the maintenance overhead of platform-specific branching.

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 has no code path to offer. 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, different result types, and different format support tables 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 UI control library that depends on a camera hardware context; it cannot run in a server process. 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 Accuracy Becomes a Production Issue

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 introduced by Apple's Vision framework shows up in the database. Teams that discover 13-digit UPC-A values in inventory records, point-of-sale systems, or supply chain integrations face a data correction problem in addition to a code problem. The workaround documented in BarcodeScanning.Native.Maui's GitHub issues corrects new scans but does not fix historical data. When the scope of the data quality issue becomes clear, migrating to a library that returns correct UPC-A values without application-level normalization is often the cleaner long-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." For any application where PDF417 reliability is a functional requirement rather than a nice-to-have, this known issue is a direct blocker that forces evaluation of 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 Workaround Removal

Any codebase that handled BarcodeScanning.Native.Maui's iOS UPC-A 13-digit behavior will have code that checks BarcodeFormat.UPC_A and calls Substring(1) to strip the leading zero. This code must be deleted after migration — IronBarcode returns the correct 12-digit value, and leaving the workaround 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.