I’ve been watching companies buy expensive third-party mobile applications for Business Central for years now, and I keep asking myself: why?

I get it—old habits die hard. For decades, if you wanted warehouse staff scanning barcodes or shop floor workers capturing production data on a tablet, you had to buy something from an ISV. That’s just how it was. But somewhere around Business Central version 23, that stopped being true. Microsoft gave us native barcode scanning, tablet support, and AL extensibility in the standard mobile app—and most people are still acting like it’s 2015.

I just came back from the Community Summit North America and it is painful to hear people talk about the dinosaur mobile solutions like there are no alternatives. This made me go home and write this blog, I felt obligated to try to let people know that there is a better alternative.

We’re now in the era of fourth-generation mobile solutions for Business Central, and if you’re still evaluating (or worse, buying) third-generation apps, you’re solving yesterday’s problem with yesterday’s tools.

Let me walk you through why the native Business Central app is not just “good enough”—it’s actually better than most of what’s out there.

The Four Generations of Mobile Solutions in Business Central

Here’s how we got here:

1st Generation: ADCS (Automated Data Capture System)

This was the Navision-era solution for warehouse scanning. You had a server component, terminal emulation software, and a bunch of configuration that only worked if you had exactly the right hardware and a consultant who’d done it before. It worked, but it was clunky, hard to troubleshoot, and nearly impossible to extend without rewriting chunks of it. I found the below screenshot from an installation document I had from 2006 (and it felt old already then). I implemented this several times back in the days, took many days to just install it all.

2nd Generation: IIS-Based Web Pages on Mobile Browsers

In the mid-2000s, companies started building mobile solutions by hosting ASP.NET or similar web pages via IIS, which you accessed through a browser on the mobile device. It was better than ADCS because you could use cheaper hardware, but the user experience was rough—tiny buttons, pages that didn’t scale, constant scrolling. It felt like using a desktop application through a keyhole. And it took a team of different people to install and maintain, you needed an expert on IIS, a Navision expert, a device expert and a network person. They looked much better than the ADSC, but I don’t remember anyone being happy with this type of solution.

3rd Generation: Dedicated Mobile Apps (Usually with Web Services)

This is where most ISVs live today. They build a custom Android or iOS app, connect it to Business Central via web services (SOAP, OData, or REST APIs), and give you a mobile UI designed for warehouse or manufacturing workflows.

Some of these are genuinely good products. But I’ve also seen solutions that:

• Send data back and forth in XML files stored on network shares (I’m not making this up)
• Require middleware servers that need their own updates and maintenance
• Break every time you upgrade Business Central because the APIs changed
• Cost as much per year in licensing as a mid-sized car
• Can not easily be customized or extended without involving the vendor

And yet, people keep buying them. I think it’s because they don’t realize there’s a better option out there.

4th Generation: The Native Business Central Mobile App

Since Business Central 2023 release wave 2 (version 23), Microsoft has included native barcode scanning in the mobile app. It works on supported phones and tablets using the device’s camera or a dedicated Android barcode scanner device.

More importantly, the mobile app is fully extendable using AL—the same modern development language you use for all Business Central customizations. You write your extensions in Visual Studio Code, publish them to your tenant, and they just work in the mobile app. No middleware. No separate licensing. No XML files flying around your network.

This is the generation you should be on.

What You Can Do with the Native Business Central Mobile App

Let me be specific about what this looks like in practice.

Barcode Scanning (Camera or Dedicated Scanner)

The barcode scanning capability supports several of the most common 1D and 2D barcode formats, including QR code, Data Matrix, UPC A, UPC E, EAN 8, EAN 13, Code 39, Code 93, Code 128, Codabar, ITF, and PDF 417. And I have also seen RFID readers work with this.

You have three ways to implement scanning:

1. Simple UI button on a field

Set the ExtendedDatatype property to Barcode on a field, and the mobile client displays a barcode button when the page opens on a supported device. Once scanned, the value enters the field and focus moves to the next quick-entry field. This is perfect for scenarios like scanning item numbers during physical inventory counts.

That’s it. One property. The mobile app handles the rest. This adds the below icon and you can now scan with the camera.

With the above you can use any phone or regular tablet to scan barcodes, no need for special devices. Why are not everyone doing this?

2. Invoke scanning programmatically from AL

You can trigger the scanner when a page opens, when a user selects an action, or based on any other event you code. This is useful for guided workflows—like scanning a production order barcode to open the output journal.

This is describe by Microsoft here, it seems complicated but once you done it one time it is easy, and if you need help creating this you can just ask your Copilot GitHub Agent to do it for you, Vibe Coding, or?. 🙂

3. Integrate dedicated barcode scanners

Professional hardware scanners, like Zebra or Datalogic, can communicate with the Business Central mobile app by emitting Android Intent messages for every scanned barcode. This is the option for high-volume warehouse environments where speed and durability matter. Your warehouse staff scan items continuously, and the app processes incoming barcodes in the background—no UI interaction required.

