Barber Connect is a concept mobile app for booking a specific barber directly. It was built from six user interviews, a scheduling survey, and a round of usability testing that reshaped the core booking flow. Researched, designed, and iterated end to end, solo.
In India, there's no platform for booking an appointment with a specific barber, and most local salons run on walk-ins. If you have a barber you trust, your options are to wait in line for them or settle for whoever's free. The idea started in that exact waiting room, where I sat wondering why a haircut ate half a Saturday. Conversations with friends confirmed the frustration was shared, not personal.
I took it on as a solo concept project: research, product definition, design, and usability testing, end to end. The goal was a validated booking flow, not production code.
Customers with a preferred barber face a forced trade every visit: compromise on who cuts their hair, or sit through the queue. Booking platforms that do exist, such as Urban Company and Lakme Salon, only connect you with their own in-house stylists. That model brings its own problems: limited stylist choice, availability constraints, uneven quality of service, and pricing set by the platform. None of them solve for the relationship people actually have: with one specific barber, often at a small independent salon.
So the product question became: let barbers create individual profiles, and let customers book their barber at a time that fits, directly, with no platform middleman deciding who they get.
I interviewed six regular salon-goers to test whether the waiting problem was worth solving. Three patterns held across every conversation: people would rather wait for their preferred barber than take whoever's available; when they do consider switching, they rely on friends' recommendations or plain trial-and-error; and, the finding I didn't expect, many feel hesitant or outright embarrassed asking for a specific barber at the counter. The waiting was annoying. The social friction of asking was the part nobody had designed for. An app that makes the request silent and standard removes that friction entirely.
A competitive pass on Urban Company and Lakme Salon confirmed the gap from Ch 02: both lock you to in-house stylists, which is precisely the constraint my interviewees were working around with loyalty to independent barbers.
Wants: trendy styles, skilled stylists for specific looks. Open to switching, and relies on reviews and friends' recommendations to choose.
Friction: can't tell reliable stylists from the rest; hesitates to request her preferred one, fearing she's imposing.
Wants: consistency. Has visited the same barber for years and will wait in line rather than switch.
Friction: the wait itself, plus the same hesitancy. He doesn't want to seem like he's causing inconvenience by asking.
Two behavioral poles from the interviews. The app had to serve both: discovery and reviews for Sarah, fast repeat-booking for Mark.
The research reduced to four requirements, which became the product's foundation:
Top-rated barber recommendations, surfaced by preference, location, and booking history, so explorers like Sarah have a starting point.
Search with real filters for location, services, availability, and specialty, so finding a specific barber doesn't depend on luck.
A booking flow with no dead ends: service, date, time, confirm. This became the screen I tested hardest (Ch 04).
Reviews filtered by the reviewer's age, because styling is subjective, and feedback from your own age group is the feedback you'd actually act on (Ch 05).
I sketched the flows on paper, built wireframes, and ran initial user tests before moving to hi-fi. The booking page, the focused step in the flow above, looked clean and tested badly. Watching people use it surfaced three concrete failures. The rebuild fixed all three.
The problemThree things broke in testing. They are flagged on the before screen and resolved on the after. See the numbered changes below.
The "Select a date" bar visible above wasn't the obvious choice. A calendar was. A scheduling survey settled it: 83.3% of users book within one to two days of deciding they need a haircut. Almost nobody plans three weeks out, so a full calendar would have been navigation overhead for a choice that's really "today, tomorrow, or the day after." The picker bar puts the next few days one tap away, with a calendar tucked behind "Select date" for the rare longer-horizon booking.
The evidenceThe picker bar exists because of the survey, not in spite of the calendar convention. When the data says the decision window is 48 hours, the calendar is the wrong default. It's tucked behind "Select date" for the rare longer-horizon booking.
Reviews filtered by age group. Styling is subjective: a cut that's "great" to a 22-year-old and to a 45-year-old are different judgments. The interviews showed people already filter socially: they trust recommendations from friends, who are mostly peers. So the review section lets users read feedback from their own age bracket, turning a wall of mixed opinions into the subset they'd actually weigh.
Contact details on the salon page. Booking removes the queue, but questions still happen: directions, a running-late call, a service clarification. Putting the salon's contact and location one tap from the profile keeps those moments inside the app instead of sending users to a search engine.
The changeLeft: reviews narrowed to the reader's own age bracket (here, 18–25), so the feedback is from people with comparable taste. Right: salon details with map, address, hours, and one-tap contact.
My Bookings, split into Upcoming and Completed. Upcoming bookings can be rescheduled or cancelled in place. Completed bookings get a Repeat button: one tap rebooks the same barber, service, and preferred slot. That button is the whole product thesis in miniature: the loyalist behavior from the interviews, the Marks who've seen the same barber for years, turned into the fastest path in the app.
The resolutionLeft, Upcoming: reschedule or cancel in place. Right, Completed: a Repeat button on every past booking. One tap rebooks the same barber, service, and slot. That's the loyalist behavior turned into the fastest path in the app.
The hardest unsolved edge is slot scarcity: popular barbers book out, and cancellations free up slots that nobody knows about. The next feature on the roadmap was Notify Me: opt in on a taken slot, and get pinged if a cancellation opens it. It serves both sides: customers get their preferred time, barbers don't eat empty slots from no-shows.
On the process itself, two honest notes. Six interviews were enough to find the pattern but not to size it. Today I'd pair them with a broader survey earlier, the way the 83.3% scheduling number ended up doing the heaviest lifting in the design. And this project predates my move into building in code: if I picked it up now, the validated flow wouldn't stop at a Figma prototype. The booking page would be a working app, which is exactly how I build today.
Defined the product from primary research: 6 interviews, a scheduling survey, and a competitive pass.
Designed the full flow from paper sketches through wireframes to hi-fi, solo.
Usability testing drove a concrete rebuild of the core booking page: three failures found, three fixes shipped into the prototype.
Six interviews, one survey, one round of usability testing. Every screen in Barber Connect traces back to something a user said or did. The process isn't a diagram; it's visible in the decisions.