Building an 'Uber for X' App: Architecture for On-Demand Services

The Anatomy of an On-Demand Marketplace

Whether you are building an "Uber for Dog Walking," an "Uber for Home Cleaning," or an "Uber for Mechanics," the underlying software architecture is largely identical.

Unlike a standard e-commerce site where users patiently wait 3 days for shipping, on-demand apps require real-time synchronization. If a customer requests a plumber, that request must instantly broadcast to all available plumbers within a 5-mile radius, and the first to accept wins the job.

At DevApps Technology, we have engineered multiple on-demand platforms (like Apnar Shebok and Workili). Here is how we architect them.

1. Real-Time Geolocation (PostGIS)

You cannot use standard SQL text queries to find the nearest service provider. You must use spatial mathematics.

We utilize PostgreSQL with the PostGIS extension. This allows the database to understand longitude and latitude coordinates natively.

When a customer opens the app, we query the database to find all online providers within a specific radius using the ST_DWithin function:

-- Find all 'Online' plumbers within 10 kilometers (10,000 meters) of the customer's coordinates
SELECT provider_id, name 
FROM providers 
WHERE service_type = 'Plumbing' AND status = 'Online'
AND ST_DWithin(
  location_geom, 
  ST_MakePoint(-73.9782, 40.6482)::geography, 
  10000
);

2. Real-Time Bid Broadcasting (WebSockets)

When the customer confirms their request, we do not want them to refresh their screen to see if a provider accepted.

We implement WebSockets (via Socket.io).

1. The Node.js server receives the job request.
2. The server queries PostGIS to find the 5 nearest online plumbers.
3. The server emits a silent WebSocket payload to the React Native apps of those 5 specific plumbers.
4. Their phones instantly ring with an "Accept Job" push notification.

3. Live Tracking and Map Navigation

Once a provider accepts the job, the customer wants to see them moving on a map (the "Uber car moving on the screen" effect).

• Google Maps SDK / Mapbox: We integrate native map SDKs into the React Native app.
• Location Polling: The provider's phone uses background GPS polling (tracking their location even when the app is minimized) and fires their updated coordinates back to the WebSocket server every 5 seconds.
• ETA Calculation: We use the Google Directions API to continuously calculate real-time ETAs based on live traffic.

4. Background Push Notifications (FCM/APNs)

If the provider's app is closed, WebSockets will not reach them. We implement Firebase Cloud Messaging (FCM) and Apple Push Notification service (APNs). This ensures that even if the plumber's phone is locked in their pocket, a high-priority "New Job Alert" will wake the phone and play a loud custom ringtone.

Do you have an idea for an on-demand startup? Real-time architecture requires serious engineering horsepower. Contact DevApps Technology to build a fast, scalable on-demand platform.