Mobile App Development for Security Company
Security company app is not just CRM with assignments. It's a system where a 30-second push notification delay can mean a real incident without response. Alert delivery reliability and geo-tracking of units — that's what determines architectural decisions.
Three System Loops
Security app typically serves three user groups with different needs:
Client (Security Customer): request for security dispatch, location status (protected/withdrawn), alarm history, documents (reports, contracts), personal account with rapid response team contacts.
Security Guard on Location: patrol checklist with geolocation points, event logging (shift start/end, patrol completed, incident), emergency button, dispatcher communication, navigation to location.
Dispatcher: real-time map with current units, incoming alerts, unit assignment, event log.
Three separate interfaces — but one backend and, if desired, one Flutter app with profile switching.
Geolocation and Unit Monitoring — Technically Most Complex
Guard at location must periodically confirm presence in assigned geofence. Implement via background geolocation: flutter_background_geolocation (commercial plugin but the only reliable for iOS + Android with background mode) or geolocator with foreground service.
Without foreground service on Android with constant notification, background location dies in Doze Mode around third hour of shift — especially on Xiaomi and Huawei with aggressive battery policies. This isn't theoretical risk: we encountered this when developing app for shopping mall security. Solution — foreground service + wake lock + battery whitelist (with onboarding explaining what user needs to do).
Guard geolocation data writes to PostGIS (PostgreSQL) — allows building reports by shift trajectory, verifying patrol point completion via ST_DWithin.
Patrol points are geofences on location map. When guard approaches 10 meters — auto-mark. Optional NFC tag at physical point for additional confirmation (via flutter_nfc_kit).
Emergency Button
Guard alert must reach dispatcher as fast as possible. WebSocket (Laravel Broadcasting + Pusher or custom Socket.io) — 100–300 ms delay in normal conditions. FCM push — backup channel, but FCM doesn't guarantee second-level delivery.
For client emergency signal (panic button at location) — same, plus auto-create unit dispatch to nearest available rapid response group.
Integrations
- Integration with alarm systems (Bolid, C2000) via security monitor API — if security company wants sensor status visible in app
- Telephony via SIP (linphone_sdk) — dispatcher to guard communication without app exit
- Report and dispatch generation to PDF by template
Stack
Flutter 3.x + Clean Architecture (feature-first), Laravel 10 + WebSocket, PostgreSQL + PostGIS, FCM, Redis for real-time data.
Stages and Timeline
Analytics → design three role interfaces → UX/UI → development → geolocation scenario stress testing → publication → support.
MVP with unit geo-monitoring, emergency button, and client app — 18 to 24 weeks. Full system with alarm integration, SIP telephony, extended analytics — 32+ weeks.
Pricing is calculated individually after requirements analysis.