Flagship case study

AasPas

Hyperlocal service marketplace and realtime operations platform

AasPas is a full-stack marketplace built around a complete service lifecycle: customer discovery, worker matching, booking acceptance, live arrival tracking, job execution, payment completion, earnings distribution, support, post-service trust, and multilingual AI-guided booking help. It combines React Native mobile clients, StyleSheet-driven native screen architecture, a Node.js backend, realtime Socket.IO flows, Firebase Cloud Messaging, Google Maps, Razorpay, Agora calling, Redis-backed active state, MongoDB recovery, AI-assisted conversational flows, and native Android modules for lock-screen, background, and notification-driven behavior.

This product was designed, built, and iterated end to end by me as a solo developer across mobile UX, backend APIs, realtime systems, native Android behaviors, payments, tracking, worker tooling, and admin operations.

Open on Play Store Explore other projects

Solo built

End-to-end ownership across mobile, backend, native Android, and ops

3 product surfaces

Customer app, worker app, and admin control layer

12 languages

Localized mobile experience for real Indian service markets

Realtime + native

Socket rooms, FCM, maps, calling, lock-screen, and background flows

Wallet + payments

Advance fee, remaining due, worker earnings, commission, and settlement

Recovery-aware

Redis hot state with Mongo durability and route fallback behavior

Visual showcase

Designed product surfaces

These are real production screenshots from the customer and worker apps. I placed them here so the case study shows actual product depth across discovery, package selection, AI assistance, tracking, payments, wallet visibility, and earnings correctness instead of only marketing visuals.

Marketplace identity

AasPas positioned as a modern hyperlocal service brand with worker discovery, booking intent, and service-at-home messaging.

Customer home and service discovery

The home experience starts with search, service categories, and a strong booking-first interface instead of a generic landing screen.

Package selection by category

Category-specific package selection lets the marketplace handle richer service menus such as beauty workflows with multiple bookable items.

AI concierge in the real app

The AI concierge is not a concept slide. It is integrated into the app with multilingual responses and booking-oriented worker suggestions.

Live worker tracking and work timer

The live tracking surface combines worker map state, elapsed job timer, current cost, ETA, and direct communication controls.

Marketplace payment flow

Advance booking fee, secure payment entry, and backend-owned money correctness are exposed through a polished customer payment flow.

Worker control surface

The worker app includes operational quick actions for jobs, earnings, support, and emergency workflows in a field-operations oriented layout.

Wallet and payout visibility

The worker-facing wallet surface shows balance, payout setup, commission, and earnings composition to support settlement clarity.

Per-job earnings breakdown

Each completed job can be audited through a detailed earnings sheet showing work amount, online payment, commission, and final credited value.

System map

Major product systems

AasPas is wide in scope because it connects discovery, booking, realtime state, worker motion, money movement, operational support, and post-service trust inside one mobile product. The engineering challenge was not one feature. It was making all of these subsystems behave consistently together.

Booking engine

Supports service discovery, worker selection, booking creation, worker acceptance, cancellation, work start, job completion, payment pending, payment success, review flow, and booking history restoration.

AI booking and support assistant

A multilingual conversational layer helps users ask for services in natural language, guides them to the right category or worker flow, and can support assisted booking behavior instead of relying on rigid menu-only navigation.

Live tracking and service radius

Workers configure their operating area and availability so discovery is location-aware. Once a booking is active, customer tracking uses latest worker location, route cache, ETA, distance updates, and map-based arrival visibility.

Native communication

Voice calls use Agora with custom Android incoming-call and ongoing-call experiences, notification actions, lock-screen entry, speaker and earpiece routing, and seamless return-to-call behavior.

Payments and money flow

Handles minimum booking fee, online payment, cash collection, final job amount, worker earnings, commission logic, remaining balance, wallet visibility, and settlement-ready records without exposing private business internals.

Worker operations

Workers manage incoming bookings, active jobs, location sharing, job timer, collect payment flow, earnings dashboard, wallet view, document setup, service-area setup, and availability control.

Admin and support operations

Backend and admin tools cover notifications, payout and wallet visibility, service monitoring, support tickets, tutorial content, app version control, and operational status tracking.

Role design

Three connected product surfaces

This product is deeper than a single app because it has separate responsibilities for customers, workers, and operations. There is also a shared realtime platform layer keeping those surfaces synchronized.

