Mobile CRM App Development from Scratch

We develop mobile CRM applications that solve real problems for sales managers. A standard CRUD interface over a database doesn't work here. Imagine: a manager is on the subway, the connection is unstable, and they urgently need to update a deal status. Without offline mode—you lose the client. Our team creates CRMs that work even on weak 3G and sync after network recovery. Over our time in the field we have released more than 20 mobile CRM solutions for various industries—from retail to logistics. We guarantee quality and hold Apple/Google developer certifications.

Why offline sync is critical for CRM

Offline mode is not an option but a requirement. The manager shouldn't wait for data to load. We use a local SQLite database with server-side conflict resolution. This speeds up work with client cards by 40% compared to an online-only approach. On Flutter we use drift (formerly moor) as a typed ORM on top of SQLite, and connectivity_plus to track network state:

// Save the action locally and enqueue for sync
Future<void> updateDealStage(String dealId, DealStage stage) async {
  await localDb.updateDeal(dealId, stage: stage, syncStatus: SyncStatus.pending);
  await syncQueue.enqueue(
    SyncOperation(
      type: OperationType.updateDeal,
      payload: {'id': dealId, 'stage': stage.name},
      createdAt: DateTime.now(),
    ),
  );
  // Trigger sync if network is available
  if (await connectivity.checkConnectivity() != ConnectivityResult.none) {
    syncService.flush();
  }
}

Conflicts arise when the same contact is edited from multiple devices. A 'last write wins' strategy corrupts data. The right approach: Last-Write-Wins at the field level rather than the record level—with updated_at on every mutable field, and a version vector for critical data. > "Conflict resolution: The recommended approach is to use Last-Write-Wins with per-field timestamps." — SQLite Documentation.

How to implement role-based access in a mobile CRM

Roles are the foundation of security and UX. A manager sees only their own clients; a supervisor sees the entire department. We implement this with Row Level Security on the server (PostgreSQL) and hide inaccessible actions on the client. On iOS we use the Keychain bound to the device—the token does not transfer to backups, which is essential for corporate security.

Telephony integration

The ability to call directly from a contact card is a standard mobile CRM feature. On iOS we use CallKit for native integration: a call via a VoIP provider (Twilio, Vonage) appears as a regular incoming call with the name from the CRM and is logged in the device call history.

// iOS CallKit provider
class CRMCallProvider: NSObject, CXProviderDelegate {
    func provider(_ provider: CXProvider, perform action: CXAnswerCallAction) {
        // Connect Twilio Voice SDK
        TwilioVoice.connect(with: connectOptions) { [weak self] call, error in
            guard let call = call else { return }
            self?.activeCall = call
            action.fulfill()
            // Log call start in CRM
            self?.crmService.logCallStarted(contactId: action.callUUID.uuidString)
        }
    }
}

On Android the equivalent is ConnectionService via TelecomManager.

Architecture and stack

For a cross-platform CRM application, Flutter is the optimal choice: one codebase covers iOS and Android, which is important given constantly changing business requirements. Architecture: BLoC + Clean Architecture, the repository layer isolates the local database and API. Flutter reduces development time by 30% compared to separate native apps, and a single codebase simplifies maintenance.

For native iOS or Android development—SwiftUI + Combine / Jetpack Compose + ViewModel respectively.

Working with push notifications

CRM events—scheduled meetings, new leads, overdue tasks—require push delivery in the background. On iOS UNUserNotificationCenter with content-available: 1 launches the app in the background to update data. A critical point: iOS gives background processes no more than 30 seconds, and too frequent background fetches lead to throttling by the system. Strategy: push only notifies about the event; heavy data is loaded lazily when the notification is opened. This architecture reduces battery drain by 25%.

What does the development process look like?

Requirements audit and data model design → design (if not already done) → parallel API and mobile client development → integration testing of sync with edge cases → testing on real devices with network loss simulation → publishing to App Store / Google Play → support. A mandatory step is load testing sync with a large database (10,000+ contacts). On low-end Android devices, SQLite operations on a large dataset without proper pagination and indexes cause ANR errors.

Timelines and budget

MVP with basic functionality (contacts, deals, tasks, offline): 8–12 weeks. Full-fledged app with telephony, integrations (email, calendar), advanced analytics: 4–6 months. Cost is calculated individually after requirements analysis. Contact us for a project estimate.

What's included in the work

• Architecture design and technology selection
• CI/CD setup, App Store/Google Play console configuration
• Documentation and code review
• Testing on real devices
• Post-launch support: 3 months free
• Training of the client's team

Our experience

Extensive experience in mobile CRM development with more than 20 completed projects. Apple and Google certified developers. We guarantee quality at every stage. Get in touch with us for a consultation—we'll assess your project within one day.

Mobile App Analytics: Firebase, Amplitude, AppsFlyer and Attribution

