Eventya

The problem

An event is not a single purchase. Some items are bought the way any online store sells them (tables, chairs); others are services quoted against a date, an address and how far the vendor has to travel (catering, music). On top of that, each vendor only covers certain states and municipalities, and few customers can pay the full amount up front. All of it had to fit in one app, without leaving out the vendors, the field crew or the back office.

What I built

I built the whole ecosystem on a shared Node, Express and TypeScript backend with MongoDB. The React Native (Expo) app filters the catalog by state and municipality, so nothing shows up that can't actually reach the customer's address, and it runs two very different sales flows: a standard cart for products, and date-, address- and distance-based quoting for services, with the distance computed through Google Maps. Services close on a deposit and the balance is charged on the agreed dates through Stripe. On the business side I delivered the vendor portal (catalog, pricing, service areas, orders, scheduling, payouts, promotions, reviews and proof of service), the crew app where field workers claim available jobs, level up and track bonuses and payments, and the admin panel with metrics, categories and analytics. I'm now building the fifth piece: the web marketplace, with filters by category, locality, price and rating, and a calculator that shows each vendor what they take home after commission.