Live Commerce Marketplace
Solo-built a production Flutter marketplace with real-time live streaming, auction bidding, and a full financial ledger — from buyer checkout through seller settlement and payout — for a regional e-commerce client.
I work across mobile, web, and backend — using AI as a multiplier, not a replacement for thinking. The goal is always the same: something that works correctly and holds up over time.
These are the projects I would want a hiring manager or client to review first. Each one starts with a production constraint and ends with a measurable result.
Solo-built a production Flutter marketplace with real-time live streaming, auction bidding, and a full financial ledger — from buyer checkout through seller settlement and payout — for a regional e-commerce client.
Built a bilingual Arabic/English quiz platform with two game modes — a host-led trivia board and live multiplayer Seen-Jeem rooms — backed by atomic Postgres RPCs to eliminate race conditions at scale.
Architected an Arabic-first SaaS platform connecting companies with HR freelancers for project-based hiring — including a custom pricing engine, a 13-phase ATS Kanban, five Gemini AI workflows, and end-to-end Moyasar payment processing with VAT compliance.
Designed, built, and launched an opinionated resume builder for tech professionals in 5 weeks — with Gemini AI bullet refinement, in-app purchases, and a Dockerized LaTeX-to-PDF pipeline that cut generation costs by ~60%.
I work best in teams where implementation quality matters as much as the architectural decision behind it.
First engineer to join. Own end-to-end delivery of client products across mobile and web, contributed to PRDs, client discovery, and hiring process alongside building the engineering culture from scratch.
Worked inside an existing Flutter codebase, led a UI overhaul, and cut iOS CPU usage in half by profiling and optimising hot render paths with iOS Instruments and Flutter DevTools.
A few essays and internal memos have turned into reusable thinking. The published set is small; the useful ideas are not.
The gap between a Flutter app that looks cheap and one that feels considered is rarely about features. It is about typography, motion, color discipline, and a handful of decisions most developers skip.
What actually goes wrong when you ignore bounded contexts in a growing codebase, and how to draw lines that hold up under real product pressure.
A walkthrough of a real codebase handed off after going wrong — what the patterns looked like, how I diagnosed the damage, and what the refactor actually involved.
If something here resonated, feel free to reach out.