Elixir
Elixir is an Iraqi e-commerce platform built around a creative core idea: shoppable reels. Merchants upload short video reels showcasing their products — with pricing and variants attached directly to the reel — and customers can add items to their cart and purchase without ever leaving the video they're watching. Think Instagram reels meets a storefront. The platform serves the Iraqi market with a mobile-first experience for both merchants and customers, sitting on top of a complex multi-role dashboard that powers everything behind the scenes.
I was one of two frontend developers responsible for the dashboard.
// the-work
The dashboard was one of the most role-heavy systems I've worked on. Admin, posts reviewer, accountant, customer support — each role with its own set of pages, permissions, and workflows. The surface area was large and the complexity was real.
My ownership within the dashboard was focused on two of its most critical areas: orders and finance.
The orders section is the heartbeat of any e-commerce platform — and on Elixir it was no different. I built the full orders pages including advanced filtering, order status management, and detailed order views that gave the team complete visibility into every transaction moving through the platform. Getting the filtering and the information architecture right on these pages mattered — the operations team lives inside them every day.
The finance section was where the real complexity lived. Elixir's financial model was built around a multi-wallet system — merchants, customers, and the platform itself each carrying balances with transactions flowing between them automatically on every order. On top of the automatic transaction layer there was a manual transaction system for adjustments and exceptions. I handled the full frontend of both — presenting a complicated financial reality in a way that the accountant and admin roles could actually work with clearly and confidently.
// the-outcome
Elixir pushed my frontend skills in a specific direction — handling complexity at the UI level. When the underlying business logic is genuinely complicated, the frontend developer's job is not just to display data but to make that complexity disappear for the person using the interface. That was the standard I held myself to on every page I built for this project.