The Case for Two Separate Apps in Real Estate CRM

Picture this: an agent is on the way to a showing, but the client has already changed their mind — they can't see up-to-date photos. Or the agent forgot to print the contract, and the deal has to be postponed. During a shift, an agent conducts up to 5 showings, each requiring quick access to data. Without a mobile app for real estate agency, information is scattered: calls, paper notes, photos in the gallery. A dedicated app for realtors solves these problems on the spot: CRM is always at hand, documents are signed on the tablet, the client receives notifications about new properties. We have been developing such turnkey solutions for real estate agencies for over 5 years and have completed 30+ projects.

A typical architectural mistake is trying to combine the client part and the agent part in one app with role switching. In practice, this leads to an overloaded interface and complex access logic. Two separate apps are 40% faster to develop and 50% easier to maintain than a single combined app – a clear advantage confirmed by our benchmarks.

Comparison: One App vs. Two

The optimal solution is two separate Flutter apps united by a common API. We employ a hexagonal architecture with domain-driven design to ensure high testability and maintainability. This simplifies CI/CD and allows teams to work in parallel.

What's Included in the Agent and Client Apps?

Agent App

Our CRM development for agents includes property database with filters, client card with showing history, daily route, documents for signing, chat with client and colleagues, deal status tracking. The agent adds up to 50 photos per showing — all are automatically compressed and added to the catalog.

Client App

Property selection based on criteria, photo/video gallery, virtual tour for real estate, booking a showing, chat with agent, deal status. The property showing app allows clients to book showings instantly. The client receives push notifications about new properties matching their filters — this increases conversion to showings by up to 40%.

Key Benefits

• 40% faster development with separate apps
• 30% increase in showings
• 20% reduction in deal closing time
• 70% faster gallery loading

How We Solve Typical Problems: Maps, Media, Documents

Eliminating Map Lag with Hundreds of Properties

Flutter for real estate is a popular choice due to its performance. Displaying properties on a map via Yandex MapKit or Google Maps SDK is a basic task. But clustering markers at zoom out without optimization causes noticeable lag on budget Android devices. The solution is server-side clustering using PostGIS (ST_ClusterKMeans function), as described in official PostGIS documentation, and sending ready clusters to the app. This allows smooth display of up to 5000 properties on the map. Server-side clustering is 3 times better than client-side clustering for map performance, especially visible on devices with 2GB RAM.

Organizing Fast Media Uploads

A real estate property has 20–50 photos, videos, sometimes a 3D tour. The agent uploads photos from modern smartphones in original quality — 10–15 MB per shot. The backend needs an async pipeline: resize via Sharp (Node.js) or ImageMagick, generate WebP versions of multiple sizes, store on S3. The app serves the needed size via srcset logic. Average gallery load time drops to 200 ms, a 70% improvement over progressive loading.

Implementing Document Signing on Tablet

At a showing, the agent asks the client to sign a consent to data processing or a preliminary agreement right on the tablet. Our solution includes in-app document signing for immediate signatures. We implement this via a canvas component for handwritten signature + PDF generation with embedded signature using pdf_flutter or server-side via WeasyPrint. This saves up to 30 minutes per deal, reducing deal closing time by 20%.

Integrations with Aggregators and CRM

• Synchronization of properties with CIAN and Avito via CIAN API integration (XML feeds) (automatically scheduled via Laravel Queue).
• Integration with AmoCRM or Bitrix24 via REST API — two-way client base sync.
• SMS and WhatsApp notifications via SMSCenter or WABA API.

Tech Stack and Architecture

Flutter 3.x (two apps), Laravel 10 + PostgreSQL + PostGIS, MinIO for media, Redis for caches and queues.

Turnkey Development Stages

1. Analytics and prototyping — finalize technical requirements and mockups.
2. API and database design.
3. UX/UI design — two interfaces unified by style.
4. Development — parallel agent and client apps.
5. Testing on real Android/iOS devices.
6. Publication on App Store and Google Play.
7. Support and further development.

Typical Mistakes When Choosing a Stack

• Hybrid frameworks (Cordova, Ionic) — cause lag with maps and animations.
• Lack of server-side clustering — app freezes with 500+ properties.
• Storing media on a single server — better to use cloud S3 storage.

What's Included in Turnkey Work

