The challenge
Swayed is a two-sided marketplace: people who want a new hairstyle on one side, hair professionals on the other. The customer-facing product is a native mobile app, but a marketplace is only as good as the operations behind it.
Someone has to approve providers, resolve listing problems, keep bookings moving and see what is happening on the platform. Doing that inside a mobile app is impractical, and doing it in a database console is worse.
A web admin panel for a mobile product
We built the operational backend as a Bubble.io web admin panel sitting alongside the mobile app, so the operations team works on a desktop with the screen space the job needs.
This split — native app for consumers, Bubble.io admin for operators — is an architecture we have delivered more than once, and it consistently gets teams operational faster than building bespoke internal tooling.
Managing both sides of the marketplace
The panel handles users and providers as distinct populations with distinct needs, because a marketplace operator manages supply differently from demand.
Listings and bookings are administrable from the same place, so a problem raised in the app can be resolved without switching tools.
Built for day-to-day operations
The interface was designed around the tasks operators repeat daily rather than around the database structure underneath. Frequent actions are quick; rare ones are simply available.
Because it is a Bubble.io build, new operational views can be added as the marketplace matures and the team discovers what it needs.
The outcome
Swayed runs with a consumer mobile app front-of-house and a Bubble.io web admin panel behind it, covering users, providers, listings, bookings and platform operations.
It sits alongside BostMD as our reference for mobile-plus-admin-panel architecture — and it is the pattern we recommend whenever an app team needs operational tooling without a second engineering project.