Customizing the Bitrix24 mobile app

Customizing the Bitrix24 Mobile App

The native Bitrix24 mobile application cannot be modified internally — it is a closed binary. Customization is possible through Mobile Applications (built-in web applications based on the JavaScript SDK) and through widgets — embeddable UI elements within standard CRM screens. The distinction is fundamental: a widget adds a button or block to an existing interface, while a mobile application is a separate screen with a fully custom UI.

Mobile Applications via JavaScript SDK

Bitrix24 provides the BX24.js SDK for embedded applications. In the mobile context, the application opens in a WebView inside Bitrix24. The SDK allows you to:

• Read and write CRM data via REST API
• Open standard Bitrix24 screens (BX24.openApplication())
• Retrieve authenticated user data
• Call REST methods: crm.deal.list, crm.contact.get, tasks.task.list

Example of a CRM call from a mobile application:

BX24.callMethod('crm.deal.list', {
    filter: { ASSIGNED_BY_ID: BX24.getAuth().user_id },
    select: ['ID', 'TITLE', 'STAGE_ID', 'UF_CRM_CUSTOM_FIELD'],
}, function(result) {
    if (result.error()) {
        console.error(result.error());
    } else {
        renderDeals(result.data());
    }
});

Mobile applications are published in the marketplace or installed locally (on-premise Bitrix24). Technically these are HTML/CSS/JS hosted on your server and registered under Settings → Applications.

Widgets in CRM

Widgets are the most common type of mobile customization. Widget placement options:

A widget is registered via placement.bind in the REST API:

BX24.callMethod('placement.bind', {
    PLACEMENT: 'CRM_DEAL_DETAIL_TAB',
    HANDLER: 'https://your-app.com/widgets/deal-tab',
    TITLE: 'Additional Data',
    DESCRIPTION: 'Delivery history',
});

Custom Business Process in Mobile

To automate actions from mobile (e.g., "Approve discount"), a combination is used: a button in a widget → REST call → launch a business process via bizproc.workflow.start. The user sees a button in the deal card, taps it — a BP starts on the server, the status changes, and a notification is sent to the responsible person.

White Label

For on-premise Bitrix24, it is possible to build a proprietary mobile application under the company's brand: Bitrix provides the option to recompile the application with a custom name, icon, and splash screen (White Label). Requires an Enterprise license and a separate agreement with 1C-Bitrix.

Case Study: Insurance Broker, Custom Agent Interface

Goal: agents work in the field from their phones; the standard CRM interface is cluttered — only 3 actions are needed: view a client, issue a policy, schedule a meeting.

Implementation:

• Mobile application (WebView) with a simplified interface: client list, policy issuance form
• CRM_CONTACT_DETAIL_TAB widget with policy history from an external database
• "Call" button in the widget opens a call via Bitrix24 SIP telephony
• Data is synchronized with the internal accounting system via REST API

Result: time to process an insurance event on-site reduced from 20 to 5 minutes; agents stopped keeping paper records.

What Is Included in Customization

• Mobile application (WebView) development with custom UI via the BX24 JS SDK
• Widget creation in CRM cards for the mobile interface
• Widget integration with external systems via REST API
• Configuration of business processes triggered from mobile
• White Label: assistance preparing assets for rebranding