Hi HN! Frontend dev here. At my day job the same bug kept shipping: layouts look fine in English, then the German translation (+35% length on average) overflows a fixed-width button in production.
Devs know pseudo-localization from the code side, but designers never see it — by the time strings come back from translators, the design is "done". LocaleProof runs pseudo-localization and worst-case length expansion directly on Figma text layers and checks every
text node against its container, so overflow shows up at design time.
Technical notes: pure client-side (TypeScript + esbuild + React in the plugin iframe), no backend, manifest networkAccess: none. Per-language expansion ratios are baked in from published localization data; restore is one click (originals are cached before mutation).
Free on Figma Community: https://www.figma.com/community/plugin/1652797384930391326. Curious how your team catches i18n layout bugs today.
Voice makes sense as a third input mode, but it seems like a poor replacement for the controls you need while stressed or time-constrained. In a car the real UX test isn't "can the system eventually understand me?", it's "can I do this eyes-free, in noise, with high confidence, in under a second?" That's why defrost, wipers, volume, and temperature feel fundamentally different from "navigate to X". Touch is fine for discoverability, voice is fine for occasional commands, but safety-critical/high-frequency actions still want dedicated hardware.