BeautyFindr

What we did

• •We shaped the mobile experience around separate client and provider journeys. Clients could browse by location and service type, review profiles and prices, send service requests, message professionals, and arrange bookings. Providers could publish services, set pricing and availability, respond to requests, and manage conversations in the same app.
• •We built a browser-based admin portal so the platform owner could review provider information and license details before approval. The portal also brought platform activity into one place, creating a practical layer of oversight alongside the customer-facing app.
• •We developed the mobile app with React Native and TypeScript and used Node.js, PostgreSQL, and AWS services for the backend. The architecture supported authentication, image storage, notifications, email, deployment, and scheduled tasks, while a shared mobile codebase made future cross-platform work more manageable.
• •The service-selection hierarchy and nested menu state created maintainability problems as the interface evolved. We simplified the component structure, added stronger typing and utility functions for updating the hierarchy, and tested the layouts across device sizes. These changes reduced edge cases and made the codebase easier to maintain.
• •The product launched with both clients and beauty professionals using it. Providers gained a dedicated channel to present their services and respond to demand, while clients could compare local options and contact professionals directly before booking.