Embedded GUI Modernization

Your machine control logic works. Your display UI does not reflect it. Embien's GUI modernization service decouples the display interface from your backend firmware and replaces it with a full-colour, animated modern HMI — without disrupting the application code that runs your product.

Start Modernization Explore Services

What Is Embedded GUI Modernization?

Embedded GUI modernization is the process of replacing an outdated embedded display interface — monochrome, low-resolution, character LCD, or visually dated TFT — with a modern, full-colour, animated HMI, without necessarily rewriting the underlying machine control firmware. The core principle is decoupling: the UI layer is architecturally separated from backend logic, rebuilt using the Sparklet embedded GUI framework and Flint UI Designer, and reconnected to the existing backend via a clean, documented interface.

The result is a product that looks and behaves like a modern embedded system while retaining the proven, validated backend firmware that controls the machine. The OEM avoids the cost and risk of a complete product rewrite — and avoids re-validating backend firmware that has been in field operation for years.

Embien's GUI modernization service is part of its embedded GUI development services portfolio. It is the appropriate service when a display upgrade is needed but a full product rewrite is not justified by the business case. For a practical engineering guide to the modernization process, see Modernize Legacy Embedded HMI.

Three Modernization Scenarios

Scenario 1 — New UI on Existing Hardware

The MCU and all backend firmware remain unchanged. The old display panel and its driver are replaced with a modern colour TFT. Sparklet is ported to the new display hardware, and a new GUI is built in Flint UI Designer using the same data the old display was already receiving. The backend firmware requires no modification — only a new display driver and a new UI build are deployed. This is the lowest-risk modernization scenario and the most common starting point for industrial and medical products with proven backend firmware whose machine control team is unavailable or unwilling to touch validated firmware.

Scenario 2 — Platform Migration

The legacy MCU is end-of-life, under-powered, or no longer available. Both the MCU and the GUI library are replaced — but the backend machine control logic and communication protocols (CAN bus, RS-485, Modbus, UART) remain unchanged. Sparklet is ported to the new MCU (STM32H7, NXP i.MX RT1170, Renesas RA8D1), and the new UI is designed in Flint from scratch against the existing backend data interface. This scenario delivers a significant improvement in display quality — typically moving from a 4-bit colour or monochrome panel to a full-colour IPS TFT with capacitive touch — while avoiding any need to re-port or re-certify machine control code.

Scenario 3 — Feature Expansion

The existing product is fully functional, but new display requirements cannot be met by the current GUI library — multi-language support (including Arabic), animations, new data visualisation widgets, or a new brand aesthetic. The existing MCU has sufficient performance headroom; only the GUI framework changes. Sparklet replaces the legacy GUI library (emWin, SWIM, LVGL, or custom pixel-drawing code). The UI is rebuilt in Flint, preserving all data connections to the backend. New screens, languages, and animations are added within the same engagement. The customer receives the Flint project source and Sparklet C code for future in-house maintenance.

Embien's Four-Step Modernization Process

A structured, low-risk approach — from legacy assessment to validated delivery with full source handover.
Assess

Step 1 — Assess

Embien reviews the existing display hardware, GUI library, application code structure, and backend data interface. Output: a modernization scope document agreed before work begins — no surprises in scope or cost.

Decouple

Step 2 — Decouple

The UI layer is architecturally separated from backend logic. A clean, documented interface is defined between the display subsystem and the machine control firmware. Existing CAN bus, UART, Modbus, or RTOS message interfaces are preserved and mapped to Sparklet widget properties.

Redesign

Step 3 — Redesign

The new UI is designed in Flint UI Designer — all screens, navigation flow, animation design, colour scheme, typography, and data layouts. A working prototype is shared for approval. The design accounts for the display hardware capabilities of the target modernized platform.

Deploy

Step 4 — Deploy

The approved UI design is implemented in Sparklet C code on the target hardware, connected to the existing backend data layer, and validated against the original HMI functional specification. Full source, documentation, and a knowledge transfer session are delivered at handover.

Modernization Scenario Summary

ScenarioTriggerSparklet ApproachBackend Firmware ChangeTypical Timeline
New UI on Existing HWDated display panel, poor UXNew Sparklet HAL for new display; Flint UI rebuildNone3–5 weeks
Platform MigrationMCU end-of-life or underpoweredNew MCU bring-up; full Sparklet UI rebuild in FlintMinimal — add data feed handler6–10 weeks
Feature ExpansionNeed animations, multi-language, new widgetsLegacy GUI library replaced by Sparklet; incremental rebuildNone4–8 weeks

What Modernization Delivers

Four outcomes every embedded GUI modernization engagement is designed to achieve.
Backend Preserved

Backend Firmware Preserved

Proven, validated machine control code runs unchanged. Embien modernizes the display layer only — no re-validation of machine control logic required.

Modern Visuals

Consumer-Grade Modern Visuals

Full-colour animations, smooth transitions, capacitive touch, and brand-consistent visual design — replacing character LCDs, static bitmaps, or early-generation TFT graphics.

In-House Maintainability

In-House Maintainability After Delivery

The customer receives the Flint UI project source and Sparklet C code. Future UI changes can be made in-house using Flint's WYSIWYG designer — no need to re-engage Embien for routine updates.

Royalty-Free

Royalty-Free at Any Volume

Sparklet's developer-seat licensing means the modernized UI carries zero per-unit cost across the entire installed base — whether 500 units or 50,000. No royalty compounding as the modernized product ships.

Frequently Asked Questions

Embien's approach starts with a legacy system assessment to identify which software components need to change and which can be preserved. The new UI is designed in Flint UI Designer, implemented in Sparklet C code, and connected to the existing backend via the preserved data interface — CAN bus, UART, RTOS queues, or direct memory. The backend firmware typically requires no modification. The result is a modern, animated HMI that coexists with the proven backend firmware.

Ready to Modernize Your Legacy Embedded HMI?

Share your current display hardware, MCU, backend protocol, and UI goals. Embien will scope the modernization and propose a risk-managed approach.

Start Modernization