I’ve seen implementations where a Zebra scanner on a forklift sends dozens of scans per minute into the BC app without the driver ever touching the screen. It’s fast, it’s reliable, and it doesn’t require a separate software license. Plug and play is back!

Tablets and Touch-Optimized Pages

The BC mobile app works beautifully on tablets. You can design pages specifically for touch input—bigger buttons, fewer fields per screen, quick-entry flow. Use the same AL page extensions you’d write for the web client, just optimized for mobile use.

I recently helped a client build a shop floor data capture solution on Samsung tablets mounted next to production lines. Workers scan a barcode on their job card, the production order opens, they enter output quantity and scrap, and they’re done. The whole interaction takes less than 30 seconds, and it’s all standard BC mobile app with AL extensions.

Below is how our own Shop Floor application looks like on a table for example. Built using 100% AL code in Visual Studio, it combines my Shop Floor Barcode System, some Shop Floor Terminal features, a nice BarTender Integration, Time Capture functionality, etc.. into one mobile application. I should probably write another blog post just about what we have done in our Naviona Shop Floor & Warehouse Mobile application, there are soo much goodies in it, stay tuned. 🙂

Full AL Extensibility

This is the part that makes the 4th generation truly superior: you extend the mobile app the exact same way you extend Business Central.

Using Visual Studio Code and the AL Language extension for Microsoft Dynamics 365 Business Central, you can create new files, use code snippets, receive compiler validation while you code, and publish by just selecting Ctrl + F5.

Your mobile customizations live in the same extensions as the rest of your Business Central code. Same development environment. Same version control. Same deployment process. When you upgrade Business Central, your mobile extensions upgrade with it—no separate vendor, no separate contract, no “mobile module” surcharge.

Compare that to a third-party mobile app where you’re paying annual fees, waiting for the vendor to support new BC versions, and hoping they don’t go out of business (I have seen that happening too sadly).

Why the Native App Is Superior to Third-Party Solutions

Let me be opinionated for a moment: if you’re buying a third-party mobile app in 2026, you’re probably making a mistake.

Here’s why the native BC mobile app wins:

1. It’s Included

You already have it. It’s part of your Business Central. No additional fees, no “warehouse module” add-on, no extra service, etc. that might be needed for a separate dinosaur ‘mobile’ application.

2. It’s Extendable in AL

You can extend tables, pages, reports, code flows, and the security model directly in AL. If you need custom logic for validating scanned lot numbers, auto-creating picks, or enforcing business rules, you just write AL code. If you can customize BC, you can customize the mobile experience. Your imagination is the limit. 🙂

3. It’s Upgrade-Safe

Third-party apps often lag behind BC releases. I’ve seen clients stuck on an old BC version because their mobile app vendor hasn’t certified the new version yet. With the native app and AL extensions, you upgrade BC and everything comes with it.

4. It’s Maintained by Microsoft

Microsoft is actively improving the mobile app. Business Central version 24 introduced barcode scanning APIs based on control add-ins to replace .NET-based APIs, supporting both online and on-premises scenarios. They’re investing in this—it’s not abandonware.

5. No Middleware

Many third-party solutions require a middleware layer—an app server, a synchronization service, something running on a VM somewhere that you have to maintain. The native app talks directly to Business Central. One less thing to manage, patch, and troubleshoot.

6. Modern Development Experience

When you extend the mobile app in AL, you get all the benefits of modern development:

• IntelliSense in Visual Studio Code for code completion
• Built-in snippets to speed up coding
• Compiler validation while you type
• Integrated debugging with Ctrl + F5 publish and run
• Version control with Git
• AI-assisted coding with Copilot or other AL coding agents

This is light-years ahead of the old C/SIDE days or dealing with proprietary development tools from ISVs.

When You Might Still Need a Third-Party Solution

I’m not saying third-party mobile apps are never the answer. There are edge cases:

• True offline warehousing: If your warehouse literally has no reliable connectivity and you need workers to scan thousands of items while offline, a purpose-built offline-first app might be necessary.
• Complex, multi-tenant ISV scenarios: If you’re a software vendor building a vertical solution that spans multiple BC tenants with unique mobile workflows, a custom app might make sense.
• Legacy integrations: If you’re already deep into a third-party WMS ecosystem that includes mobile capabilities, switching might not be worth the disruption.

But for most companies – the native BC app is the right choice. And it is a proven solution.

How to Get Started

If you want to try this out, here’s the simplest path:

For Basic Camera Scanning:

