Low migration cost
Preserve a WinForms-style mental model so .NET desktop developers can move toward cross-platform GUI runtime work more naturally.
LVGLSharp
About
LVGLSharp is a cross-platform GUI runtime for .NET developers built on top of LVGL, with the goal of preserving a WinForms-style development experience while bringing UI work into lighter, more trimmable, and more host-flexible runtime environments.
- LVGLSharp
- LVGL
- WinForms-style
- Cross-platform Runtime
Current contributors
5
Core direction
IoT + Runtime
Source mirrors
GitHub + Gitee
Current project
LVGLSharp
LVGLSharp core values
LVGLSharp is not only trying to answer whether a UI can be rendered, but whether it can be built in a way that is sustainable, portable, and engineering-friendly over time.
Built for long-term evolution
Avoid becoming a one-off API wrapper and instead keep investing in runtime layering, host expansion, AOT readiness, and device-side paths.
Engineering that can ship
Focus on real runtimes, real hosts, and real build-and-release workflows instead of stopping at concept demos or single-platform experiments.
Who it is for / target scenarios
LVGLSharp is not a universal answer for every GUI problem, but it is especially relevant for the following users and environments.
.NET desktop developers
Useful for developers with WinForms experience who want to carry that knowledge into cross-platform and device-oriented runtime environments.
Device and edge-side projects
Useful when a project needs local interaction, status dashboards, operator panels, or lightweight deployed UI on the device side.
Cross-platform runtime exploration
Useful for teams and individuals exploring Windows, Linux, Headless, Remote, and other multi-host runtime paths.
AOT and lightweight deployment
Useful for engineering scenarios that care about NativeAOT, self-contained publishing, trimming, startup speed, and runtime dependency control.
Why IoTSharp would build GUI / LVGLSharp
Given the rest of the portfolio, LVGLSharp looks like a natural extension rather than a disconnected side project.
Devices eventually need UI
A team that spends years around device management, edge systems, and field-side tooling will eventually run into local interfaces, status displays, and operator panels.
Desktop developer habits still matter
Many .NET developers understand WinForms well, but device and cross-platform environments do not map cleanly onto classic desktop stacks, which creates space for a new runtime layer.
IoT and GUI naturally converge
Once a team already understands connectivity, cross-platform runtime concerns, packaging, and engineering workflows, pushing further into GUI runtime work is a logical next step.
Where LVGLSharp fits
LVGLSharp is best understood as the UI-runtime branch of the broader IoTSharp engineering direction. It carries the team’s cross-platform, device-side, and engineering-oriented experience into the GUI layer.
WinForms over LVGL
Preserve the familiar WinForms mental model while moving rendering onto the lighter and more portable LVGL stack.
Multi-host runtime work
Keep expanding across Windows, Linux, Headless, Remote, and future device-side host implementations instead of stopping at a single desktop runtime.
Device-oriented UI path
Given the wider IoTSharp background, LVGLSharp makes more sense as a GUI runtime path for devices and edge environments than as a simple desktop control wrapper.
How the IoTSharp team presents itself
The organization page suggests that IoTSharp is building a wider open-source portfolio rather than maintaining a single isolated product.
IoT platform capabilities
The core IoTSharp project focuses on device management, data collection, processing, status detection, and remote control, which signals a long-term interest in real device connectivity and platform-level workflows.
Infrastructure components
Projects such as mqttclient, TaosConnector, and AspNetCore.HealthChecks show that the team also invests in communication, data access, and service-governance building blocks.
Engineering and tooling extensions
Projects like SilkierQuartz, iotsharp.github.io, and now LVGLSharp suggest that the team keeps extending into scheduling, websites, developer experience, and cross-platform UI/runtime tooling.
Team capability map
Taken together, the IoTSharp repositories suggest a capability map that spans several adjacent layers.
Devices and protocols
Device management, remote control, MQTT access, embedded integration, and cross-platform connectivity.
Data and storage
Data collection, processing, visualization, database access, and industrial data pipelines.
Services and scheduling
Health checks, job scheduling, background execution, service governance, and operations support.
UI and runtime
Websites, developer tooling, cross-platform GUI runtime work, and the LVGLSharp UI engineering path.
Representative IoTSharp projects
The repositories below are visible on the current public IoTSharp organization page and help illustrate the team’s long-running technical priorities.
IoTSharp
mqttclient
SilkierQuartz
TaosConnector
AspNetCore.HealthChecks
LVGLSharp
An open-source IoT platform focused on device management, data collection, processing, visualization, and remote control.
A high-performance cross-platform MQTT client spanning embedded systems, Linux, Windows, and Mac.
Quartz hosting and web management tooling that reflects the team’s scheduling and operations-side experience.
An ADO.NET / ORM / statement access component for TDengine, showing the team’s data access direction.
A set of health-check related components that reflects service-governance and infrastructure interests.
The team’s current extension into cross-platform GUI runtime work, WinForms-style developer experience, and device-side UI.
Current contributors
The names below come from the current repository history via git shortlog -sn HEAD, with bot accounts excluded.
Organization and source entry points
Use these links if you want to understand the broader IoTSharp project landscape or continue into the LVGLSharp source.
Contact on WeCom
If you would like to follow project updates, discuss engineering cooperation, or reach the team directly in China, scan the Enterprise WeChat QR code below.
WeCom
LVGLSharp WeCom QR Code
Scan this code to reach the team on Enterprise WeChat.