New to ForgeUI
Prepare Studio, create a first screen, preview it and flash the reference hardware.
Documentation Centre
ForgeUI is a semantic embedded application platform built on LVGL.
Learn the Practical LVGL and Native Component platforms, physically proven Hardware Examples, generated Runtime SDK, developer-owned UserEvents, hardware-profile-driven export and current ESP32-P4 evidence.
A guide to the live browser workspace, account-backed projects and assets, Hosted firmware builds, target verification, browser flashing, optional AI tools and native ESP-IDF/LVGL export.
Discover Hosted Studio →Current supported targets
Waveshare ESP32-P4-WiFi6-Touch-LCD-7B · Landscape
Guition 10.1-inch tested P4 v1.x/pre-v3 · Portrait
1024 × 600 + 800 × 1280 · ESP-IDF 5.5.4 · LVGL 9.2.2
View hardware details →Current status
44/44 practical LVGL 9.2 components are physically proven. Fourteen Native Components are current: six are PROVEN and eight are HARDWARE VALIDATED. Hardware Examples 01–03 are PHYSICALLY PROVEN on ESP32-P4.
Generated SDK
Control any used Fi icon through generated visibility, opacity and colour APIs, with optional click hooks routed through 95_UserEvents.
Authoritative documents
Getting Started is the clearest first step. The product documents explain ForgeUI; the engineering maps preserve the detailed architecture and generated API contract.
Authoritative u-blox NEO-8 UART1 wiring, live NMEA, fix data and checksum-valid UBX request/response physical proof.
Authoritative physical proof record for the stock-C6 Wi-Fi, verified Open-Meteo HTTPS, forecast, time, Fi icon and dynamic local-background runtime.
Authoritative physically proven ESP32-P4 to stock ESP32-C6 SDIO, Wi-Fi, TLS and HTTPS architecture used by connected ForgeUI exports.
PN532 software-SPI wiring, identity, ISO14443A polling, UID reading, removal and logical de-duplication proof.
MB85RC256V shared-I²C identity, write/read/verify and complete power-cycle persistence proof.
Board-specific wiring, generated contracts, developer ownership, startup behavior, troubleshooting and accepted physical proof for two buttons and two LEDs.
Audited pin ownership, electrical restrictions, allocation register and physical evidence for the Waveshare ESP32-P4-WIFI6-Touch-LCD-7B.
Authoritative implementation and physical-evidence ledger for Standard widgets, Native Components, Runtime features and Hardware Examples.
Generated application-facing APIs, UserEvents, naming, ownership, feature gating and current proof boundaries.
Authoritative engineering journal for improvements, resolved and active issues, validation history and proof priorities.
Set up ForgeUI on a fresh Windows system, launch Studio, create and preview a first project, build and flash, then continue in a standalone ESP-IDF export.
Configure the optional OpenAI API key, local .env environment variable, security practices and troubleshooting for ForgeUI Studio AI features.
Product and capabilities overview covering AI-assisted design, Interactive Assets, native LVGL runtime APIs, System Runtime and standalone ESP-IDF export.
The creator story, engineering philosophy, platform direction, open-source credits and contact context behind ForgeUI Studio.
Authoritative architecture, proven scope, current priorities, physical validation boundaries and save-point history.
Detailed source, subsystem and ownership map for the Studio, generated runtime, connectivity, storage and export paths.
Generated public APIs, developer hooks, output-only controls, presentation-only decisions and file-ownership boundaries.
Canonical Fi Icon pipeline, generated 90/95/96 ownership, runtime presentation, optional click behavior and future semantic direction.
Practical integration patterns for GPIO, tasks, queues, buses, sensors, networking, storage and developer-owned application modules.
Download the Windows bootstrap utility that verifies the ForgeUI workspace and repairs Studio dependencies where possible.
Download .bat ↓Prepare Studio, create a first screen, preview it and flash the reference hardware.
Inspect generated C, connect event hooks and continue in a standalone ESP-IDF project.
Work from proven hardware requirements through controls, flashing and practical diagnostics.
Run generated C with real LVGL 9.2.2 in WebAssembly. Workflow, native interaction and Sim V1 limits.
Supported ESP32-P4 and ESP32-S3 display and headless profiles, with experimental status and physical-proof boundaries.
Integrated ESP-IDF BUILD, authoritative live MONITOR and read-only I/O insight in the Studio workspace.
Editable, board-specific projects with wiring, generated contracts, developer-owned hardware code and physical proof.
PHYSICALLY PROVEN ON ESP32-P4 across both GPIO input → UI and UI → GPIO output paths.
PHYSICALLY PROVEN identity, write/read/verify and complete power-cycle persistence.
PHYSICALLY PROVEN PN532 polling, UID reading, removal and de-duplication.
Review the audited Waveshare ESP32-P4 pin ownership and proven GPIO2 / GPIO3 / GPIO4 / GPIO5 allocation.
Connect GPIO and device code through the Runtime SDK and genuine UserEvents without touching private LVGL objects.
44/44 practical LVGL 9.2 components physically proven, plus the individual status of all 14 current Native Components.
Browse all 14 current semantic components with generated contracts, interaction models and ESP32-P4 status.
One semantic Canvas component, private LVGL composition, stable identity and generated Runtime APIs.
Understand Registry ownership, preview/export parity and the complete proof gate.
Use proven semantic value, units, status and progress APIs plus an optional click hook.
Project typed measurements, thresholds, trend, timestamp and colour through six semantic APIs.
Bind 1–8 zero-based logical channels and master control to developer-owned hardware.
Preserve customised hooks safely across regeneration and distinguish genuine user actions from setters.
0 active issues · Current proof target: Waveshare ESP32-S3 Touch LCD 7B physical parity closed across 59 widgets/components.
Install prerequisites, run preflight and reach the first hardware flash.
Use AI-assisted tools, Canvas, Inspector, Preview and standalone export.
Understand generated UI, developer hooks and native ESP-IDF ownership.
Use generated setters, commands and genuine-user callbacks without editing private LVGL code.
Select and persist the authoritative board target, dimensions and generated project configuration.
Review the physically proven LVGL 9.2 foundation; Lottie remains intentionally excluded.
Control any used Fi icon through generated visibility, opacity and colour APIs, with optional click hooks routed through 95_UserEvents.
Use the validated target and either integrated or external build commands.
Interactive APIs, CMake registration, native assets and regeneration.
Diagnose setup, build, port, asset, callback and runtime failures.
Find API directions, file ownership and current target versions.
Studio workflow
Use Hosted build and browser flash for the direct route to supported hardware, or preserve normal C, CMake, Git and ESP-IDF practices after standalone export.