1. Install the Business Central mobile app on an Android or iOS device (search “Business Central” in the app store, or visit https://aka.ms/bcmobileapp). You can do this on your phone.
2. Log in with your Business Central credentials.
3. Open a page like Physical Inventory Journal or Item Journal.
4. Look for fields with the barcode button icon next to them (standard BC includes this on Item No. fields in journals).
5. Tap the barcode button and scan something with your camera.

That’s it. You’re scanning barcodes in Business Central.

For Dedicated Scanners (Zebra, Datalogic, etc.):

1. Ensure your scanner runs Android 11 or later and has the BC mobile app installed.
2. Configure the scanner to emit Android Intent messages (usually through DataWedge on Zebra devices or similar configuration tools on other brands).
3. Set the Intent settings to match BC’s expected values (broadcast intent mode, specific action and category strings).
4. Create an AL extension using the BarcodeScannerProviderAddIn control add-in to intercept scanned barcodes.
5. Test and deploy your extension.

For Custom Mobile Pages:

1. Set up Visual Studio Code with the AL Language extension.
2. Create a page extension or new page optimized for mobile use (fewer fields, larger touch targets, quick-entry flow).
3. Add barcode fields using ExtendedDatatype = Barcode where needed.
4. Write AL code to handle validation, auto-population, or custom business logic.
5. Publish to your BC environment and test on your mobile device.

Important: Mobile device must be using Business Central mobile app version 4.0 or later for barcode scanning to work. To download the latest version, go to https://aka.ms/bcmobileapp.

Real-World Example: Shop Floor Production Reporting

Let me give you a concrete example of what this looks like in practice.

A client of mine manufactures custom industrial equipment. They have 12 production lines, each with a wall-mounted Samsung tablet running the BC mobile app. Here’s their workflow:

1. Worker scans the barcode on their job card (printed on the production order)
2. The AL extension intercepts the scan and opens the Production Journal for that specific order
3. Worker enters output quantity, scrap (if any), and hours worked
4. Hits Post
5. Done

The entire interaction takes 20-30 seconds. No logging into a separate system. No manual lookup of the production order number. No transcription errors.

We built this using:

• Standard BC mobile app (free)
• Three AL page extensions (written in VS Code)
• One codeunit for barcode logic (about 150 lines of code)
• Samsung tablets ($300 each)
• Barcodes printed on production order travelers (Code 128, generated by an AL report extension)

Total development time: About 8 hours for the initial build and testing, plus an hour or two for some training.

Compare that to the quote they got from a third-party mobile vendor: tens of thousands for licensing and implementation, plus thousands per year maintenance. The ROI was obvious.

The Technical Reality: What Works and What Doesn’t

I want to be honest about the limitations I’ve encountered:

What Works Great:

• Camera scanning for ad-hoc use (physical inventory, receiving, quick lookups)
• Dedicated Android scanners for high-volume warehouse work
• Custom pages designed for tablets (production reporting, quality checks)
• Integration with standard BC processes (journals, documents, orders)
• Extending functionality with AL code

What’s Still Tricky:

• Zebra scanner configuration: The DataWedge setup can be finicky. Microsoft’s documentation covers it, but expect some trial and error.
• iOS scanner support: Dedicated hardware scanners work best on Android. iOS is more limited to camera scanning.
• Offline scenarios: The mobile app has some offline capabilities, but it’s not as robust as purpose-built offline-first apps. If you have warehouses with truly no connectivity, this might still be a gap.

But here’s the thing: even with these limitations, the native app covers 90% of mobile use cases I encounter. And when you hit an edge case, you can often solve it with AL code rather than buying a whole new product.

A Word About ADCS (For the Historians)

Some of you reading this might still have ADCS implementations running. If it works, and you’re not paying much to maintain it, there’s no urgent reason to rip it out. But if you’re troubleshooting ADCS issues in 2026, or if that one person who understands it is about to retire—now is the time to migrate.

The native mobile app does everything ADCS did, but better. And you can build it yourself instead of relying on increasingly scarce ADCS expertise.

My Take: Stop Overthinking Mobile

For 20+ years, mobile data capture in NAV/BC was hard. You needed a third-party solution, and you needed a specialist to implement it. That shaped how we think about mobile.

But the world changed. The native BC mobile app, combined with AL extensibility, gives you 90% of what most companies need – and you already own it.

I’m not anti-ISV. Some of those third-party apps are excellent, and their vendors do great work. But I’ve also watched clients spend $50,000 on a mobile solution that they could have built in AL for a fraction of the cost.

If you’re evaluating mobile options for Business Central today, start with the native app. Extend it with AL. See how far you get. If you hit a wall, then consider third-party tools. But I bet most of you won’t hit that wall.

We’re in the fourth generation now.

What to Watch Next

Microsoft continues to improve the mobile app with each release. I’m particularly interested in seeing how they integrate Copilot capabilities into mobile workflows—imagine scanning an item and having Copilot suggest bin locations or alert you to stock issues in real time using AI reasoning.

If you’re doing interesting things with the BC mobile app and AL extensions, I’d love to hear about it. Drop me a note – I’m always curious how people are solving real problems with this.

Resources

Microsoft Learn Documentation:

• Barcode scanning in mobile app
• Developing extensions in AL
• Get started with AL
• Download the Mobile App: https://aka.ms/bcmobileapp