Sewa Service Providers Marketplace and Freelance Mobile Application

It is a Sunday afternoon. Your kitchen sink starts leaking. You don't need a full renovation, just someone who knows what they're doing to show up in the next hour or two. You open your phone, search for a plumber, and land on a list of businesses with no reviews, outdated numbers, and zero indication of whether anyone is actually available or how far away they are.

This is the everyday friction Sewa was built to eliminate. Not just for plumbing emergencies, but for the entire category of local services that people need reliably and quickly: cleaning, electrical work, carpentry, car repairs, and the dozens of small fixes that fall through the cracks of every existing platform.

The idea was straightforward on paper: a mobile marketplace that connects users to verified service providers based on their location. In practice, building something people would actually trust enough to invite strangers into their homes turned out to be a much more nuanced design problem than the brief suggested.

Before we opened Figma, we needed to understand the two very different groups of people this app had to serve simultaneously: the users hiring services, and the providers offering them. A marketplace only works when it works for everyone on it, so getting both sides right was the first real design challenge.

On the user side, we built out personas grounded in research interviews. The first was Keisha, a busy marketing manager in her early thirties. She came home one evening to find her kitchen sink leaking badly. She needed a trusted plumber immediately but had no idea where to find one quickly. Her priorities were speed, trust, and visibility into pricing before she committed to booking. The second was Jamal, a sales rep in his forties who drives constantly for work. When his car broke down on the way to a client meeting, stranded on a busy road, his only goal was to locate a reliable mechanic within minutes. Both personas shared the same core anxiety: a time-pressured situation, a stranger who needed to be trusted fast, and no obvious platform that made that easy.

On the provider side, the challenge was different. Freelance service workers needed a platform that delivered consistent, verified job requests rather than the irregular word-of-mouth work they were used to. The app had to feel credible and professional enough for them to commit their income to it.

With a clear picture of our users, we mapped the friction points that existing solutions had consistently failed to resolve. Three problems kept surfacing regardless of which persona or use case we examined:

Our goal was to design a location-first marketplace that resolved all three challenges through deliberate, interconnected features rather than isolated fixes. The platform needed to feel fast, feel safe, and feel familiar. Not ambitious for its own sake, but precise in a way that actually solves the problem.

We organized the core features around what users told us mattered most: building enough trust to take the leap, and making the experience frictionless once they did.

We started with low-fidelity wireframes, not screens. The core flows needed structural solutions before they needed visual polish: how does a user browse service categories, select a provider, and confirm a booking in as few steps as possible? We mapped the full user journey end to end, from opening the app to receiving a completed service, and identified every decision point where we could reduce friction.

For navigation, we borrowed familiar patterns from ride-hailing apps. Users already knew how to request a driver nearby, see their arrival time, and track them in real time. Applying that same mental model to service bookings made the app feel immediately legible without a learning curve. The visual language followed suit: a clean, minimalist layout with bold action buttons, calming tones to reinforce trust and reliability, and clearly labelled service categories represented by recognizable icons.

After multiple iterations on the wireframes, we moved into high-fidelity prototypes and ran usability testing sessions. The testing revealed a handful of flows where users hesitated or took an unexpected path. We iterated on those specific moments until the journey felt natural. The final mockups reflected every insight gathered along the way: a product that looked polished, but had been shaped entirely by real user behaviour.

The launch results were a strong validation of the design decisions made throughout the project. The metrics reflected not just an attractive interface, but a product that had genuinely resolved the friction points users had been living with.