Components and Support Boundaries
Distinguish React Native descriptor registration from the behavior that the Hera adapter actually translates.
Fabric can construct the Root, View, Image, ScrollView, Paragraph, Text, and RawText shadow nodes registered by the default registry. Their visible behavior still depends on what the Hera adapter translates and what supporting services provide. Use the registry as a list of available descriptors, then inspect the implementation before relying on a particular property or resource pipeline.
Views and Layout
The adapter extracts position and size from Fabric layout metrics and reads common view properties such as opacity, display visibility, and z-index. It translates background and border appearance into Hera view content.
Yoga resolves React Native layout before the host submits a scene, leaving the server with explicit geometry rather than flexbox rules. To extend a visual property, follow its extraction and retained update behavior through the adapter; accepting the JavaScript prop only establishes the input to that work.
Text and Paragraphs
The text path begins with attributed content in paragraph state. The platform text layout manager uses Hera's shaping services to supply React Native measurement, and the adapter produces retained glyph runs for final rendering. Since those runs name glyphs from registered faces, the client and daemon need matching font registrations.
Text and RawText descriptors participate in Fabric's text structure; they do not imply a separate display node for every JavaScript text fragment.
Scrolling
ScrollView connects its retained content placement to native interaction through HeraScrollView, scroll state, the input controller, and mutation emission. Together, these keep content offset and clipping aligned with both server scene updates and React Native event delivery.
Read input and scrolling before changing wheel handling or content offset behavior.
Images
Image demonstrates why descriptor availability alone is not a support guarantee. The registry can construct its shadow node and the sink can represent image content, but the current Fabric adapter does not supply a complete source-loading and buffer-import pipeline. Arbitrary URI images therefore need additional implementation before they can be decoded and displayed.
Completing that path requires source resolution and decoding, followed by imported-buffer ownership that handles updates and eventual release. Those services must connect to the registered component's lifecycle as well as its initial creation.
Additional Native Components
A component absent from the registry needs an explicit descriptor and host implementation. TextInput, platform pickers, native navigation containers, accessibility integration, and third-party native views must be assessed individually; upstream availability is not a Hera support guarantee.
Use the smallest representative application to validate an integration, then add meaningful native and end-to-end checks around the new behavior.
Source Reference
The following files in the Hera checkout define the behavior described on this page.
react-native/rn_host/src/runtime/registry/component_registry_factory.cppreact-native/rn_host/src/fabric/adapter/adapter.cppreact-native/rn_host/src/platform/text/hera_text_layout_manager.cppreact-native/rn_host/src/platform/scroll/hera_scroll_view.cpp