Build a Marketplace App with AI — Two-Sided, Native, in 5 Weekends
Native two-sided marketplace with AI help. React Native + Stripe Connect + Supabase. Sellers + buyers + payouts. Real build time from a developer who shipped 4 apps in a month.
Why a marketplace is the hardest category to build casually
A marketplace is two apps stapled to one backend. A seller flow and a buyer flow, each with its own auth state, its own screens, and its own trust problem. If you try to treat them as one app you end up with an inbox that nobody uses.
I built one marketplace inside my 4-app run. The hard part was not the code. It was admitting that the two sides have almost nothing in common except the database.
What you actually need to build
- Seller onboarding with payouts: Stripe Connect Express is the right default. Skip if you are doing a services marketplace, but for physical goods or bookings this is non-negotiable.
- Listings: Title, one image, price, category. No variants, no inventory counts, no bulk upload in v1.
- Buyer browse + search: A simple list with a text filter. Skip faceted search.
- Checkout: Stripe for the transaction, seller gets a payout after a holdback window (7 days is a good default for fraud).
- Messaging per listing: Buyer and seller chat about the listing. Keep it dumb — a single
messagestable with listing_id, not a full inbox model. - Review after transaction: One-time review prompt after a successful purchase. This is the trust loop.
No seller analytics dashboard in v1. Sellers will ask for it after they make their first $100, not before.
The stack I use
- React Native + Expo.
- Supabase — Postgres with RLS, Storage for listing images.
- Stripe Connect Express — onboarding, split payments, payouts.
- NestJS — the transaction endpoint that charges the buyer and splits to the seller.
- Supabase Realtime for the per-listing chat.
- Claude Code + 11 AI agents — scaffolds the seller and buyer screen sets.
Real build time
With the boilerplate, expect 5 weekends for a functioning v1.
- Stripe Connect onboarding flow: ~10 hours. This is the biggest single chunk.
- Listings CRUD + images: ~8 hours.
- Buyer browse + search: ~5 hours.
- Checkout + split payment + holdback logic: ~12 hours.
- Per-listing chat: ~6 hours.
- Review loop + App Store submission: ~8 hours.
About 49 hours. The Stripe Connect onboarding alone is half a weekend if you have never done it.
Where people get stuck
- Stripe Connect verification friction: Sellers bounce during the KYC flow. Embed the Stripe-hosted onboarding in a WebView and let Stripe handle it. Do not try to collect SSN in your own form.
- Payout timing disputes: Sellers want the money now, buyers want protection. A 7-day holdback is the middle ground. Document it on the seller onboarding screen, not buried in terms.
- Chargeback fraud: A buyer claims non-delivery. Without a delivery proof flow you lose every dispute. At minimum, record a timestamp when the seller marks shipped and require the buyer to confirm receipt.
Skip the setup
Stripe Connect, Supabase schema with RLS, chat infra, push — pre-wired. The 11 AI agents scaffold the seller and buyer screens separately so the two flows stay clean.
Skip the setup. Start shipping.
Every piece of the stack above is pre-configured in Shippen. 11 AI agents scaffold the rest.