Native integration
Use named factory props for native Inspector settings. reference captures a built component; configure handles one-time native work. For additional reactive native integration, use P.Bind, P.Set, P.Apply and P.On inside the owning scope. P.Declare<T> supports user-authored native components without reflection dispatch or a registration table. Imperative integration reference.
Choose the integration point
| Need | Integration |
|---|---|
| Set a supported native property | Supply its named factory prop, using a literal or reactive value. |
| Capture the built component | Supply reference; it receives the actual native component. |
| Perform one-time setup after props and children | Supply configure. |
| Bind additional native state reactively | Use P.Bind or P.Set inside the owning scope. |
| Apply imperative property declarations | Use P.Apply on the native target. |
| Declare a user-authored Unity component | Use P.Declare<T> with the native component type. |
Capturing a reference does not make later reads reactive. Use a binding when the native property must follow changing state; use configure for work that should run once. The deferred creation API explains when references and configuration run during mounting.
Keep native objects and declarations separate
View describes what Pine will mount. A UnityEngine.Component reference is the object created from that declaration. Deferred .With(...) composition accepts declarations and modifiers; advanced imperative Create, Apply and Bind operate on native objects. Choose the path that matches what you already own, then keep its observers and event handlers inside the same live scope.
The native integration reference contains signatures and constraints. Start with native controls and reactive props when a named prop already covers the setting you need.