Beauty Services Marketplace App

Outcomes

Context

Marketplace liquidity depends on a phone-native booking and payment loop.

Challenge

A beauty marketplace needed consumer mobile UX for discovery, location, authentication, payments, and engagement — with store-ready Android/iOS builds.

Approach

We shipped an Expo/React Native app with navigation stacks, Redux Toolkit state, Google/Apple auth, Stripe React Native, maps/location, Firebase analytics, and EAS build profiles for development, preview, and production.

Architecture

Expo React Native client, Stripe mobile payments, Firebase analytics, OAuth social login, EAS build pipelines, location/maps services.

Scope

• —Discovery UX
• —Auth
• —Payments
• —Maps/location
• —Notifications
• —Store builds

Constraints

• —App Store / Play compliance
• —Payment PCI via Stripe SDK
• —New Architecture migration caution on native modules

Solution highlights

• —EAS profiles for safe promotion paths
• —Stripe as payment system of record in-app
• —Analytics wired early for funnel learning

Technologies

Results

• —Store-oriented mobile client with EAS release profiles
• —Payments integrated in the native purchase flow
• —Social login and push-ready engagement hooks
• —Location-aware discovery patterns for service businesses

Lessons learned

• —Marketplace apps are release-engineering products as much as UI.
• —Maps and payments drive dependency risk — budget upgrades.
• —Social auth reduces signup friction but increases compliance surface.