Industry: Real Estate Technology
Platforms: iOS & Android
Type: Property Offer & Bidding Platform
Technology: React Native & Firebase
Case Study
Building a Cross-Platform Property Offer & Bidding Platform with React Native and Firebase
Virtueinfo designed and built a mobile-first marketplace application that connects property sellers and buyers through a structured offer and bidding workflow — replacing fragmented, manual communication with a real-time, document-rich mobile experience available on both iOS and Android.
Project Overview
The client operates in the real estate technology space, serving two distinct user groups: property sellers who list properties for sale and buyers who submit offers to purchase them.
The goal was a single mobile application that supports both roles with tailored navigation, workflows, and permissions, while keeping the entire offer lifecycle — from listing to walkthrough to acceptance — inside one connected experience.
The Business Challenge
Property sale negotiations traditionally involve scattered communication: phone calls to schedule walkthroughs, email threads for offer documents, and manual tracking of who has seen what.
The client needed a platform that could let sellers list properties and manage incoming offers in one place, while buyers discover listings and submit structured offers with supporting documents. Two-sided calendar scheduling had to coordinate property walkthroughs, with both parties notified instantly as offer status changed.
The platform also had to maintain a reliable audit trail of documents, receipts, and activity — and work smoothly on both major mobile platforms from a single codebase.
Our Approach
Virtueinfo followed a discovery-first process to map the two user journeys — buyer and seller — before writing code, since the entire navigation and permission model needed to branch by role from day one. Discovery defined buyer and seller workflows, offer states, and notification triggers, and a serverless backend was selected to avoid infrastructure overhead and enable real-time data sync out of the box.
Development produced a single React Native codebase targeting iOS and Android, with Redux managing feature-scoped state for offers, bids, scheduling, notifications, and profile. Push notification delivery was connected to in-app deep linking so a notification opens the exact relevant screen.
Component and unit testing ran through Jest with error monitoring wired in from the start, and backend logic that must not run on-device was structured into serverless cloud functions — keeping privileged operations off the client.
The Solution
The platform is organized around a central listing entity that both roles interact with differently.
For Sellers
Create and manage listings, review incoming offers, accept or reject bids, and coordinate walkthrough scheduling — all from one place.
For Buyers
Browse listings, submit offers with supporting files, track offer status in real time, and schedule property walkthroughs without leaving the app.
Shared Infrastructure
A notification system, document and receipt management, and activity logging that both roles rely on throughout the offer lifecycle.
Key Features
Role-Based Experience
Buyers and sellers see tailored navigation, screens, and actions based on their account type, driven by a single shared codebase.
Structured Offer & Bidding Workflow
Offers move through defined states — submitted, under review, accepted, rejected, terminated — with each transition reflected in real time for both parties.
Two-Sided Walkthrough Scheduling
An integrated calendar lets buyers and sellers coordinate property walkthrough times without leaving the app.
Multi-Type Document Management
Users can attach plans, bid documents, photos, and permit or job notes to a listing, with camera, gallery, and file-picker support.
Real-Time Push Notifications
Offer updates, scheduling changes, and status transitions trigger push notifications that deep-link directly to the relevant screen, with unread-count badges kept in sync.
Receipt and Transaction Records
Dedicated screens track receipts and related transaction documentation tied to each listing.
Activity Logging
A logs screen gives users visibility into recent account and listing activity for a reliable audit trail.
Offline-Aware UX
Network connectivity state is tracked centrally so the app can adapt behavior gracefully when connectivity drops.
Technical Challenges and Solutions
| Challenge | Our Approach |
|---|---|
| Keeping buyer and seller in sync on the same offer in real time | Used a real-time document database so state changes propagate to both parties without manual refresh. |
| Push notifications needing to open the exact right screen from any app state | Built a centralized notification-to-navigation handler that maps payload data to in-app routes, tested across foreground, background, and terminated states. |
| Attaching multiple document types to a single listing | Designed a typed file-upload model with dedicated upload categories and a unified file browser per listing. |
| Two-sided calendar scheduling without conflicting bookings | Built dedicated scheduling logic and screens per role so availability and confirmations stay consistent between buyer and seller views. |
| Keeping notification badge counts accurate across app transitions | Synced unread-notification counts on app-state change events rather than relying on client-only counters. |
| Avoiding infrastructure overhead for a mobile-first MVP-to-scale product | Chose a managed backend — serverless database, storage, auth, messaging — to avoid server provisioning and reduce operational burden. |
| Maintaining visibility into production issues across two platforms | Integrated crash and error monitoring at the application level from early development. |
Security & Reliability
A managed identity service handles sign-in, sign-up, and password reset flows rather than custom credential storage, while role-based access governs which screens, actions, and data a user can reach.
Sensitive or backend-only logic runs in serverless functions, isolated from the client and not exposed through the mobile app bundle. Structured, typed data models for listings, offers, and file uploads reduce malformed or inconsistent records, and uploads are scoped to authenticated users and their role permissions.
Application-level error and crash monitoring is integrated across both mobile platforms to support fast issue diagnosis.
Scalability & Performance
A real-time document database and managed storage layer scale with usage without manual database administration, while notification and privileged-operation workloads run in independently scalable serverless functions rather than a fixed server.
Cached, optimized image components reduce load time and memory pressure on listing- and document-heavy screens.
Feature-isolated Redux state keeps the client lightweight and makes it straightforward to extend individual workflows — offers, scheduling, notifications — independently, while centralized network-state tracking lets the app adapt gracefully under poor connectivity.
Business Outcomes
- Consolidated a previously fragmented offer and negotiation process into a single mobile application.
- Real-time visibility into offer and scheduling status for both buyers and sellers.
- Reduced reliance on manual calls and emails for walkthrough coordination.
- Centralized document and receipt management per listing, improving traceability.
- A maintainable, single-codebase mobile solution covering both iOS and Android.
- A scalable technical foundation for adding future workflow or listing features.
Why Virtueinfo
Virtueinfo brought hands-on experience architecting role-based mobile applications on top of managed, real-time backends — a pattern well suited to marketplace and two-sided transaction products. Our team designed the offer and bidding state model, the notification-to-navigation system, and the multi-type document workflow as cohesive pieces rather than bolted-on features, which is what makes a two-sided marketplace app feel reliable to both user types.
We favor managed backend services where they reduce operational risk, and reserve custom server logic for the operations that genuinely need it — keeping the system easier to maintain and extend over time.
Building a Real Estate or Two-Sided Marketplace App?
Let’s keep both sides of your transactions synchronized in one real-time mobile experience.
Frequently Asked Questions
How do you build a real-time property offer or bidding app?
A real-time offer and bidding app typically pairs a cross-platform mobile framework like React Native with a managed, real-time backend so that offer status, messages, and scheduling updates reach both parties instantly without manual refreshes.
What technologies suit a two-sided real estate marketplace app?
React Native is a strong fit for the mobile client since it supports iOS and Android from one codebase. Managed backend services covering authentication, a real-time database, file storage, and push messaging reduce infrastructure overhead while supporting real-time, role-based workflows.
How is buyer/seller role separation handled in a shared mobile app?
Role separation is usually driven by the authenticated user's profile data, which determines which navigation stacks, screens, and permissions the app exposes — allowing one codebase to serve fundamentally different experiences per role.
How do push notifications open specific in-app screens?
A centralized notification handler maps the data payload of an incoming push notification to a specific in-app route, so tapping a notification — in foreground, background, or from a terminated app state — takes the user directly to the relevant screen.
Can an app handle multiple document types tied to one listing?
Yes — by defining a typed upload model with separate categories for plans, bids, photos, and notes tied to a parent entity, an app can support multiple document types per record while keeping uploads organized and easy to retrieve.
Why choose a serverless backend for a marketplace app?
A managed backend removes the need to provision, scale, and secure your own servers for authentication, storage, and real-time data sync — letting engineering effort focus on business logic while serverless functions handle operations that must stay off the client.
How do you keep two-sided scheduling conflict-free?
By modeling scheduling as its own state domain — with dedicated logic per role for proposing, confirming, and updating time slots — so both sides always see a consistent, up-to-date view of availability and confirmed appointments.
What does role-based navigation mean in a React Native app?
The app's navigation structure — tabs, drawers, and screens — is generated dynamically based on the logged-in user's role, so buyers and sellers or any other distinct user types get a tailored experience from a single shared codebase.