Mobile Apps

B2B mobile apps are tools that give employees access to company data and functions outside the office — in the field, on a building site, at a client’s premises, between locations. Hexacode designs and builds apps for iOS and Android (React Native or native), with offline mode, integration with company systems, and post-publication maintenance.

When does your company need its own mobile app?

A mobile app makes sense when users need access to data and functions exactly where they work — in the field, between locations, outside the office. Not just because “everyone has an app”. A responsive website is enough for presenting an offer. An app is needed when a process requires interaction with company data in mobile mode — collecting information in the field, offline access to the system, real-time notifications.

Native vs. cross-platform — and why that’s not the most important question

We build apps in React Native — one codebase for iOS and Android, with native performance. But technology is a decision we make after analysing the process, not before. The more important questions are: who will use the app, under what conditions, what data they need at hand, and what happens when there’s no internet.

Offline mode and synchronisation are not a feature — they’re the foundation of a field app. We design offline-first architecture so users can work without a signal and data syncs automatically when connectivity is restored.

UX designed for real conditions

A B2B app used in the field is not the same as an app operated at a desk in an office. Conditions are different and the UX must account for that from the very first screen.

Readability in full sunlight — we design interfaces with high contrast and clear typography so that the screen is usable outdoors, not just in lab conditions. Key actions have large, unambiguous buttons with clear labels. Dark mode isn’t an aesthetic option — it’s a tool for improving visibility in specific lighting conditions.

One-handed operation — a technician in the field often has one hand occupied. Navigation, key actions, and the most frequently used functions are placed within thumb reach. Forms are designed to require a minimum number of steps: selections instead of typing, default values from context (location, date, assigned project), scanning a code instead of manual entry.

Unstable connection — the user shouldn’t have to think about whether they have internet. The app saves data locally, queues operations that require a network connection, and syncs them automatically once the connection is restored. If synchronisation encounters a conflict (e.g. the same record changed in the app and in the central system), the user sees a clear comparison of the differences and decides which version to keep.

Synchronisation and push notifications

Data synchronisation in an offline-first app requires a well-thought-out architecture. We design it using an operation queue: every user action (adding a record, changing a status, attaching a photo) is saved as an operation to be executed. When the connection returns, the queue processes automatically in the correct order, with retry handling for network errors.

Push notifications serve a different purpose in a B2B app than in a consumer one — the goal isn’t to engage the user, but to deliver critical information when it’s needed. A new job assigned to a technician, a change in order status, an alert when a threshold is exceeded, confirmation that a large data package has synced. Every notification is configurable — the user or administrator decides which alert categories should reach their phone.

The app as part of the system, not a standalone entity

Your mobile app needs to communicate with the rest of the company — CRM, database, custom system, external APIs. We design integrations from day one, so data flows between the app and company systems without manual transfer.

After publication on the App Store and Google Play, we take over maintenance — crash rate monitoring, system updates, new features in regular sprints. The same team that built the app is responsible for its stability.

Mobile data security

A mobile app operates outside the controlled environment of the company network — a phone can be lost, stolen, or used on an unsecured Wi-Fi network. We design security at the architectural level: encryption of data stored locally, enforced biometric or PIN authentication before accessing the app, automatic logout after a period of inactivity.

All server communication takes place exclusively over encrypted connections. Access tokens have a limited lifespan and are refreshed automatically. In the event of a lost device, an administrator can remotely wipe the app’s data without affecting the rest of the phone. These mechanisms are standard, not optional — in a B2B context, company data on a mobile device requires the same level of protection as data in a central system.

When doesn’t a mobile app make sense?

If the only argument for an app is “our competitors have one” — that’s not enough. An app generates ongoing maintenance costs: system updates, crash rate monitoring, adapting to new iOS and Android versions. If users don’t need offline access, push notifications, or data interaction in the field — a responsive website will do the same job for a fraction of the cost. We’ll tell you this directly at the first meeting.

Publication and the review process

Publishing an app on the App Store (Apple) and Google Play requires meeting detailed guidelines from both platforms — from technical requirements to the content of descriptions, screenshots, and privacy policy. We prepare a complete submission package: optimised screenshots, descriptions in the required format, answers to privacy and permissions questionnaires. We manage the client’s developer account and handle communication with the review teams of both platforms.

After the first publication, the cycle repeats with every update. We plan releases so they don’t conflict with periods of intensive use and so new versions pass review before the planned deployment date.

Case studies

An example of mobile API integration? HistoriaSzkod.pl — a platform handling thousands of requests daily, whose data reaches end-user apps. HR Event Management System with 24/7 mobile participant registration.