Styling
Style props on a React Native component work the same way here as on iOS and Android: Fabric commits a style record for each node, and this engine reads it at mount or update time and builds the matching Impeller draw calls. The value React Native's style layer resolves is the value that gets painted.
Two things differ from a native host because the renderer is Impeller rather than a platform UI toolkit.
Anti-aliasing depends on the backend
Metal and Vulkan surfaces get edge antialiasing from the surface's MSAA. The GL backend (Linux, Windows, and macOS until native Metal lands) has no surface-level AA, so stroked SVG icons come out jagged without help. The engine works around this with a supersample-then-downsample pass: it renders the icon at 4x into an offscreen texture, then composites it down with a linear filter. This pass is on by default on macOS and off elsewhere while the technique is validated further. For more information about the backend list, see How it works.
Not every style prop has landed yet
Style and NativeWind coverage is tracked by a pixel-diff gate
(tools/ci-style-coverage.sh), not asserted from memory. The full list of
what passes today, and the known gaps, is in
Supported components and style props.
Two gaps apply here:
nw:tabularNums(NativeWind's utility forfont-variant: tabular-nums) isn't implemented. See Fonts and text.- Platform colors, emoji, CJK, and Arabic text render correctly through a font-fallback path, not the primary font. See Fonts and text.
A platform is listed as passing a style tile only after its
tools/ci-style-coverage.sh run proves it. Nothing here is aspirational.