Why it matters: the current v0.6 cycle makes the first-run mobile experience clearer for guided customer rollouts and technical evaluation.

The current v0.6 Beta cycle is tightening the first-run mobile experience for guided rollouts. Evaluators now land on a clearer pilot activation path, operator preview surfaces use the larger touch-target system, and scanner behavior is being aligned across native iOS, native Android, and browser fallback paths. This remains a guided rollout/Beta motion, not a broad public launch.

Why it matters: buyers can now evaluate the operator workflow across phone, tablet, and browser install paths without changing backend integrations or deployment model.

v0.5.2 expands where Eryxon Flow can run. Native iPhone/iPad and Android packaging now sit alongside an installable PWA, all sharing the same touch-first operator shell. That gives evaluators and rollout teams a clearer path to test shop-floor usage on the devices they already use.

Why it matters: the May release line made Eryxon easier to connect into existing manufacturing systems and easier to deploy in self-hosted or integration-heavy environments.

The May release line improved Eryxon's integration posture for manufacturing teams that need more than a standalone web app. FrePPLe and Odoo planning adapters landed, MQTT gained retry and dead-letter protection, and the MCP server added HTTP/SSE plus Docker deployment paths for self-hosted rollouts. v0.5.1 then tightened the release posture and supporting documentation around that foundation.

Why it matters: technical evaluators hit fewer trust and deployment problems during spring cleanup work.

Across March and April, Eryxon tightened several rollout blockers that matter during evaluation: self-hosted Supabase support improved, false or unbuilt claims were removed from docs, login blockers were fixed, and the docs footprint became easier to trust in English, German, and Dutch. This work is less flashy than a feature launch, but it directly reduces rollout friction.

Why it matters: March closed the loop on batch execution so teams could track work more reliably from the floor through the API layer.

v0.4.1 strengthened batch execution from both the operator and integration side. Batch lifecycle APIs, weighted time distribution, and webhook events made batch tracking more usable in real workflows, while the surrounding operator and routing cleanup reduced friction for day-to-day execution.