Sparklet vs TouchGFX: Cross-Platform Portability vs STM32 Lock-In

TouchGFX is a capable embedded GUI framework — when you are committed to STM32. For teams building on Renesas, NXP, Infineon, or managing multi-vendor hardware roadmaps, Sparklet provides the cross-platform portability, MISRA C compliance, and pure C foundation that TouchGFX cannot.

Get Free Evaluation Contact Sales

What Is the Difference Between Sparklet and TouchGFX?

TouchGFX is an embedded GUI framework developed by STMicroelectronics, available free of charge for STM32 microcontrollers. It is built in C++, accelerated via the STM32 DMA2D peripheral, and comes with TouchGFX Designer — a graphical design tool for building embedded UIs. TouchGFX is STM32-specific by design; official support does not extend to Renesas, NXP, Infineon, or other silicon vendors.

Sparklet is a royalty-free embedded GUI framework written in pure C by Embien Technologies. Unlike TouchGFX, Sparklet is silicon-agnostic — the same codebase and widget library runs across nine hardware platforms including Renesas RH850, RA series, NXP i.MX RT1170, STM32, Infineon TRAVEO T2G, and Rockchip, without re-implementation. Sparklet is MISRA C compliant and includes Flint UI Designer, a full WYSIWYG no-code design tool that generates optimised C code for any supported platform.

This page provides a fair, factual comparison — including where TouchGFX genuinely excels — so you can make the right decision for your specific project and hardware roadmap.

Sparklet vs TouchGFX: Head-to-Head Comparison

CriteriaSparkletTouchGFX
LanguagePure CC++
License ModelRoyalty-free (per developer seat)Free on STM32; per-unit on other platforms
Platform Support9+ platforms — Renesas, NXP, STM32, Infineon, Nuvoton, Rockchip, Linux, WindowsSTM32 only (officially)
MISRA C CompliantYes — full MISRA C complianceNo — C++ codebase is not MISRA C compliant
Hardware AccelerationDMA2D, D/AVE2D (Renesas), Mali GPU, Chrom-ART — multi-vendorDMA2D — STM32 only
Visual Design ToolFlint UI Designer — WYSIWYG, UML state machines, animation, FigmaTouchGFX Designer — screen builder with animation support
Cross-PlatformYes — single codebase, platform-specific HALNo — STM32-specific architecture
Professional SupportDirect-to-engineer support from EmbienST ecosystem and community forums

Sparklet vs TouchGFX: Four Critical Differences

Explore platform lock-in, C vs C++, licensing economics, and design tool capabilities.

The Strategic Cost of STM32 Lock-In

The most significant risk with TouchGFX is not a technical flaw — it is an architectural constraint. TouchGFX is designed exclusively for STM32 microcontrollers. The framework's hardware acceleration, driver model, and vendor support are all built around the STM32 ecosystem.

For product teams with multi-vendor hardware roadmaps, this creates a re-implementation tax:

  • Silicon shortage migration: When STM32 supply tightened globally, teams on TouchGFX found themselves unable to migrate to Renesas or NXP alternatives without rewriting the entire GUI layer. Teams on Sparklet swapped the HAL layer and kept all widget and screen code unchanged.
  • Multi-product portfolio: An organisation building automotive clusters on Renesas RH850 and industrial panels on STM32 cannot share a codebase with TouchGFX. With Sparklet, the same widget library and Flint-generated screen code deploys to both targets.
  • Next-generation hardware: As product roadmaps move to MPU platforms (NXP i.MX 8, Rockchip RK3506G2), TouchGFX does not follow. Sparklet spans MCU to MPU with the same framework.

Explore all Sparklet-supported platforms to see the full cross-platform coverage.

Three Reasons Teams With Multi-Vendor Roadmaps Choose Sparklet

Features Image

Sparklet at a Glance: What You Get That TouchGFX Cannot Provide

Four concrete capabilities that differentiate Sparklet from a platform-locked, C++ framework.
9 Platforms

9+ Hardware Platforms

The same Flint-generated screen code deploys to Renesas, NXP, STM32, Infineon, Nuvoton, Rockchip, and more. No per-platform re-implementation — ever.

MISRA C

Full MISRA C Compliance

Pure C codebase, static memory pools, no C++ runtime. Automotive and medical safety programmes can use Sparklet where TouchGFX is excluded by language.

Flint Designer

Flint: UML State Machines + Figma Import

Visual state machine editor, animation timeline, and Figma asset pipeline — capabilities not available in TouchGFX Designer, generating portable C not platform-locked C++.

Royalty Free

Zero Per-Unit Royalty, All Platforms

Sparklet's per-seat licence covers all silicon equally. No per-unit royalty on Renesas, NXP, or any other platform — unlike TouchGFX outside STM32.

Migrating from TouchGFX to Sparklet

Embien's services team has executed migrations from TouchGFX for multiple customers. This is the structured path.
Screen Inventory

1. Screen Inventory

Catalogue every TouchGFX screen, container, and state machine transition in the existing application. Document C++ class hierarchies and identify which application logic is coupled to the TouchGFX widget model.

Flint Rebuild

2. Flint Rebuild

Rebuild each screen visually in Flint UI Designer. Flint's WYSIWYG approach means rebuilding a screen — including state machine wiring and animation — is typically faster than reading and understanding the equivalent C++ code in the TouchGFX application.

HAL Integration

3. HAL Integration

Configure Sparklet's HAL for the target hardware. On STM32, DMA2D acceleration is handled by the Sparklet GDI layer. For Renesas, NXP, or other silicon targets, the HAL configuration template for that platform is available.

Application Logic

4. Application Logic Port

Event handlers and data binding logic are reconnected through Sparklet's clean C API. Because Sparklet's architecture separates UI from application logic, this step benefits from any existing separation already present in the TouchGFX C++ code.

Frequently Asked Questions: Sparklet vs TouchGFX

Sparklet uses a royalty-free per-developer-seat licensing model — it is not free-of-charge like TouchGFX on STM32. However, the licensing cost is fixed per engineer on the project, with zero per-unit royalty at any production volume. For high-volume products, Sparklet's total licensing cost is typically lower than per-unit royalty models, and significantly lower than the engineering cost of re-implementing a GUI when silicon changes. A free evaluation binary and Flint UI Designer are available to try before purchasing.

Evaluate Sparklet on Your Target Hardware

Download the free Sparklet evaluation binary and Flint UI Designer. Runs on Windows simulator immediately — no hardware required to get started. Available for STM32, Renesas, NXP, Infineon, and all other supported platforms.

Get Free Evaluation