Compare
Joel Transport vs WDDNG vs Fashionly
The problem, what was built, the stack and the outcome, next to each other.
Clear · Up to 3 at a time
In common
- Shared stack: none in common
- Both kinds of work: Web
- Order: Joel Transport (Dec 2022 – May 2023) → WDDNG (Jan 2026 – present) → Fashionly (Apr 2026 – present)
Swipe sideways to compare ›
Joel Transport ›
Online booking platform on AWS
WDDNG ›
South Africa's wedding marketplace, with two apps on Google Play
Fashionly ›
Your style, elevated: an AI stylist that starts with what you own
At a glance
- Role
- Lead Engineer
- When
- Dec 2022 – May 2023
- Length
- 6 mo
- Status
- Live
- Type
- Web, Platform
- Role
- Founder / Full-stack & Mobile Engineer
- When
- Jan 2026 – present
- Length
- 10 mo so far
- Status
- Live
- Type
- AI, Mobile, Web
- Role
- Founder / Lead Engineer
- When
- Apr 2026 – present
- Length
- 7 mo so far
- Status
- MVP
- Type
- AI, Mobile, Web
The problem
Centralised the customer journey and operational data, reduced manual hand-offs and set up a documented AWS foundation.
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.
Fashion-commerce recommendations usually optimise for another purchase without understanding what the customer already owns.
What was built
Led architecture and hands-on engineering for an online booking platform: Python APIs and the AWS deployment architecture, integrated with Paystack, Sage Accounting, Zoho Bigin and Zoho SalesIQ.
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.
Fashionly grounds recommendations in the user's wardrobe, builds outfits from existing items and recommends products only where a genuine wardrobe gap exists. Khanya, a LangGraph stylist with about 15 typed tools, handles wardrobe access, catalogue search, saved looks and human-stylist bookings.
Stack
- Python
- AWS
- Paystack
- Sage
- Zoho
- Next.js
- Supabase
- PostgreSQL
- Kotlin
- Jetpack Compose
- LangGraph
- Zod
- Paystack
- Azure
- LangSmith
- Next.js
- Kotlin
- Supabase
- LangGraph
- MongoDB
- SSE
Highlights
- Python APIs and AWS deployment architecture
- Paystack, Sage Accounting, Zoho Bigin and Zoho SalesIQ integrations
- 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
- Khanya: a LangGraph tool-calling stylist with about 15 typed tools
- MongoDB-checkpointed conversation memory and SSE streaming of tool progress and grounded product cards
- Request-scoped Supabase clients with row-level security on every request
Infrastructure choices
- AWS
- Supabase with PostgreSQL RLS
- Supabase with RLS
- MongoDB checkpoints
- SSE
Outcome
Centralised the customer journey and key operational data, reduced manual hand-offs and established a documented AWS foundation for future development.
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.
A working end-to-end MVP across web and Android: wardrobe management, catalogue discovery, conversational styling, saved looks and human-stylist booking.