Our team regularly encounters projects where analytics is already "set up" but yields no real insights. A typical example is a startup with 50k DAU: tracking dozens of events without a single answer to the question "why don't users reach payment?". In two weeks we built a basic funnel and found that 70% of users drop off at the phone number verification screen. After fixing the bug, retention increased by 12%. The takeaway: analytics should start with specific questions, not tracking everything indiscriminately.

Why Event Taxonomy is the Foundation of Mobile App Analytics?

Firebase Analytics, Amplitude, Mixpanel — technically similar. The difference lies in what you put into them. A common mistake: events like screen_view, button_tap_1, button_tap_2 without context. A month later, no one remembers what button_tap_2 means.

Proper taxonomy: object + action + context. product_viewed, checkout_started, payment_completed with parameters product_id, category, price, source. This allows building funnels, cohort analysis, and retention without additional tracking.

We document the naming convention in a tracking plan — a document (Google Sheet or Amplitude Data Catalog) describing every event, its parameters, and triggering conditions. The tracking plan is synced with the analytics team before development begins, not after. This approach ensures that data remains interpretable months later and doesn't become a dump. Experience from 50+ projects confirms: without a tracking plan, analytics maintenance costs increase 2-3 times due to rework.

What Should You Choose for Mobile App Analytics: Firebase, Amplitude, or Mixpanel?

The table below highlights key differences between the three popular platforms. Choice depends on budget, traffic, and tasks.

Firebase Analytics — free, deep integration with Google Ads, BigQuery export for raw data. Limitations: data latency up to 24 hours, limited funnels. For startups with Google Ads traffic, it's the first choice.

Amplitude — product analytics focused on cohorts and user journeys. Journeys (formerly Pathfinder) shows actual paths between events — not assumed funnels but real routes. Session Replay records sessions for UX analysis. The free tier up to 10M events/month is enough for most products at launch.

Mixpanel — close to Amplitude, stronger in real-time segmentation. Insights, Funnels, Retention cover 90% of product analysts' tasks.

How to Solve Multi-Channel Attribution with AppsFlyer?

Knowing where a user came from is a separate task. Firebase Attribution works only within the Google ecosystem. For multi-channel attribution (Facebook Ads, TikTok, Apple Search Ads, programmatic), an MMP (Mobile Measurement Partner) is needed.

AppsFlyer is the market leader. OneLink — universal deep link working on iOS and Android, correctly attributing installs from any channel. Protect360 — built-in fraud protection (fake installs, click injection on Android). Adjust and Branch are competitors with similar features. Branch excels in deep linking; Adjust is popular in gaming.

According to Apple, with iOS 14.5, apps must obtain user permission via ATT before collecting IDFA for tracking. AppsFlyer uses probabilistic matching (IP + user agent + timing) for these users — accuracy is lower but better than nothing. SKAdNetwork and Privacy Preserving Attribution provide aggregated data from Apple with a 24-72 hour delay.

How to Set Up Crash Analytics to Not Miss Bugs?

Firebase Crashlytics is the standard for crash reporting. It automatically groups crashes by stack trace, shows affected users %, and sends velocity alerts when crash rate increases by more than 10% per hour.

Important: symbolication. On iOS, .dSYM files must be automatically uploaded with each build — via Fastlane upload_symbols_to_crashlytics or Xcode Cloud built-in. Without symbols, crashes in Crashlytics appear as memory addresses. This happens more often than expected when switching to a new CI — in one project with 500k users, we found that 40% of crashes remained unsymbolicated due to a missing CI/CD step. After automation, bug response time dropped from 3 hours to 15 minutes.

For React Native and Flutter, @sentry/react-native and sentry_flutter provide additional context: breadcrumbs, network requests before the crash, Redux/Provider state.

Below is a comparison of popular crash analytics tools to choose according to your needs.

Environment Setup

Three environments with separate Firebase projects: dev, staging, production. Mixing analytics from test sessions and production is a common mistake that skews all metrics. On iOS via GoogleService-Info.plist per scheme, on Android via google-services.json in each flavor folder.

Timelines: basic analytics with Firebase + Crashlytics — 3-5 days. Full tracking plan + Amplitude/Mixpanel with funnels and cohorts — 2-3 weeks. Attribution via AppsFlyer with deep linking and fraud protection — 1-2 weeks. Cost is calculated individually based on integration complexity.

What Is Included in Our Work

As part of analytics implementation, we provide:

• Development and approval of a tracking plan with product and marketing teams.
• SDK integration (Firebase, Amplitude, Mixpanel, AppsFlyer) considering your stack (Swift/Kotlin/Flutter/React Native).
• Setup of funnels, cohorts, dashboards, and alerts.
• Automation of symbolication and .dSYM upload via Fastlane.
• Documentation of events and parameters.
• Team training on the analytics platform.
• Two weeks of post-release support and tracking adjustments.

Our experience: 7 years of analytics implementation and over 80 successful projects in mobile development. We guarantee data correctness and transparency at every stage.

Contact us for a consultation on setting up analytics for your app. Request an audit of your current analytics — and we will show you which metrics you are losing.