Unit fields

Every value-plus-unit field asks the user to think like a database. Drop the unit dropdown: collapse one value plus one unit picker into one natural-language field that stores the canonical number.

This wins for one value plus one unit pair. Keep the form structure people expect, but stop making each value carry a separate required unit picker.

The /docs#forms-ux demo shows five realistic before/after forms:

• Finance: Without lingo, Budget value plus currency picker, rate value plus %/bps mode, settlement value plus duration unit. With lingo: 1250 usd, 25 bps, 2 days. The app stores USD, percent, and days. Currency is built in; no live FX implied.
• Recipes: Without lingo, Ingredient amount plus cup/mL/L picker, oil amount plus tsp/tbsp/mL picker, cook-time picker. With lingo: 1.5 cups, 2 tbsp, 45 min. The app stores mL and minutes while accepting prep-sheet wording.
• Engineering: Without lingo, Clearance, pressure, axial load, and torque each require their own unit selector. With lingo: 3/4 in, 32 psi, 120 lbf, 35 Nm. The app stores mm, kPa, N, and N⋅m. Force and torque are built in.
• Fitness: Without lingo, Body weight, distance, duration, and energy each carry a separate mode choice. With lingo: 165 lb, 5 km, 42 min, 450 Calories. The app stores kg, meters, minutes, and kcal for analytics.
• Medical: Without lingo, Dose volume, interval, height, and cuff pressure selectors create a noisy intake layout. With lingo: 1.5 tsp, 6 hr, 5'11", 120 mmHg. The app stores field-local canonical values; medication units remain domain-owned.

Unit-entry mistakes are expensive. The Mars Climate Orbiter was lost to pound-force vs newton-seconds; the Gimli Glider ran out of fuel from a lb/L vs kg/L slip; insulin doses measured in mL instead of units are a documented harm class. A single canonical field removes the class.