Imagine: an elevator installer receives a task to replace a cable. He needs to photograph the marking, measure the length, and mark completion. In Jira this is 5 clicks, but on site there are gloves and dirt.
You need an app with a single screen: task, "Complete" button, camera. And all of this must work without the internet, because underground parking garages and construction sites are areas with poor coverage.
Any delay derails the schedule, so synchronization must happen instantly after connectivity is restored.
We develop such apps turnkey. Over 7+ years of experience, we have delivered 50+ projects for construction, service, and logistics companies. We use Swift, Kotlin, Flutter, React Native — we select the stack for your task.
We guarantee stable operation even during connection drops: data is stored locally and synchronized when the network is restored. Notifications are delivered via FCM, Huawei Push Kit, and fallback WebSocket, so that no event is lost.
How does a mobile task management app solve the offline problem?
Offline mode is a key requirement for field employees. We use Hive (Flutter) or Room (Android) for local data storage. Synchronization when the network is restored is handled by background workers.
Conflicts during simultaneous changes are resolved using the LWW (Last Writer Wins) algorithm. This ensures that no action is lost, even if an employee completed a task in a basement without connectivity.
How do push notifications ensure task control?
Task assigned → assignee receives push with details. Deadline in 2 hours → reminder. Task overdue → notification to manager. Task completed → notification to customer or task creator.
This is a basic event-driven workflow, implemented via Firebase Cloud Messaging with priority: high for assignments and overdue tasks. Deadline reminders — a server-side Bull Queue scheduler.
Important consideration for B2B applications: an employee may have the app store blocked or use corporate Android (AOSP without Google Services). Then FCM does not work.
Solution — support for Huawei Push Kit (hms_push_kit) and fallback to WebSocket when the app is open, SMS for critical notifications.
What technical challenges do we overcome?
Main challenges:
- Offline work: field employees are often in areas without internet. We use Hive (Flutter) or Room (Android) for local storage, synchronization via background workers when the network is restored. We resolve conflicts using the LWW (Last Writer Wins) algorithm. This is critical so that a task is not lost during simultaneous changes.
- Media confirmations: the assignee attaches a photo with a geotag and timestamp. Compression to 1-2 MB, video up to 60 seconds with resumable upload. Checking the distance to the object:
distanceBetween < 500 m. This eliminates falsification. - Complex task hierarchy: project → stage → task → subtasks. We use event sourcing for audit and rollback of changes. Each change is saved as an event, which provides a complete history.
Thanks to offline mode and push notifications, our application delivers critical tasks twice as fast compared to similar solutions that work only online.
How do we work on your application?
- Analytics: we collect requirements, study business processes, and identify critical scenarios.
- Design: architecture (Clean Architecture), UI prototype, data model.
- Implementation: 2-week agile sprints, code review, unit tests.
- Testing: load testing, on real devices, beta testing via TestFlight / Firebase App Distribution.
- Deployment: publishing to App Store and Google Play, setting up CI/CD.
Architectural pattern: Clean Architecture with three layers (data, domain, presentation). Dependency injection — Hilt (Android) or GetIt (Flutter). Networking — Retrofit/Chopper, local storage — Room/Hive.
Technical specifications of the application
| Parameter | Value |
|---|---|
| Minimum iOS version | 15.0 |
| Minimum Android version | 9.0 (API 28) |
| Tablet support | Responsive layouts for iPad and Android tablets |
| Offline storage | Up to 10,000 tasks with media files |
| Push notifications | FCM + Huawei Push Kit + WebSocket/SMS fallback |
| Distributed teams | Support for multiple time zones and languages |
Why choose us?
Experience: 7+ years in mobile development, 50+ delivered projects. Expertise: we master Swift, Kotlin, Flutter, React Native, integration with 1С and enterprise systems. Guarantee: we provide a 12-month warranty on the code and fix bugs after release free of charge.
Comparison: integration with 1С via REST API reduces reporting time by 3 times compared to manual entry.
Development Timeline
| Scope | Functionality | Timeline |
|---|---|---|
| MVP | Tasks, statuses, push notifications | 6–8 weeks |
| Standard | + Media confirmations, offline, analytics | 12–16 weeks |
| Enterprise | + Integration with 1C, corporate SSO, MDM | 20–26 weeks |
The cost is calculated individually after the requirements are detailed. After project completion, you receive source code with comments, access to App Store Connect and Google Play Console, administrator and user instructions, as well as technical support for 3 months.
Updates for new OS versions are provided free of charge for six months. Contact us to discuss your project — we will estimate the timeline and cost.