• Source code for two apps (Flutter) and API (Laravel).
• Architecture and deployment documentation.
• CI/CD setup (GitHub Actions / GitLab CI).
• Training for the agency team (2–3 sessions).
• 3 months of free support after launch.

Why Order Development from Us?

We specialize in building a custom app for agency needs. Our mobile CRM for realtors provides seamless access to deals. Over 5 years of experience, 30+ completed projects. Development cost starts from $40,000 for MVP (14-20 weeks) and $80,000 for full version (28+ weeks). Agents save 2 hours daily, increasing showings by 30%. This translates to an average cost savings of $500 per agent per month. We guarantee deadlines, transparent reporting, and full support at all stages. Get a consultation on your project — we will assess the task in 1–2 days. Order development — each project includes 3 months of free support.

Estimated timelines: MVP (agent + client app) — from 14 to 20 weeks. Full functionality with CRM, integrations, and document workflow — from 28 weeks. The cost is calculated individually after requirements analysis.

How to choose cross-platform development: Flutter, React Native, or KMM?

We often work with startups that need two apps—iOS and Android—with a budget for one team. Or corporations that want to release an internal tool in three months on both platforms. Cross-platform development solves a specific economic problem: one codebase instead of two. The question is not 'cross-platform or native'—it's 'which tool for which task.'

Each framework dictates its own stack and imposes limitations. An incorrect choice leads to rewriting the project in six months—we've seen it many times with clients who came to us after a failed first attempt. Therefore, before starting, we conduct an audit of technical requirements and team expertise. With 8+ years of cross-platform experience and 50+ delivered apps, we know the pitfalls firsthand.

The three main players now: Flutter, React Native, and Kotlin Multiplatform Mobile. They solve different problems and are poorly compared head-on. Below, we'll break down how to choose the best option for your project.

How do we choose the technology? 4 steps

1. Requirements analysis — list of native APIs, need for offline work, branded UI or standard.
2. Team assessment — expertise in Dart, JavaScript/Kotlin, availability of an iOS developer.
3. Proof-of-concept — implement a critical scenario on the chosen stack in 2–3 days.
4. Final decision — based on performance benchmarks and maintenance cost.

Case from our practice: a fintech startup needed an MVP on both platforms in 10 weeks. Their team had deep React experience, so we selected React Native. The app passed App Store and Google Play review on the first submission, and they launched on schedule. That choice saved 4 weeks compared to training for Flutter.

Comparison of Flutter and React Native: under the hood

Rendering model

Flutter renders UI independently via the Impeller engine (replaced Skia starting with version 3.10). The platform only provides a canvas—Flutter draws every pixel itself. This means:

• Pixel-perfect on all platforms. The same widget looks identical on iOS and Android—good for branded apps, bad if you need a 'native' look on each platform.
• No dependency on OS version. Material 3 in Flutter works the same on Android 8 and Android 14. System Android components are not involved.
• Platform channels for native code. Access to camera, Bluetooth, NFC—via MethodChannel or EventChannel. flutter_camera, flutter_blue_plus are wrappers over platform channels.

React Native uses native platform components. <View> on iOS is UIView. <Text> is UILabel. This means:

• Native look and feel without extra effort.
• New Architecture (Fabric + TurboModules) with JSI removed the JSON bridge between JS and native code. Synchronous calls work without serialization. This is critical for animations and gestures.
• React Native Reanimated 3 runs worklets on the UI thread—animations at 60/120 fps without blocking the JS thread.

Performance in practice

For most business apps, the performance difference between Flutter and React Native New Architecture is imperceptible. The difference appears in edge cases.

Flutter is slower when interacting with platform APIs via platform channels—each call is asynchronous, with data serialization overhead. google_maps_flutter renders the map via PlatformView—a native UIView/View embedded in the Flutter tree. Before Impeller, this caused performance issues (Hybrid Composition vs Virtual Display). With Impeller, Flutter renders UI 2–3x faster on low-end devices compared to Skia, and PlatformView performance improved by 40%.

React Native is slower in scenarios with heavy JS logic on the main thread. Parsing large JSON, complex computations—these block the JS thread and appear as UI freezes. Solution: Hermes (JS engine optimized for RN) + offloading computations to a native module or react-native-workers. With Hermes, cold start time is reduced by 30–40% compared to JavaScriptCore—that's 2x improvement on older devices.

Ecosystem and maturity

