Customization of Bitrix24 Mobile App
Imagine fifty agents in the field, each opening CRM on their phone—and seeing twenty tabs, when only three are really needed. Switching between them takes up to thirty seconds per action, and over a day that adds up to an hour of downtime. We solve this by customizing the Bitrix24 mobile app in two ways: widgets (embedded UI elements, loading in 200 ms) and web applications via JavaScript SDK (full screens in 2–3 seconds). The choice depends on the scenario: for quick actions (call, status change) — widgets, for complex forms (order processing) — web apps. Savings after deployment can be substantial for a team of 50 employees.
What customization methods are available?
Web applications via JavaScript SDK. The platform provides the BX24.js SDK for embedded apps. In the mobile context, the app opens in a WebView inside the system. The SDK allows reading and writing CRM data through the REST API, opening standard screens, getting user data, and calling methods like crm.deal.list, crm.contact.get, tasks.task.list. Example API call from a mobile app:
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()); } }); Web applications are placed in the marketplace or installed locally (on-premise version). Technically, they are HTML/CSS/JS hosted on your server and registered in the "Settings → Applications" section.
Widgets in CRM. Widgets are the most popular customization type. They run 3 times faster than full web apps because they don't require a complete reload. Widget placement:
| Placement Location | Widget Type | Use Case |
|---|---|---|
| Deal card | CRM_DEAL_DETAIL_TAB | Additional tab with data |
| Contact card | CRM_CONTACT_DETAIL_TAB | Interaction history |
| Deal list | CRM_DEAL_LIST_TOOLBAR | Quick action buttons |
| Call card | TELEPHONY_CALL_CARD | Customer info during call |
Widgets are registered via placement.bind:
BX24.callMethod('placement.bind', { PLACEMENT: 'CRM_DEAL_DETAIL_TAB', HANDLER: 'https://your-app.ru/widgets/deal-tab', TITLE: 'Additional Data', DESCRIPTION: 'Delivery history', }); How to run a business process from mobile?
Combination: button in widget → REST call → start BP via bizproc.workflow.start. The user presses a button in the deal card, the server starts a business process, changes the status, sends a notification. In 2 days we implement the chain: task list, approval, document sending.
Step-by-step guide:
- Develop a widget with an "Approve" button and register it on the deal card.
- In the widget handler, call BX24.callMethod('bizproc.workflow.start', { ... }) with template parameters and deal ID.
- On the server, the business process runs 5 steps: condition check, deal status change to "In Progress", send notification to manager, write to history, notify client.
- After completion, the mobile app receives the response and updates the interface.
White Label: your own branding
For on-premise platform, White Label is available—building your own branded mobile app. The system allows recompiling the app with custom name, icon, and splash screen. Requires an Enterprise license and a separate agreement with 1C-Bitrix. We help prepare resources: icons in 5 resolutions, splash screens for 3 resolutions, build configuration.
Case study: insurance broker, custom agent interface
Details from our practice
Challenge: 50 agents work in the field with phones; the standard CRM interface forced them to scroll through 4 screens to process an insurance event. Only 3 actions needed: view client, issue policy, schedule meeting. Monthly time loss was significant.
Solution: We developed a web application (WebView) with a simplified interface, a CRM_CONTACT_DETAIL_TAB widget showing policy history from an external database, a "Call" button via the system's SIP telephony, and synchronization with the internal accounting system via REST API.
Result: Time to process an insurance event on-site dropped from 20 to 5 minutes (75% savings). Agents saved an average of 3 hours per day, paper records disappeared. Cost per policy reduced by 80%, leading to annual savings.
| Stage | Duration |
|---|---|
| UX design and interaction flows | 2 days |
| WebView app development | 5 days |
| CRM card widgets | 3 days |
| Integration with external accounting system | 4 days |
| Deployment and testing on devices | 2 days |
Timelines and pricing
Development timelines depend on complexity: MVP (minimum viable product) — from 5 days; standard project with web app and several widgets — from 10 to 20 days; comprehensive customization with White Label — up to 30 days. Cost is calculated individually after auditing your business processes and approving the technical specification. Payback period for customization is 3–4 months due to reduced deal processing time.
What is included in the work
Within the project we provide:
- Technical specification with architecture description, screen prototypes, and your approval.
- Source code of web apps and widgets registered in your system.
- Documentation for REST methods and usage scenarios.
- Installation and configuration guide, including access rights.
- Testing on real devices (iOS, Android) and bug fixing.
- Support for 30 days after delivery (consultations, adjustments as agreed).
Every project starts with an audit of current processes. Get a consultation—we'll assess your scenario in 1 day. Contact us to discuss architecture and timelines. Order customization of your mobile app—start with an audit.