# On-Demand App Development | Uber-Style Dispatch + Real-Time Tracking | Alher Tech > Uber-style on-demand apps: customer + driver + admin, real-time tracking, surge pricing, payouts. From rides to delivery to home services. 16-22 week launch. - Canonical page: https://alhertech.com/en/solutions/on-demand-app-development/ - Site: Alher Tech (custom software, AI agents and SEO engineering, https://alhertech.com/) - Contact: https://alhertech.com/en/contact/ --- Three apps that act as one: customer-facing, driver/provider, ops dashboard, wired through a real-time dispatch engine that survives launch day. ## What On-Demand App Delivers - **A Dispatch Engine That Scales With You**: On-demand is the hardest category of app to ship because every screen has a real-time partner: the customer needs to see the driver moving, the driver needs to see the queue, the dispatcher needs to see the city. Most teams underestimate the dispatch engine and end up debugging maps and websockets at 2am after launch. We build the dispatch core first. - **Real-Time Maps That Just Work**: Mapbox or Google Maps (your call) with WebSocket location streams batched intelligently to keep driver battery alive. Customers see smooth movement, drivers do not run out of phone. - **Pricing Logic You Can Read**: Base + per-km + per-min + surge multiplier + commission split, codified in pure functions with unit tests. Marketing changes a price; the change is reviewable in Git. - **Driver Onboarding That Does Not Burn Ops**: Self-service driver application, document OCR + verification, background-check integrations, training videos, vehicle inspection workflow. Reduces ops support by 60% versus manual onboarding. - **Payments + Payouts End to End**: Customer pays via Stripe / Apple Pay / Google Pay; driver gets paid via Stripe Connect with automated weekly payouts and tax forms. Cash-payment fallback for emerging markets. - **Compliance for Regulated Cities**: VTC licensing flows in Spain, electronic ride logs for tax authorities, optional invoice-per-trip for B2B. Designed to survive the first inspection. ## How We Build Your On-Demand App - **Service Design Workshop**: Two days mapping every state of every party (customer waiting, driver assigned, en-route, arrived, completed, disputed). The state machine becomes the spec. - **Dispatch Core First**: We build the matching engine, location streaming and the price calculator before any UI, load-tested with synthetic drivers and customers. - **Driver App + Customer App in Parallel**: Two squads, daily sync. Driver app and customer app share a contract and we test their interaction every Friday. - **Admin Dashboard + Ops Tools**: Live city map, manual override on dispatch, surge controls, driver suspension, refund tools: what your ops team needs at 2am. - **Closed Beta in One Zone**: Real drivers, real customers, capped at one neighborhood. We measure ETA accuracy, complete-rate and dispatch latency before opening the city. - **Launch + 24/7 Coverage**: We sit on call with your team for the first month: real-time apps fail in unexpected ways and the first week determines if drivers stay. ## High-performance stack used by global leaders React/Next.js/Angular on the frontend and Java 21 + Spring Boot + PostgreSQL 14 on the backend: the same stack that BBVA, ING, and Netflix use for their security and performance. ## On-Demand App: FAQ ### How much does an on-demand app cost? A focused MVP (one city, one service type, single payment method) is €80,000-€140,000. A full multi-city, multi-service platform reaches €250,000-€500,000+. Below €80K you cannot ship something that works at launch, and we will tell you so. ### How long to launch? 16-22 weeks to a single-zone beta. 6-9 months to a city-wide rollout with full ops tooling. ### iOS, Android or both? Both, from day one, on React Native: same JS codebase shared across drivers and customers, native modules where they matter (location, push, payments). ### Can drivers use the app offline? Yes. Trip data queues locally and syncs when connectivity returns. Customers see "driver searching" state and we transparently retry. No data is lost. ### How do you prevent fraud? Device fingerprinting, behavioral signals (suspicious GPS jumps), Stripe Radar for cards, manual review queue for first-trip drivers, and a velocity rule engine you can update without a deploy. ### Can it handle multiple service categories? Yes: rides, parcel delivery, food delivery and home services all share the dispatch core but have distinct flows. Adding a new category is typically 4-6 weeks once the core is live. ### What about driver labor law compliance? Spain has the Riders Law and ongoing case law on platform employment. We build classification flexibility in: contractor onboarding, or agency-employed integration via your payroll provider. Legal call before architecture is mandatory for this category. ### Do you work with clients globally? Yes. We work fully remote with clients across Spain, Europe, the US and LATAM. Time zones, video calls and live demos at every milestone.