Docs menu

Documentation Centre

ForgeUI Studio Documentation

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.

Help and community resources

ForgeUI Hosted Studio

Public / live

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

ForgeUI Fi Runtime

Control any used Fi icon through generated visibility, opacity and colour APIs, with optional click hooks routed through 95_UserEvents.

SOFTWARE COMPLETECLICK PATH PROVENPRESENTATION PROOF PENDING
Read the Fi Runtime guide →

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.

Engineering ReferencePHYSICALLY PROVEN / CLOSED

Hardware Example 05 — GPS / GNSS Source Record

Authoritative u-blox NEO-8 UART1 wiring, live NMEA, fix data and checksum-valid UBX request/response physical proof.

Engineering ReferencePHYSICALLY PROVEN / CLOSED

Hardware Example 04 — Online Services — Live Weather Source Record

Authoritative physical proof record for the stock-C6 Wi-Fi, verified Open-Meteo HTTPS, forecast, time, Fi icon and dynamic local-background runtime.

Engineering ReferencePHYSICALLY PROVEN / CLOSED

ESP32-P4 Wi-Fi / ESP-Hosted Architecture

Authoritative physically proven ESP32-P4 to stock ESP32-C6 SDIO, Wi-Fi, TLS and HTTPS architecture used by connected ForgeUI exports.

Engineering ReferencePHYSICALLY PROVEN / CLOSED

Hardware Example 03 Source Record

PN532 software-SPI wiring, identity, ISO14443A polling, UID reading, removal and logical de-duplication proof.

Engineering ReferencePHYSICALLY PROVEN / CLOSED

Hardware Example 02 Source Record

MB85RC256V shared-I²C identity, write/read/verify and complete power-cycle persistence proof.

Engineering ReferencePHYSICALLY PROVEN ON ESP32-P4

Hardware Example 01 Source Record

Board-specific wiring, generated contracts, developer ownership, startup behavior, troubleshooting and accepted physical proof for two buttons and two LEDs.

Engineering ReferenceGPIO2 / GPIO3 / GPIO4 / GPIO5 proven

ESP32-P4 Board Pinout Master

Audited pin ownership, electrical restrictions, allocation register and physical evidence for the Waveshare ESP32-P4-WIFI6-Touch-LCD-7B.

Engineering Reference44/44 practical LVGL components proven

ForgeUI Feature Status

Authoritative implementation and physical-evidence ledger for Standard widgets, Native Components, Runtime features and Hardware Examples.

Engineering ReferenceCurrent generated SDK direction

ForgeUI Runtime SDK Direction

Generated application-facing APIs, UserEvents, naming, ownership, feature gating and current proof boundaries.

Engineering ReferenceCurrent engineering journal

Feature Improvements & Known Issues

Authoritative engineering journal for improvements, resolved and active issues, validation history and proof priorities.

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 ReferenceCurrent v3.5.7 documentation baseline

ForgeUI Project Spine

Authoritative architecture, proven scope, current priorities, physical validation boundaries and save-point history.

Engineering ReferenceCurrent v3.5.7 documentation baseline

Developer Code Map

Detailed source, subsystem and ownership map for the Studio, generated runtime, connectivity, storage and export paths.

Engineering ReferenceCurrent v3.5.7 documentation baseline

Generated Export API Code Map

Generated public APIs, developer hooks, output-only controls, presentation-only decisions and file-ownership boundaries.

Engineering ReferenceSoftware complete; partially physically proven

ForgeUI Fi Runtime Guide

Canonical Fi Icon pipeline, generated 90/95/96 ownership, runtime presentation, optional click behavior and future semantic direction.

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

Browse Documentation

LVGL Simulator

Run generated C with real LVGL 9.2.2 in WebAssembly. Workflow, native interaction and Sim V1 limits.

Supported Hardware and Board Selection

Supported ESP32-P4 and ESP32-S3 display and headless profiles, with experimental status and physical-proof boundaries.

Device Console

Integrated ESP-IDF BUILD, authoritative live MONITOR and read-only I/O insight in the Studio workspace.

Hardware Examples

Editable, board-specific projects with wiring, generated contracts, developer-owned hardware code and physical proof.

Hardware Example 01 — 2 Buttons + 2 LEDs

PHYSICALLY PROVEN ON ESP32-P4 across both GPIO input → UI and UI → GPIO output paths.

Hardware Example 02 — I²C FRAM

PHYSICALLY PROVEN identity, write/read/verify and complete power-cycle persistence.

Hardware Example 03 — SPI NFC/RFID

PHYSICALLY PROVEN PN532 polling, UID reading, removal and de-duplication.

Board Hardware / Pinout Evidence

Review the audited Waveshare ESP32-P4 pin ownership and proven GPIO2 / GPIO3 / GPIO4 / GPIO5 allocation.

Developer-Owned Hardware Integration

Connect GPIO and device code through the Runtime SDK and genuine UserEvents without touching private LVGL objects.

Feature Status and Roadmap

44/44 practical LVGL 9.2 components physically proven, plus the individual status of all 14 current Native Components.

Native Component Library

Browse all 14 current semantic components with generated contracts, interaction models and ESP32-P4 status.

Native Components Overview

One semantic Canvas component, private LVGL composition, stable identity and generated Runtime APIs.

Native Component Architecture

Understand Registry ownership, preview/export parity and the complete proof gate.

Dashboard Card

Use proven semantic value, units, status and progress APIs plus an optional click hook.

Sensor Tile

Project typed measurements, thresholds, trend, timestamp and colour through six semantic APIs.

Relay Panel

Bind 1–8 zero-based logical channels and master control to developer-owned hardware.

UserEvents and Developer Ownership

Preserve customised hooks safely across regeneration and distinguish genuine user actions from setters.

Feature Improvements & Known Issues

0 active issues · Current proof target: Waveshare ESP32-S3 Touch LCD 7B physical parity closed across 59 widgets/components.

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.

ForgeUI Runtime SDK

Use generated setters, commands and genuine-user callbacks without editing private LVGL code.

Project Hardware Profiles

Select and persist the authoritative board target, dimensions and generated project configuration.

Practical LVGL 44 / 44

Review the physically proven LVGL 9.2 foundation; Lottie remains intentionally excluded.

ForgeUI Fi Runtime

Control any used Fi icon through generated visibility, opacity and colour APIs, with optional click hooks routed through 95_UserEvents.

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

Flash from the browser. Or export native C.

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.