topic hubAL Developmentofficial - Microsoftreviewed - checked by Opus

Developing for the Business Central mobile app

Developing for the Business Central mobile app (tablet and phone) with AL: strategy choices, screen size design, page limitations, role centers, barcode scanning, and browser-based testing. It answers questions about how to build and test mobile-friendly extensions.

Path: Development > Programming in the AL language > Pages and the user interface > Developing for the Business Central mobile app · tier official · system development · narrative reviewed (checked by Opus)

Overview

The Business Central mobile app gives small and medium-sized business users tablet and phone interfaces with touch-optimized design. It is meant for portable access and light data entry, and it does not replace the web client. Extensions for it use the same AL development framework, with extra care for smaller screens, touch input and role centers.

Start with the introduction and the get-started page, then read the strategy page to choose between platform-native AL development, a Power Apps connector, or OData/SOAP web services. Next, use the screen size and limitations pages to design pages that work on small devices. The Sales Rep Role Center walkthrough shows a practical tablet example.

For testing, you can open the tablet or phone client directly in a browser with URL parameters. This is for design-phase testing only, not a supported production scenario. The barcode scanning page covers camera and dedicated scanner capabilities through AL code and control add-in APIs.

Key points

  • Mobile extensions use the same AL development framework as the web client, with attention to small screens, touch and role centers.
  • Strategy options compared: Business Central platform development, Power Apps connector, custom connector, OData web services and SOAP web services.
  • Mobile page limits include no multiple selection, no FactBoxes on lists, no advanced filters, restricted action visibility and no worksheets.
  • Screen size guidance covers layout constraints, element counts per page type, activity tiles and list columns, with device emulation in Edge DevTools.
  • Tablet and phone clients can be opened in a browser by URL parameters (company, page, report, profile) for testing only, with multitenant support.
  • Barcode scanning works through the device camera or dedicated Android scanners, using UI buttons or programmatic calls, via control add-in and .NET-based APIs (versions 23.0 and 24 are mentioned).
  • A walkthrough builds a Sales Rep Role Center for the tablet client from existing pages and actions, including KPIs and sales quotes.

Learn pages

Videos and posts

Linked by a Haiku matcher with a grounding quote from the item’s summary (link/topics.ts); machine-generated.

Source: Microsoft Learn (CC BY 4.0). Descriptions are Learn’s own.

What Learn documents here 8 Learn pages