Customer app

Trust, booking, payment, and visibility

The customer surface handles the complete service journey from search to review, with strong emphasis on trust, realtime visibility, and payment clarity.

Category-based service discovery with worker browsing and profile viewing

Multilingual AI booking-help flow for natural-language service requests and assisted booking

Booking creation with payment mode selection and minimum booking fee handling

Live worker tracking with distance, ETA, map state, and latest-location recovery

Call worker, cancel booking, payment summary, and booking-complete visibility

Booking history, profile stats, saved addresses, reviews, support tickets, and tutorials

Recovery-oriented behavior so active booking context can be restored after relaunch or reinstall

Worker app

Field operations, motion, and earnings

The worker experience is not a passive dashboard. It is a field-operations app that has to react to bookings, movement, job timing, payment collection, and availability state in realtime.

Native incoming booking popup with accept and reject actions from active, background, or lock-screen states

Immediate location capture on accept, route preparation, and live location sharing for the active booking

Active job details, job timer, booking-state transitions, and travel-to-job awareness

Collect payment flow with backend-calculated remaining amount and money-state correctness

Earnings breakdown, wallet balance, settlement visibility, and payment history cues

Availability, service setup, service radius, package management, documents, and onboarding flows

Admin operations

Business control and operational oversight

AasPas also includes the operational layer needed to run the business, monitor workflows, and support users after the initial booking happens.

Booking, user, worker, and activity visibility for operational support

Notification routing, ticket handling, review visibility, and support workflows

Wallet, payout, settlement, and payment-related oversight routes

Service monitoring, category management, worker oversight, and readiness support

Tutorial and informational content management for the mobile product

App version control and rollout support for production updates

Shared platform services

Realtime state, recovery, and infrastructure glue

These are the cross-cutting systems that keep customer, worker, and admin surfaces synchronized, recoverable, and production-friendly under real mobile conditions.

Socket.IO room architecture for booking state, call state, payment state, and live location events

Redis-backed hot state for active bookings, routes, latest worker location, and fast reads

MongoDB durability for recovery snapshots and business-side history

Firebase push fallback when sockets are not enough because the app is backgrounded or killed

Google Maps and Directions integration with cache-first routing behavior

Native Android notification, activity, and background patterns for time-sensitive actions

Technical architecture

Technology footprint

The stack spans mobile frontend, backend APIs, realtime event routing, cache-backed recovery, mapping, external payment and communication services, and native Android integration. Each layer has a clear job rather than acting as accidental complexity.

Mobile frontend

Role-based customer and worker experiences built in React Native with StyleSheet-driven native screen architecture, multilingual UX, state-driven flows, and offline-aware behavior.

React NativeReact Native StyleSheetExpoTypeScriptReact NavigationAsyncStoragei18nextoffline-aware UX

Backend services

A Node.js and Express backend that owns canonical booking, payment, worker, wallet, and history state with protected routes and validation.

Node.jsExpress.jsMongoDBMongooseJWT authrequest validationrole-based APIs

AI-assisted conversational layer

The product also includes conversational booking-help patterns that connect natural-language service intent to guided marketplace actions without exposing internal business logic.

multilingual assistant UXintent-guided booking helpcustomer support automationnatural-language interaction

Realtime event layer

Socket-driven state propagation keeps customer, worker, and admin experiences synchronized through booking rooms and targeted event delivery.

Socket.IO roomsbooking state eventsworker location streamingpayment eventscall lifecycle events

Hot state and recovery

Fast active-booking reads are separated from durable recovery so the product remains responsive while still recovering from app reinstall or reconnect scenarios.

Redis active stateroute cachelatest worker locationMongo recovery snapshotscache-first fallback

Native Android layer

Platform-specific Android work was added where plain React Native was not enough for booking urgency, call UX, and background behavior.

full-screen booking popupincoming call activityongoing call notificationnotification actionsbackground behavior

Payments and external services

The product integrates payment, maps, calling, and notification infrastructure while keeping backend-owned correctness for sensitive business state.

RazorpayFirebase FCMAgoraGoogle MapsGoogle Directionscloud media/storage flows

Money systems

Marketplace payments, wallet, and earnings

This product needed more than a simple payment button. It required marketplace-style money flow: advance fee, remaining balance, worker collection, earnings, commission, and backend-owned correctness for what was already paid versus still pending.

