We write the GUI firmware, not the glass. The packaged work is the widget tree, the screen flow, the input path, and the notes another engineer needs to change a screen later.
Most display products do not fail because someone picked the wrong widget library. They stall because the first screens were a demo, the fonts were an afterthought, and nobody can say what happens when a screen is added in the next revision.
This offer is the software that sits between your product logic and a panel that is already chosen. Typical work uses an LVGL-class stack. When a target and a constraint set call for it, we will compare that class of stack with Qt for MCUs or STM32 TouchGFX and write down why one of them fits. The comparison is a selection note, not a brand preference.
You keep the panel, the backlight, and the mechanical stack. We read the datasheet and the schematic enough to drive the interface the hardware already exposes. We do not design the display module.
