Designing a Unified Marketplace for On-Demand Local Service Discovery and Booking

This work set out to tackle a common problem: local service discovery and booking are scattered across too many separate apps. The solution proposed here is a single mobile platform that brings multiple service categories together, serving both customers looking to book services and providers looking to offer them — without needing separate apps for either side. Survey data guided the core design decisions. A large majority of respondents (84%) said they'd prefer one unified app over several separate ones, and even more (85.7%) called switching between platforms inconvenient. These results justified building a centralized, multi-service system rather than a single-purpose one. Beyond that, the survey also pointed to specific needs — straightforward booking, verified providers, secure payments, a review system, responsive customer support, and location-based features — all of which shaped the requirements. On the technical side, the app was built in Flutter for cross-platform support, with Firebase handling authentication, data storage, cloud functions, and notifications, and Razorpay integrated for payments. What's been built so far covers a core set of service categories, dual customer/provider functionality, provider verification, booking management, notifications, and payment processing. It's worth being clear that this is a working first version, not a finished product. Features like real-time tracking, AI-driven recommendations, emergency bookings, multilingual support, and subscription plans are still on the roadmap. The system also still needs thorough usability, performance, scalability, and user-acceptance testing before its real-world effectiveness can be confirmed. In short, this project shows what a requirements-driven approach to building a unified service marketplace can look like — combining discovery, provider onboarding, bookings, verification, and payments in one place lays useful groundwork for cutting down the fragmentation users currently deal with.

[1] N. Jyani and H. Bansal, “UrbanClap: India’s Largest Home Service Provider,” South Asian Journal of Business and Management Cases, vol. 10, no. 2, 2021, doi: 10.1177/09728201211018978. [2] “Examining Consumers’ Behavioral Intentions Towards Online Home Services Applications,” Journal of Global Information Management, vol. 31, no. 1, 2023, doi: 10.4018/JGIM.326547. [3] Organisation for Economic Co-operation and Development (OECD), “Trust in Peer Platform Markets: Consumer Survey Findings,” OECD Digital Economy Papers, no. 263, 2017, doi: 10.1787/1a893b58-en. [4] Google, “Firebase for Flutter,” Firebase Documentation. [Online]. Available: Firebase Documentation. [5] Google, “Flutter Documentation,” Flutter Documentation. [Online]. Available: Flutter Documentation. [6] Razorpay, “Payment Gateway Documentation,” Razorpay Documentation. [Online]. Available: Razorpay Documentation. [7] Razorpay, “Razorpay Security,” Razorpay Documentation. [Online]. Available: Razorpay Documentation.