Eryxon Flow

Customer problem: operators lose trust quickly when login, scan, or launch behavior differs between native, PWA, and browser paths or when plant connectivity is inconsistent. We're improving how scan, login, and operator entry points behave across native apps, the installable PWA, and browser fallback paths. The goal is simple: no guesswork for operators, and fewer rollout surprises in real plants with inconsistent connectivity.

We're expanding Eryxon Flow beyond the browser with guided native iPhone/iPad and Android paths plus an installable PWA. The goal is a predictable touch-first operator experience across the devices metalworking teams already use, without changing the core backend or rollout model.