Ernson Dorce
Budget: $10 – $30 USD
I’m building a custom embedded system and have reached the stage where the user interface has to come to life. The core hardware and low-level firmware are already in place; what’s missing is a clean, responsive interface that will run directly on the device.
What I need
• A complete UI layer that launches on boot, handles all screen updates and touch/button events, and communicates with the existing application logic through clearly defined APIs.
• Source code (C/C++, Qt, LVGL, or another lightweight framework you recommend) plus a brief build guide so I can reproduce the binaries on my side.
• Layout assets, icons, and style guide so future screens can be added with consistent look and feel.
• Short, step-by-step documentation outlining how to integrate your UI module into the current firmware image.
Acceptance criteria
– UI starts in under three seconds on the target board.
– No screen tearing or noticeable lag when navigating between pages.
– Memory footprint stays within the available on-board RAM; please call out any trade-offs you make to achieve this.
– Code compiles without warnings on GCC/Clang and passes a basic static-analysis scan.
You’ll have direct access to a test firmware stub and emulator so you can validate your work even if the physical board is not on hand. I’m available for quick feedback cycles and will supply any extra technical details you require.
What I need
• A complete UI layer that launches on boot, handles all screen updates and touch/button events, and communicates with the existing application logic through clearly defined APIs.
• Source code (C/C++, Qt, LVGL, or another lightweight framework you recommend) plus a brief build guide so I can reproduce the binaries on my side.
• Layout assets, icons, and style guide so future screens can be added with consistent look and feel.
• Short, step-by-step documentation outlining how to integrate your UI module into the current firmware image.
Acceptance criteria
– UI starts in under three seconds on the target board.
– No screen tearing or noticeable lag when navigating between pages.
– Memory footprint stays within the available on-board RAM; please call out any trade-offs you make to achieve this.
– Code compiles without warnings on GCC/Clang and passes a basic static-analysis scan.
You’ll have direct access to a test firmware stub and emulator so you can validate your work even if the physical board is not on hand. I’m available for quick feedback cycles and will supply any extra technical details you require.