Menu
E-commerce · Completed
Neighborhood Marketplace
Buyers can discover providers on a map, post requests, compare offers, and order products or services in one app.
- Duration
- 4-month build
- Team
- Project Lead (Me) + Mobile, Backend & QA Teams
Overview
Overview
Need a plumber, an electrician, or a carpenter? In most neighborhoods that search still works the way it did decades ago — ask around, walk the local market, hope somebody dependable is free.
An entire economy of everyday products and services ran on word of mouth, with no way to see who was nearby and free to take the job.
I led the build of the marketplace that puts that whole search on a map.
Sellers list what they offer — products and services alike — and buyers open the app to see real providers around them, ready to book in a few taps.
When nobody nearby fits, the marketplace flips into reverse: buyers post exactly what they need, and providers come to them with competing offers.
What used to be an offline, word-of-mouth market now runs as one digital marketplace: a single app for iPhone and Android with a web dashboard behind it.
It matches by category and location, with ordering and payment in one flow — whether it is a product being shipped or a service being booked.
Confidentiality note: Client and company names have been changed or omitted for confidentiality. The work, my role, and project scope are real.
Impact
Impact
2
Kinds of trade, one app
Physical products and professional services sell side by side, from a single marketplace
3
Systems built as one
A mobile app, an operator dashboard, and the backend behind them — shipped together as one marketplace
1
Codebase, both platforms
iOS and Android ship together from a single React Native codebase
Approach
Challenges & Solutions
Local, offline hunting
Finding a nearby seller or service provider meant asking around or visiting a local market in person — there was no single place to see who was available nearby.
One listing model for both
Products and services share a single catalog, so a seller can offer either — a cart for goods, a booking for services — from the same storefront.
Two marketplaces in one
Physical products sell from a catalog and cart; professional services are booked by appointment. Both had to live in one app without feeling bolted together.
Request-and-offer flow
Buyers post a requirement and receive competing quotes from multiple sellers, turning “I hope someone sells this” into sellers competing for the work.
Demand posted in reverse
Beyond ordinary listings, buyers could post what they wanted and invite offers — a request-and-bid flow most marketplaces never attempt.
Nearby, on a map
Buyers see real sellers around them on a map — the everyday hunt for a plumber or a service provider becomes a few taps instead of a trip across town.
Matching requests to sellers
Each buyer request had to reach the sellers who could genuinely fill it — the right category, close enough to deliver — not every seller at once.
One codebase, every surface
I led the build across a React Native app for iPhone and Android, a Next.js operator dashboard, and a NestJS backend — with payments and order management shared across all of it.
Stack
Built With
- TypeScript
- React Native
- Next.js
- NestJS
- Redux Toolkit
- MySQL
- REST APIs
Client Feedback Summary
Client Feedback
Muhammad led the build and understood the product, not just the tickets. The request-and-offer flow — the piece we worried about most — worked the way we pitched it.
Client name withheld
Client identity is confidential. This summary reflects verbal feedback shared with Muhammad and the project team.
Facing Similar Challenges?
Let's Talk About What You Need Next.
Share what you are building or improving, and I'll help you identify a practical next step.
Discussion
Comments
No comments yet. Be the first to share your thoughts.