Moe Qadan Senior UX & frontend Los Angeles Send a message

I do UX and frontend as one job.

Design systems, frontend craft, and AI-native product engineering. Senior generalist working across long-running platforms and independent product surfaces.

02 The Garage Built by a car enthusiast

Built for the love of cars.

I'm a car guy who ships car apps — three of them, designed and engineered solo. A daily spotting game and an AI buyer's report, both on the App Store today, and an AI mechanic in your pocket on the way.

CarSpotter portfolio poster — tilted iPhone screenshots of the daily car-detail guessing game on a dark garage backdrop.
Flagship iOS · daily game

CarSpotter

The daily car-spotting game. Five cropped details, four answers, ten seconds — for the people who can name a chassis code from a single headlight.

  • Daily 5
  • 12 detail types
  • Spoiler-free share
Open the case study
VINly portfolio poster — a warm, cream layout fanning five iPhone screenshots of the AI used-car buyer report.
Flagship iOS · AI report

VINly

A used-car listing in, a priced buyer's report out — verdict, opening offer, walk-away floor. Out now on the App Store.

Case study
ChatOBD2 portfolio poster — a light blue tech layout with the AI car-diagnostics app and an OBD-II adapter.
Coming soon iOS · AI diagnostics

ChatOBD2

Your AI car mechanic. Plug in an OBD-II adapter, ask your car anything, and get a real diagnosis in plain English.

Case study
03 Experience Inside a team

And the work I've shipped inside a team.

Two companies, two postures. A long-running multi-site platform where I own most of the frontend, and advisor portals deployed across more than fifty wealth and banking institutions.

04 How I work A method, not a manifesto

A lot of the work I take on looks like repair. A platform that grew without a system. A site that ranks well and converts badly. A frontend that ships fine on Chrome and falls apart on iOS. Existing AI tooling that needs a real home in the codebase.

01 Read

The constraints first.

Every long-running platform has opinions. Every team has history the wireframes don't capture. The first job is reading what's already true before drawing anything.

02 Pick

The structure carefully.

Most production breakage lives in the gap between intent and structure. Pick the right substrate (typed components, shared partials, prompt modules) once, ship for years.

03 Use

AI where it earns its place.

Prompts as production code. Schema-bound outputs. Deterministic layers in front of every model call. AI in the build, not the product, until it's structured enough to ship.

05 Contact

If you're working on something for the web,
I'd like to hear about it.

For project questions, design or engineering conversations. Replies within a day.