04 / Industrial software / Cross-device
WinpackOne system, several kinds of screens.
A factory automation and tracking ecosystem used at a high-volume cardboard manufacturing plant. I worked on a shared Flutter app family spanning mobile, tablet, and Android TV, adapting workflows to different contexts and screens.
Mobile · Tablet · Android TV
Flutter · Provider · Custom state architecture · Android TV
01 / Context
The setting.
A factory automation and production-tracking ecosystem for a high-volume cardboard manufacturing plant.
02 / My contribution
Where I worked.
- Designed and deployed a shared Flutter application family across mobile, tablet, and Android TV.
- Adapted a tracking system for different device contexts and factory workflows.
- Worked with Provider and a custom state architecture.
- 01Shared workflow
- 02Mobile
- 03Tablet
- 04Android TV
03 / Engineering focus
The interesting part.
The same industrial process needs different interfaces depending on where and how a device is used. The work involved adapting workflows for screen size, input behaviour, and the context of each device.
04 / Impact
What changed.
Increase in target operational throughput
Resume-reported results. These describe product outcomes, not independently audited measurements.
05 / Reflection
What stayed with me.
A shared codebase pays off when the experience still makes sense on each device.
Have a similar problem to work through? Get in touch ↗