A description, not a native view
Widgets are immutable C# values. Rebuilding one does not automatically recreate its UI Toolkit element.
LumaFlow documentation
Build your first screen, then understand the system.
A practical route from an empty Unity scene to a maintainable reactive interface. Every section tells you what to do, why it matters and where to continue.
Read in this order if you are new.
You do not need to study the complete API before building an application. Start with one working screen, then learn the contracts that prevent layout and lifecycle bugs.
Start here
Build a reactive screen
Install LumaFlow, mount the application, create a counter and dispose the mount correctly.
Understand
Widget, element and state
Learn what is immutable, what is retained and what actually rebuilds when state changes.
Scale
Lists and identity
Choose keys correctly and use virtualization for large, dynamic collections.
Structure
Navigation and overlays
Keep routes, dialogs and popovers outside Build and control their lifetime explicitly.
Find the contract behind the problem.
Each guide focuses on one production concern and the failure modes you are likely to encounter in Unity.
UI
Controls and forms
Inputs, tabs, validation, focus and product-level styling.
A11yAccessibility and locale
Semantics, keyboard navigation, reduced motion and application strings.
DXDevelopment workflow
Inspector, diagnostics, testing and Play Mode recompilation.
RulesLayout contract
Bounded axes, flex children, scrolling and responsive composition.
APIComplete API reference
Search public types and signatures when you know what you need.
Four ideas explain most of LumaFlow.
The retained mounted instance
It owns lifecycle and reconciliation. Compatible updates reuse the same VisualElement.
A value with explicit dependants
Only mounted branches that read a state value rebuild when it changes.
Identity across movement
Keys preserve logical identity when children are reordered, inserted or removed.