Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Build guide

Building an omnichannel customer engagement app

In short

A customer engagement app joins messaging, campaigns, a chatbot, tickets and calls in one inbox. The hard part is structure: many workflows without a heavy app, plus reliable real-time messaging and calling on both platforms. A first release takes roughly 16-24 weeks.

Who this is for

Founders building a SaaS that lets businesses talk to their customers from one place, including voice calls from a mobile app.

What the product has to do

  • Unified inboxConversations from every channel in one list with owner, status and history.
  • Real-time messagingInstant delivery, typing and read states between agents and customers.
  • CallingVoice and video calls between people inside the app, with a native incoming-call screen.
  • CampaignsOutbound messages to segments of contacts, with scheduling and results.
  • Chatbot and automationAnswers common questions and routes the rest to a person.
  • ContactsCustomer records with tags, history and segments.
  • Support ticketsTurns conversations into trackable issues with assignment.
  • AnalyticsResponse times, volumes and campaign outcomes.
  • Media handlingVoice notes, images and video, compressed on the device before upload.

The stack, and why

LayerChoiceWhy
App frameworkFlutter and DartOne codebase for iOS and Android across a very large feature surface.
State and structureBLoC, get_it and clean feature boundariesWith so many features, structure matters more than any single library.
MessagingSocket.IOReal-time events with fallbacks and a simple server model.
CallingWebRTC with CallKitPeer-to-peer media with the native incoming-call screen on iOS. Today I would also plan a TURN relay and a call-quality dashboard from day one.
Push and servicesFirebasePush delivery and supporting services without running them yourself.

What ships first, and what waits

Version one

  • Unified inbox with real-time chat
  • Contacts and basic tickets
  • Push notifications
  • One calling path that is solid on both platforms
  • Basic analytics

Later

  • Campaign builder and scheduling
  • Chatbot and automation rules
  • Additional channels
  • Video calls
  • Advanced reporting

Build order and timeline

  1. 2-3 weeksScope and architectureChannel list, data model, real-time design and the first-release cut.
  2. 5-7 weeksInbox, contacts and messagingWorking inbox with real-time chat and push.
  3. 4-6 weeksCallingWebRTC calls with the native incoming-call experience on both platforms.
  4. 4-6 weeksCampaigns, automation and analyticsOutbound tools, chatbot hooks and reports.
  5. 2-3 weeksBeta and store releaseTested builds submitted to both stores.

Want a number for your own scope? The app cost calculator turns platforms and features into an estimate.

Rules you cannot skip

  • Background modes on iOS

    Apple allows background services only for their intended purposes, with VoIP among those listed. Declare VoIP only if the app really makes calls.

    Official source
  • Calling and microphone use on Android

    For Android 14 and higher you must declare a foreground service type for each service, such as microphone or phone call, and explain the feature, the effect of delays and show a video in Play Console.

    Official source
  • Foreground service declaration

    Each declared foreground service type needs a description of the feature, the impact on users if it is paused and a link to a video of how it is triggered.

    Official source
  • Consent for collecting data

    Apple requires consent before collecting user data and an easy way to withdraw it, with clear purpose strings for microphone and camera access.

    Official source

Where these projects go wrong

  1. Feature sprawl

    Messaging, automation and reporting in one product can make the app feel heavy. Keep clear boundaries between features and ship channels one at a time.

  2. Calls that work on one platform only

    Incoming-call behaviour is different on iOS and Android and depends on push delivery. Test on real phones, locked, in the background and on poor networks. Read Apple's current PushKit and CallKit documentation before designing call notifications.

  3. State management chaos

    A large app without strict structure turns into tangled state. Fix the architecture before adding features.

  4. Heavy media

    Uploading raw video and voice notes burns data and time. Compress on the device.

  5. Notification overload

    A busy inbox without sensible grouping and mute rules wears people out and causes uninstalls.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

Problems you will meet on this stack

Next step

Have a product like this in mind?

Send me a few lines on what it must do. A discovery call within 48 hours.