Compare

WDDNG vs Multichoice installer payments

The problem, what was built, the stack and the outcome, next to each other.

Clear

In common

  • Shared stack: none in common

Swipe sideways to compare ›

WDDNG ›

South Africa's wedding marketplace, with two apps on Google Play

Multichoice installer payments ›

R5M+ paid to installers in the first six months

At a glance

Role
Founder / Full-stack & Mobile Engineer
When
Jan 2026 – present
Length
10 mo so far
Status
Live
Type
AI, Mobile, Web
Role
Integration engineer
When
Delivered
Length
—
Status
Delivered
Type
Platform

The problem

South African couples plan across fragmented directories, WhatsApp messages and opaque “price on request” listings, while many international tools don't support local multi-ceremony wedding journeys.
Integrated the installer management system into Multichoice's payment process so installers are paid accurately and on time.

What was built

A Next.js and Supabase marketplace with two Kotlin / Jetpack Compose Android apps on Google Play: one for couples, one for vendors. Thuli, the AI planner, is a LangGraph supervisor coordinating 16 specialist agents.
—

Stack

  • Next.js
  • Supabase
  • PostgreSQL
  • Kotlin
  • Jetpack Compose
  • LangGraph
  • Zod
  • Paystack
  • Azure
  • LangSmith
  • Payments integration

Highlights

  • Two Kotlin / Jetpack Compose Android apps published on Google Play
  • Thuli: a LangGraph supervisor coordinating 16 specialist agents through Zod-typed handoff tools
  • Per-agent model selection, token metering and LangSmith tracing
  • SSE streaming that renders vendor cards and progress during an answer
  • Processed over R5 million in installer payments within six months

Infrastructure choices

  • Supabase with PostgreSQL RLS
—

Outcome

The marketplace runs across web and two production Android apps, giving couples structured planning tools and vendors better-qualified enquiries with date, budget and guest-count context.
Over R5 million in installer payments processed within six months.

See it