Enterprise Mobile App Development
We develop enterprise mobile apps that connect task tracking, data collection and notifications to your existing systems for field sales, delivery and service teams. Platforms and offline scope are defined around your needs.
Who it is for
An enterprise mobile app brings tasks connected to company systems onto a phone. Internal mobile apps support approvals and notifications; field-team apps handle visits, deliveries and service records. Which operations can work offline is a separate scope decision.
When is it needed?
- Field sales: orders are written on paper and re-entered into the ERP at the office; representatives cannot see balances or stock.
- Delivery: delivery notes are signed on paper; the office confirms delivery only when the document returns.
- Service: work orders arrive by phone; completed work, parts and photos are stored separately.
- Warehouse and stocktaking: counting lists are on paper, with results entered into Excel in the evening.
When is it unnecessary?
- An off-the-shelf sales force automation (SFA) app is often sufficient if it fits your rules, ERP and offline needs.
- If the team is always connected and only fills in forms, a web application is more economical.
- If dealers will place their own orders, you need a B2B portal.
Scope
We agree the scope during discovery. The example below is a typical first release: a field app and an office administration panel. Offline operations, iOS/Android support, device features and distribution method are separate scope decisions in every project.
The day's work
A list of visits, stops or work orders; route, priority and change notifications.
Offline operation
Records are saved on the phone first, then sent in order when connectivity returns, without being processed twice.
Orders and forms
Customer-specific prices and discounts, payment collection, service and inspection forms.
Photos, signatures, barcodes
Proof of delivery and service; location, timestamp and e-Delivery Note number.
Administration panel
Web-based task assignment, current field status, users and reports.
Security and distribution
Role-based access, encrypted device data, app-store or internal distribution.
Outside this example's scope
- Dealer ordering app (B2B portal)
- Route optimisation (later stage)
- Device, mobile plan, MDM and app-store fees (charged directly to your accounts)
Assumptions
- This example targets iOS and Android; platforms, devices and supported versions are selected separately for the actual project.
- The ERP has an API or regular export capability and a test environment.
- Devices belong to the company and are, or will be, managed through MDM.
- A pilot team, such as one region, uses the first release.
How to choose the pilot team and first release: How do you define MVP scope?
Example scenarios
Explore the use cases
These examples plan for offline field data collection. During discovery, we distinguish steps requiring a connection, such as price validation, live stock checks and server approval.
-
Visits and orders
- Role
- Field sales representative
- Input
- Visit plan; the dealer's balance, payment terms, prices and promotions
- Action
- Orders can also be entered offline; those exceeding the limit go to the regional manager for approval.
- Output
- An ERP order, a summary for the dealer and updated sales-target status
-
Proof of delivery
- Role
- Driver
- Input
- Route, e-Delivery Note and items to deliver
- Action
- Counts, photos and signatures are captured in one flow; without connectivity, the record waits on the phone.
- Output
- Location- and time-stamped proof of delivery, shortage or damage record
-
Service visit
- Role
- Service technician
- Input
- Work order, service history and checklist
- Action
- The device is verified by barcode; work, parts and photos are entered into the form, then the customer signs.
- Output
- Service report (PDF), deduction from parts stock and invoice record
Example screens
Product concept: a solution study through interface designs, not an interactive demo or customer project. X Lojistik and X Dağıtım are fictional; the screen data is illustrative. All product concepts
Integrations
Integration details
The app connects to your ERP through a backend; only data needed for the user's work is downloaded to the device. We document flow directions and frequencies during discovery.
| System | Examples | Transferred data | Direction and frequency |
|---|---|---|---|
| ERP and accounting | Logo, Netsis, Mikro, SAP | Accounts, products, prices, stock, orders and payment collection | Master data to the device; orders to the ERP when connectivity returns |
| CRM | Salesforce, HubSpot, Dynamics 365 | Customers, visits and opportunities | Bidirectional, when records change |
| Electronic documents | Authorised e-document integrator API | e-Delivery Note, e-Invoice, e-Archive | Document number and PDF sent to the phone when created |
| Location | Phone GPS, vehicle-tracking API | Location and estimated arrival | Sent to the panel periodically during a task |
| Device management | Intune, Jamf or another MDM | Installation, configuration and remote wipe | On a new release and when a device is lost |
Which tasks can work offline?
Task notes, forms, photos and draft orders can be stored on the device. Current prices, stock reservations, credit limits or final order approval may require server validation. The interface distinguishes “on device”, “transferring” and “approved”; an offline record is not a completed transaction.
When connectivity returns, jobs enter the queue with persistent IDs. Retry counts and waiting times are limited; unresolved records are shown to the user. Resumable uploads for large files are planned separately according to device and server capabilities.
Details: How do you plan an ERP integration?
Product names are examples and do not imply a partnership.
Process
Steps in our process
-
01
Discovery
We join the team in the field and document forms, devices and places where connectivity drops.
1–2 weeks -
02
Definition & Prototype
The prototype is tested in the field with real users in week 3; the first-release scope is documented.
2–3 weeks -
03
Build
Weekly working-software demos; test releases are delivered to the pilot team's phones.
Two-week sprints,
first release target: weeks 6–12 -
04
Grow & Operate
Roll out from the pilot team to other regions in stages, measuring usage and adding modules.
Ongoing
This is an illustrative schedule assessed once access and pilot scope are clear; the final duration is determined during discovery. Step-by-step details: how we work
Budget and timeline
We do not publish a price list; offline behaviour and integrations affect cost more than the number of screens. You receive a written proposal after discovery.
- Platforms
- iOS, Android or both; tablets and handheld terminals.
- Offline operation
- Offline operations and conflict-resolution rules.
- Integrations
- Number of systems and API availability.
- Roles and screens
- User roles, forms and approval steps.
- Device features
- Camera, barcode, signature, location and mobile printer.
- Distribution and security
- App-store or internal distribution, MDM and KVKK.
- Discovery sprint
- 2 weeks Fixed scope, fixed fee
- First release
- 6–12 weeks A first release scoped together, rather than the entire project
- Other teams
- In stages Region by region after the pilot team
Delivery terms
Delivery and maintenance details
You remain independent of us: you hold the code, app-store accounts and keys.
Code and intellectual property
Transfer of project-specific code and designs, third-party licences and usage rights are defined separately in the contract.
App-store accounts
Apple and Google Play accounts are opened in your company's name from the outset.
Keys and infrastructure
The code repository, cloud infrastructure and app-signing keys are in your accounts.
Tests
Automated tests for critical flows; testing offline and on different devices.
Documentation and handover
Setup documentation and release notes are in the repository; code is handed over through joint sessions with your team.
Maintenance and releases
Compatibility with new operating-system versions, maintenance scope, support hours and release responsibility are agreed in writing.
Frequently asked questions
iOS or Android; native or cross-platform?
The devices your team uses guide the choice first. For most field apps, React Native or Flutter can cover both platforms from one codebase and make maintenance more economical. For hardware-intensive features such as continuous background location, extensive Bluetooth use or a handheld terminal's scanner, we write that component as a native Swift or Kotlin module.
How do we distribute the app to the team?
There are three routes: a public app-store release with access restricted to authorised users; a private app available only to your devices through Apple Business Manager and managed Google Play; or direct installation through the MDM managing your devices. Updates follow the same route through MDM or automatic updates, and users of unsupported old versions are directed to update. Accounts are registered to your company in every case. Organisation verification and distribution requirements vary by programme. Apple and Google Play organisation registration rules, D-U-N-S requirements and applicable exceptions are checked against current sources during discovery (checked: 11 October 2026).
Can we see your reference projects?
We present product concepts instead of a customer reference list: the driver app and field sales panel on this page are interface designs for fictional companies. To limit risk, we suggest starting with a fixed-fee discovery sprint or a pilot for one field team, with ownership of the repository and app-store accounts from day one.
What happens if the same record changes on the phone and in the office?
Example scenario: suppose the technician's phone holds version 7 of a work order, while the office cancels it in version 8. If the technician completes the work offline, reconnecting must not automatically mark the record “completed”. The server detects the version difference, preserves field notes and photos, and sends the status change to the responsible person as “awaiting review”. An authorised decision then produces a single final status with a recorded reason.
This is an example conflict rule; each field needs its own decision. Tests involving flight mode, closing and reopening the app, and resubmission check that notes survive, cancellation is not silently overwritten, and the same job is not duplicated. Uninstalling the app or clearing device data may delete records not yet sent to the server; this limitation and backup options are assessed separately. Android's official architecture guide also explains version information and application-specific conflict strategies for syncing offline changes (checked: 13 October 2026).
What happens if a phone is lost or an employee leaves?
The scope defines keeping only task-essential data on the phone, local encryption, device locking and offline-session duration. Server access can be revoked, but an offline device cannot be expected to learn this or receive a remote-wipe command immediately. If MDM support and connectivity are available, the wipe process is tracked separately. Google's device data-wipe documentation also explains the offline-device limitation. Preservation of pending records and the timing of local data deletion are tested together.
How are location tracking and KVKK addressed?
We recommend collecting location only during a task and for a defined purpose, such as delivery location or visit verification. We define and test rules that prevent collection outside working hours. During discovery, we identify which personal data is processed and why, the information needed for employee privacy notices, and the country where data is stored.
Can employees use their own phones?
Yes. In this case, company data stays within the app; personal photos, contacts and messages are not accessed. If device management is required, Android work profiles and iOS User Enrollment manage only work apps and data.
Next step
Tell us who will use the app and where. Let's review existing systems and connectivity conditions, then clarify the scope needed for a discussion or pilot.