Back to Projects
A
Engineering

AJ Luxe

Full-Stack Developer

Next.jsTypeScriptRadix UITanStack QueryTailwind CSS

About the Project

AJ Luxe is an e-commerce platform for a perfume retailer, built as two Next.js applications sharing a design system. The storefront covers the full purchase path — shop, collections, individual product pages, cart, checkout, and a customer account area with order history and profile management. The merchant console is a separate dashboard spanning products, categories, orders, customers, reviews, analytics, and a customer message inbox, so the retailer runs the whole business without touching code.

What It's Made Of

Storefront

Next.js · TanStack Query · Tailwind

The full purchase path: shop and collection browsing, individual product pages presenting imagery and scent notes, cart, checkout, and a customer account area with order history and profile management. Perfume is a high-consideration purchase made on a small screen, so this surface lives or dies on presenting product imagery well without becoming slow.

Merchant console

Next.js · separate deploy

Where the retailer runs the business without touching code: products and categories, orders, customers, reviews, analytics, and an inbox for customer enquiries. A separate application rather than an admin route, so the storefront bundle carries none of it.

Shared component layer

Radix UI primitives · design tokens

Extracted so two separately deployed apps still look like one product. The alternative — duplicating UI in both — produces two codebases that drift the moment either ships a fix, which is exactly the failure this was built to avoid.

Key Highlights

  • Built the storefront purchase path end to end: collection and shop browsing, per-product pages, cart, checkout, and a customer account area with order history
  • Shipped a merchant console covering products, categories, orders, customers, reviews, analytics, and an inbox for customer enquiries
  • Built a shared component layer on Radix primitives so the storefront and admin stay visually consistent while deploying separately
  • Managed server state with TanStack Query and validated every form with react-hook-form, keeping checkout and admin data entry resilient
  • Set up Husky pre-commit hooks so linting and type checks run before anything lands

Technical Challenges

Perfume retail is a high-consideration purchase made on a small screen, so the storefront lives or dies on how well it presents product imagery and scent notes without becoming slow. The consumer and admin apps also needed to look like one product despite being separate deployments, which is what drove extracting the shared component layer rather than duplicating UI in both — the alternative is two codebases that drift apart the moment either one ships a fix.