Why it was needed
01Matching, appointments, payments, and reviews all carry state, so the app and backend needed to stay in sync while leaving room for operations.
Private matching service
A private matching service that connects screening, matching settings, appointments, reviews, and payments.

Matching / Concierge
Private matching service that connects screening, appointments, reviews, and payments.
Project overview
W Club is a private matching service that connects screening, matching settings, appointments, reviews, and payments. The product is built around operational control and meeting quality rather than wide public exposure.
The repos show Flutter app_v2 routing, Riverpod state, webview payments, generated API clients, and a NestJS variant backend with matching, appointment, payment, review, and notification modules. It is an operations-heavy platform with state on both app and server sides.
Why it was needed
01Matching, appointments, payments, and reviews all carry state, so the app and backend needed to stay in sync while leaving room for operations.
What I built first
02I connected Flutter app_v2 routing, Riverpod state, and a variant-based NestJS backend with matching, appointment, payment, review, and notify modules.
Where this approach works well
03This fits high-touch introduction services and membership platforms with heavy operational involvement.
Technical details
App client
Server and operations
Identity, payments, and communication
Product surfaces
The screens below are the actual interfaces that defined the product experience.
Website



App






Contact
A short brief, a reference link, or the current problem definition is enough. I can help structure the right first version from there.