Shipped another Trier OS build — looking for real feedback
At this point it’s less about “can it work” and more about “will it hold up in the real world.”
What has been tested in house:
Chaos testing across ~600 endpoints
Stability under bad conditions (offline, latency, partial failure)
Curious from others who’ve built large systems:
What actually broke when you scaled past “it works”?
What’s your approach to real stress testing (not just happy path)?
I have been fortunate enough to have also trained drivers on DSD applications across 3000 ends points so I understand stability and how important it is. I was the one that would break the application and report back to Dev's because I believe happy paths are not the real world.
With version 3.4.0
Scan a QR code at the machine → instantly pull up the work order → one tap to:
start work
complete
transfer
or put on hold (with reason codes)
No searching. No navigating menus.
The goal was simple:
reduce friction at the point of work to near zero
In a plant environment, even small delays add up fast — so this was designed to be as close to “scan and act” as possible.
Curious how others are handling this:
Are you tying assets directly to QR/NFC?
Are there and PWA issues that you have ran into and what were your solutions?
Top comments (0)