Moe QadanUX developer · Los Angeles

I do UX and frontend as one job.

I work on shared web platforms and build independent iOS apps, from design through production.

See the work How I work

A detail from the CarSpotter study

Toggle between a close crop of a car's headlight and the full car. The case study is always available.

Reveal the carBack to the detail

Toyota Camry.

A browser study of the crop and reveal interaction.

CarSpotter case study
Independent products

Built around real questions.

A daily spotting game, a free VIN scanner, and an AI diagnostic tool. Designed and built solo, with two open-source libraries from the same car projects.

VINly portfolio poster: a warm cream layout headlined "Scan any VIN. Know the car." over two angled iPhones, one showing the app home with a Scan a VIN button, the other a free public-record report for a 2024 Ford F-150.
Download now Independent product · iOS

VINly

Scan a VIN and see the car's public safety record free: recalls, complaints, crash tests, fuel cost, and real listings nearby. Out now on the App Store.

Case study
Download on the App Store vinly.dev
ChatOBD2 portfolio poster. The headline "Your car is talking. ChatOBD-2 translates." in white and blue on a near-black engineering grid, beside the real app showing a live diagnosis of a P0420 catalyst fault on a 2010 Toyota Prius.
In QA Independent product · iOS

ChatOBD2

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

Currently in QA and field testing. Not yet publicly released.

Case study
Open source

Two open-source libraries.

Two libraries from the car apps: one tests the Bluetooth connection, one reads public vehicle records.

elmulator

A scriptable ELM327 adapter for testing the car app's Bluetooth code in CI, without a car or adapter. Open source · Swift + Python · GitHub Action

vinplain

The public record for a VIN in one typed call: recalls, complaints, crash ratings and fuel economy. No API key, no runtime dependencies. Open source · TypeScript · npm
Platform work

And the platform work.

I own the full stack across MagTek's eleven sites. Earlier, I built advisor portals at InvestCloud for more than fifty institutions.

MagTek experience poster. A clean light corporate layout with the MagTek.com homepage in a browser frame and a metric band.

MagTek

Current

Full-stack Platform Ownership

2022 to present
Platform context
  • $11B processed annually
  • 99.9% uptime
  • 11 sites on the shared platform
My contribution
  • 100% full-stack ownership
  • 100+ shared components

Platform figures are company-reported.

Case study
InvestCloud experience poster. A navy financial layout with two advisor-portal browser windows and a client roster.

InvestCloud

Earlier

Frontend Implementation & Design Translation

Earlier
Platform context
  • 50+ institutions on the platform
My contribution
  • 0 → production portals
  • Hand-written CSS systems

Deployed for Chase · Cetera · Northwestern Mutual · Voya · SVB · East West

Case study
How I work

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.

Read the long version
  1. 01 Read

    Start with the system.

    Long-running platforms already have rules. Before I design anything, I read the code, content, and analytics to see what the system actually does.

    MagTek platform
  2. 02 Pick

    Choose the structure.

    A lot of bugs come from a structure that doesn't fit the work. I choose the components, data model, and prompt structure once, then reuse them.

    vinplain
  3. 03 Use

    Use AI carefully.

    I keep prompts in source, validate the output, and put deterministic checks before the model. I use AI only where the result can be reviewed and shipped.

    ChatOBD2, in QA
Contact

Tell me what you're working on.

Send a message LinkedIn GitHub