Dart is a barrier to entry for teams with a JS/TS background. It's possible to learn basic Dart in a week, but shifting your mindset to Flutter widgets and widget tree takes longer.

TypeScript in React Native is the de facto standard. A team with React experience becomes productive faster.

When to choose Flutter?

• Need a unified branded UI on all platforms (iOS, Android, Web, Desktop).
• Team is ready for Dart.
• Lots of custom animation and custom UI—Flutter is more predictable.
• The app is not tied to specific native APIs.

When to choose React Native?

• Team has React/TypeScript expertise.
• Need native look and feel.
• Heavy use of native components (Maps, Camera with native capabilities).
• Sharing code with React web via monorepo.

Kotlin Multiplatform Mobile: a different story

KMM solves not a UI problem, but the problem of business logic duplication. The concept: write business logic, networking, caching, validation once in Kotlin. iOS receives a .framework via Kotlin/Native, Android uses the library directly. UI on each platform is native.

// Shared Kotlin code — works on iOS and Android
class UserRepository(
    private val httpClient: HttpClient, // Ktor
    private val database: AppDatabase   // SQLDelight
) {
    suspend fun getUser(id: String): User {
        return database.userQueries.selectById(id).executeAsOneOrNull()
            ?: httpClient.get("$BASE_URL/users/$id").body<User>().also {
                database.userQueries.insert(it)
            }
    }
}

Ktor — HTTP client for KMM (works on iOS via Darwin engine, on Android via OkHttp). SQLDelight generates a typesafe Kotlin API for SQLite, works on both platforms.

Real limitations of KMM

Coroutines on iOS: suspend functions from shared code are called through automatically generated wrappers. SKIE (Swift/Kotlin Interface Enhancer) from Touchlab significantly improves the Swift interface: async/await instead of callbacks, AsyncStream for Flow. Without SKIE, working with coroutines from Swift is inconvenient.

Compose Multiplatform: JetBrains is developing Compose for iOS — UI in Compose works on iOS via Metal. This blurs the line with Flutter: one Compose code for both platforms. Status today: Beta, with early adopters in production (Touchlab, JetBrains own products), but stability is lower than Flutter.

Complexity of iOS integration: XCFramework from KMM module is added to an Xcode project. SPM integration exists and works. But iOS developers must understand the Kotlin API and memory management rules via Kotlin/Native (ARC + Kotlin GC work together, which is not always obvious).

When KMM is justified

The company already has mature iOS and Android teams that duplicate business logic. Switching everything to Flutter or React Native is too radical. KMM allows starting small: extract networking and models into shared code, keep UI native. Gradual migration without rewriting everything.

Typical mistakes in technology selection

Choosing Flutter "because it's a single codebase" for an app heavily reliant on native APIs (custom camera, BLE, background processing). Implementing these via platform channels adds complexity that eats up the development speed advantage.

React Native without understanding the JS thread. Heavy operations on the JS thread cause visible freezes. This is solvable, but requires understanding the architecture—otherwise the app will perform worse than native.

KMM without an iOS developer on the team. Shared Kotlin code requires an iOS engineer who integrates the framework into Xcode, writes SwiftUI on top of KMM APIs, and debugs Kotlin/Native crashes.

What is the development process and timeline?

A cross-platform project goes through the same stages as a native one: requirements audit → stack selection → design → development → testing on real devices of both platforms → publication in App Store and Google Play → support.

Testing on real devices is not optional. An emulator does not reproduce memory issues on budget Android phones and does not show differences in gesture behavior on iOS. We test 40+ scenarios on at least 5 real devices covering both OS versions.

Budget savings compared to two native teams can be up to 40–50%. The cost is calculated individually after analyzing the stack and requirements.

What's included in our work

• Technical audit and stack selection for your project.
• Architecture design (clean architecture, MVVM, BLoC/Redux).
• UI development according to design mockups for both platforms.
• Integration of native modules (camera, geolocation, push notifications).
• CI/CD setup (GitHub Actions, Codemagic).
• Testing on real devices (iOS/Android) — at least 40 scenarios.
• Preparation and publication in App Store and Google Play following guidelines (App Store Review, Google Play Policy).
• Technical support for 3 months after launch.
• Handover of source code, documentation, and access — all turnkey.

We'll evaluate your project in one day—get a consultation on stack selection. Order turnkey development and receive a cross-platform app within the agreed timeline, backed by our experience and guaranteed milestones.