From a PDF lookup to a search box
To configure a custom gas, users looked up its molecular weight and response factor in a PDF table and typed them in. In my first weeks at the distributor I built a proposal, as a working page, that replaces the lookup with search and auto-fill. The manufacturer, SENKO, agreed to implement gas selection and automatic response-factor entry without a firmware change; other parts are still under discussion.
Role Found the problem, designed and built the proposalResult The manufacturer agreed to build part of it

A name that fits the screen
The detector showed only “USER GAS1”, so the operator in the field could not tell which gas was configured. The proposal adds a display name of up to 12 characters, with a counter, so the screen shows “2-MeTHF” and the response factor beside it.
Which gas? The operator can't tell.
The gas, by the name you gave it.
The measurement screen as the proposal page simulates it, with the proposal’s example readings.
Search by any name
A dropdown of hundreds of gases is unusable, so I built search. It matches English name, alternative name, formula, Chinese name and CAS number, and shows why each result matched. The built-in database covers 840+ gases.
Keep the old way
Manual mode stays for gases that are not in the database, so nothing existing breaks. Switching to it disables search and makes every field editable, the way the software already worked.

Frame it as customer experience
I built the proposal as a page the founder and the manufacturer could click through instead of describing it in an email. I pitched it as a better experience for their users and left criticism of the manufacturer’s design out of it.
- CONTEXT
- First weeks using the software as a new hire at the distributor
- STACK
- HTML · CSS · JavaScript