InsurTech Insurance Mobile App Development
An InsurTech app is three different products under one roof: online policy sales, claims handling, and customer portal. The most technically complex part is claims: damage photo capture, document uploads, claim statuses. This is where apps most often disappoint users.
Online Policy Issuance
The insurance calculator is the first screen for new users. Auto insurance: make, model, year, power, region, driving experience → cost. Liability: vehicle and driver data → premium.
Technically, this is a series of dependent requests: select make → load models → select model → load trims. Autocomplete with debouncing for database search. Cache reference data (makes, regions) for a day—they don't change hourly.
A long policy form breaks into steps with progress saving. The user stops at step 3 of 6—on return, they see saved data. UserDefaults / SharedPreferences for draft form data (non-sensitive), encrypted storage for passport data in temporary storage.
Document scanning: passport, vehicle registration—MLKit Document Scanner (Android) / VisionKit DataScannerViewController (iOS 16+). Auto-fill from recognized data reduces input errors.
Insurance Claim Handling
Here the user is stressed—accident, theft, emergency. The UI must be maximally simple and linear.
Damage photo capture is the key step. User photographs sequentially: overview, each damage, VIN, documents. Upload to S3 via pre-signed URL directly from the device—not through a server proxy. Progress bar per file. Retry on connection loss—Exponential Backoff with upload queue saved in Core Data / Room to resume after app close.
GPS coordinates of the incident location attach automatically. CoreLocation / FusedLocationProviderClient. Optionally, reverse-geocoded address (CLGeocoder / Geocoder).
Claim statuses: submitted → accepted → under review → additional documents requested → approved/rejected → paid. Push on each transition. "My Claims" screen: list with visual progress tracker.
Chat with claim manager is critical. Users can ask questions directly in claim context, not call a hotline. Stream Chat or Sendbird with thread pinned to claimId.
Personal Cabinet
List of policies: type, status, expiry date. 30 days before expiry—push "Your auto insurance ends soon. Renew?" with deep link to renewal screen.
Policy documents: PDF on device, available offline. Cache in Documents directory with freshness check by ETag / Last-Modified on next open.
Digital policy: QR with encrypted policy data. Relevant for liability—a traffic officer scans it. Data is server-signed, verification is offline.
External System Integration
RSA (Russian Auto Insurance Union) API checks CBM (bonus-malus coefficient). Request driver data → get class and coefficient → auto-apply to calculation.
Traffic Authority API checks vehicle by VIN/registration, accident history, restrictions. Data fetches automatically when VIN is entered in the issuance form.
Payment gateway: Stripe, YuKassa, CloudPayments. Card binding for auto-renewal—setup_intent (Stripe) / equivalent. On renewal, charge without re-confirmation—consent obtained during binding.
Security
Passport and INN data are encrypted in storage (iOS Keychain / Android EncryptedSharedPreferences). Never logged to Crashlytics. Certificate pinning for personal data API requests. Biometrics for login—standard for financial apps.
Stack
Native Swift (iOS) + Kotlin (Android) is preferred when integrating with fiscal APIs, government services, and complex document workflows. Flutter when time and budget are constrained, using flutter_secure_storage, camera, file_picker, FCM.
Process
Business analysis (policy types, underwriting rules, claims flow) → design → calculator and issuance → cabinet and documents → claims handling → RSA/Traffic Authority integration → payment module → testing → launch.
Timeline Estimates
MVP (one policy type, issuance, cabinet, basic claim submission): 8–12 weeks. Full InsurTech app with multiple insurance types, claims handling, document workflows, integrations: 4–7 months. Cost determined after requirements analysis.