Minimum booking fee flow for advance payment and booking confirmation

Online payment and cash collection support across customer and worker journeys

Backend-owned canonical calculation for total paid, already paid, remaining due, hourly charges, and final amount

Worker-side collect-payment experience tied to final booking state and earning updates

Commission, worker earning breakdown, wallet visibility, and settlement-oriented records

Payment verification and reconciliation patterns so UI display is not treated as money truth

Location intelligence

Tracking, geo-location, and route behavior

Live tracking had to feel stable and believable in real use. That meant worker discovery by radius, latest-location storage, polyline reuse, controlled rerouting, and customer-facing map state that survives app restarts or reconnect events.

Worker discovery filtered by service area, availability, and operating radius

Realtime location streaming for active bookings instead of static polling-only behavior

Latest worker location stored as hot state for quick reopen and tracking restore

Polyline and route cache so the app can reopen tracking without blindly calling map APIs again

Controlled rerouting logic to avoid overusing Google Directions when the worker goes off-route

Smooth visual tracking combined with ETA and remaining-distance awareness for the customer

Native communication

Calling, notifications, and Android behavior

Calling was implemented as a native-feeling system instead of a lightweight modal. The experience had to behave correctly from notifications, lock screen, background state, and in-progress multitasking while keeping caller and receiver flows synchronized.

Agora voice call integration for direct customer-worker calling

Incoming call full-screen experience and notification actions on Android

Tap-to-return ongoing call notification for both continuity and multitasking

Speakerphone-default behavior with earpiece switching for more phone-like calling UX

FCM-backed wake-up and call signaling fallback when the app is not active

Socket-driven call accept, reject, end, and synchronization events across both users

Operations layer

Admin and support control layer

The product also needed the business-side layer that helps the marketplace run after launch: notifications, service monitoring, support workflows, visibility into money movement, and rollout discipline for app updates.

Notification operations and message routing support

Wallet, payout, and payment visibility for business operations

Support ticket, issue-management, and review-awareness flows

Service monitoring, worker oversight, and availability-related support

Video/tutorial and informational content management

App version control and rollout discipline for production updates

Flagship capabilities

What makes this product unusually deep

Native Android booking and calling flows instead of simple JS modals

Smooth worker tracking with route awareness and latest-location recovery

Service radius and availability controls so workers appear only where they operate

Booking lifecycle covering acceptance to payment confirmation and review

Wallet, earning, commission, and settlement support for worker-side economics

Multilingual AI booking assistant that can guide or trigger service booking workflows

React Native StyleSheet-based screen system for customer and worker experiences

Customer, worker, and admin experiences built within one connected platform

App-version and operational tooling for controlled rollout and support

High-level security and correctness measures without exposing sensitive implementation secrets

Ownership and reliability

What I personally handled

This is the part that matters in interviews: the product was not only designed. It was also implemented, debugged, and production-shaped across all of these layers by a single developer with direct responsibility for both features and correctness.

Mobile architecture and UI flow design for both customer and worker products

StyleSheet-based native screen architecture and reusable mobile UI patterns

Backend APIs, business rules, booking lifecycle, and data modeling

Realtime socket architecture for booking, tracking, payment, and call state

Native Android integration for booking urgency, calls, notifications, and return paths

Payment, wallet, settlement, and earning correctness logic

Operational tooling, recovery patterns, and production-focused QA iteration

Production-minded safeguards

This page intentionally explains product scale without exposing sensitive secrets, internal pricing rules, private keys, raw customer data, or exploitable operational details. The goal is to show judgment, depth, and reliability in a safe public format.

Role-based access and authenticated APIs

Server-side payment truth for already-paid and remaining-amount correctness

Validated request flows and canonical booking and payment state transitions

FCM fallback when the app is backgrounded or killed

Active booking recovery after relaunch or reinstall

Cache-first route and location recovery with backend fallback behavior

Technology index

Core technologies used

React NativeReact Native StyleSheetExpoTypeScriptReact NavigationNode.jsExpress.jsMongoDBMongooseRedisSocket.IOFirebase Cloud MessagingFirebase Admin SDKAgoraRazorpayGoogle MapsGoogle DirectionsAsyncStorageJWT authenticationi18nextNative Android modulesBackground location patternsRealtime notification routingWallet and settlement logicAdmin operations tooling