New to ForgeUI
Prepare Studio, create a first screen, preview it and flash the reference hardware.
Docs menu
Documentation Centre
ForgeUI Studio Documentation
Design, preview, export and run native LVGL interfaces on ESP32-P4 hardware.
Learn the visual workflow, generated C architecture, ESP-IDF integration and current hardware path without treating the Studio as a firmware runtime.
Current supported target
Waveshare ESP32-P4-WiFi6-Touch-LCD-7B
1024 × 600 · ESP-IDF 5.5.4 · LVGL 9.2.2
Current status
Standard LVGL Runtime V1 Complete. The newly completed Standard Runtime API set is automation-validated; no blanket physical ESP32-P4 proof is claimed for that set.
Authoritative documents
Start here, then go as deep as you need
Getting Started is the clearest first step. The product documents explain ForgeUI; the engineering maps preserve the detailed architecture and generated API contract.
Start HereRecommended first step
Getting Started with ForgeUI Studio
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.
Start HereOptional AI setup
OpenAI API Setup Instructions
Configure the optional OpenAI API key, local .env environment variable, security practices and troubleshooting for ForgeUI Studio AI features.
ProductCurrent product overview
ForgeUI Studio README
Product and capabilities overview covering AI-assisted design, Interactive Assets, native LVGL runtime APIs, System Runtime and standalone ESP-IDF export.
ProductProject background
About ForgeUI Studio
The creator story, engineering philosophy, platform direction, open-source credits and contact context behind ForgeUI Studio.
Engineering ReferenceStandard LVGL Runtime V1 Complete
ForgeUI Project Spine
Authoritative architecture, proven scope, current priorities, physical validation boundaries and save-point history.
Engineering ReferenceStandard LVGL Runtime V1 Complete
Developer Code Map
Detailed source, subsystem and ownership map for the Studio, generated runtime, connectivity, storage and export paths.
Engineering ReferenceStandard LVGL Runtime V1 Complete
Generated Export API Code Map
Generated public APIs, developer hooks, output-only controls, presentation-only decisions and file-ownership boundaries.
Engineering ReferenceCurrent integration guide
Developer Hardware Integration
Practical integration patterns for GPIO, tasks, queues, buses, sensors, networking, storage and developer-owned application modules.
Start HereWindows bootstrap utility
First-Time ForgeUI Setup
Download the Windows bootstrap utility that verifies the ForgeUI workspace and repairs Studio dependencies where possible.
Download .bat ↓Choose Your Path
Embedded Developer
Inspect generated C, connect event hooks and continue in a standalone ESP-IDF project.
Maker and Enthusiast
Work from proven hardware requirements through controls, flashing and practical diagnostics.
Browse Documentation
Getting Started
Install prerequisites, run preflight and reach the first hardware flash.
Studio Workflow
Use AI-assisted tools, Canvas, Inspector, Preview and standalone export.
Developer Export Architecture
Understand generated UI, developer hooks and native ESP-IDF ownership.
Hardware and Flashing
Use the validated target and either integrated or external build commands.
Popular Technical Topics
Interactive APIs, CMake registration, native assets and regeneration.
Troubleshooting
Diagnose setup, build, port, asset, callback and runtime failures.
Reference
Find API directions, file ownership and current target versions.
Studio workflow
Design visually. Export native C. Continue in ESP-IDF.
ForgeUI accelerates interface construction while preserving normal C, CMake, Git and ESP-IDF practices after export.