FAQ
Is SymbioteNative a WebView?
Section titled “Is SymbioteNative a WebView?”No. SymbioteNative drives React Native Fabric and paints real native iOS and Android views.
Does SymbioteNative fork React Native?
Section titled “Does SymbioteNative fork React Native?”No. The native stack stays stock React Native: Fabric, JSI, Yoga, Hermes, and the platform hosts remain ordinary dependencies. SymbioteNative replaces the JavaScript renderer path that talks to Fabric.
Does SymbioteNative support React Native’s New Architecture?
Section titled “Does SymbioteNative support React Native’s New Architecture?”It requires it — there is no other option. SymbioteNative’s renderer talks directly
to global.nativeFabricUIManager, the JSI-bound mutation API the New
Architecture’s Fabric renderer exposes (createNode, cloneNodeWithNewProps,
completeRoot, …). That API doesn’t exist under the legacy bridge, so there
is no old-architecture fallback to support — SymbioteNative is built on Fabric from
the ground up, not migrated onto it. Any React Native version and toolchain
that runs Fabric (0.76+ with the New Architecture on by default, or an earlier
version with it explicitly enabled) works; anything still on the legacy
renderer does not.
Why does the app still depend on react-native?
Section titled “Why does the app still depend on react-native?”react-native is the native runtime singleton and Metro/native version anchor.
Apps should pin it explicitly at the top level. SymbioteNative hides most imports from
app code, not the runtime dependency from the app manifest.
Can Vue render any React Native package?
Section titled “Can Vue render any React Native package?”No. A third-party React Native package that exports a JavaScript React component still calls React hooks or uses the React dispatcher internally. Non-React adapters need a native-view wrapper over the underlying Fabric view instead.
Why are Vue events not identical to React props?
Section titled “Why are Vue events not identical to React props?”Because Vue users should get Vue APIs. React uses callback props such as
onValueChange; Vue exposes typed emits such as @value-change. The native
payload and shared logic can be the same while the framework contract differs.
Is Angular a first-class adapter?
Section titled “Is Angular a first-class adapter?”Yes — it’s on the landing page’s live framework switcher alongside React and
Vue, with its own guide, demo GIF, and
API reference, and wrapper packages like Slider ship an
Angular build too. One thing is still catching up: Angular has its own
real-device Detox e2e suite, but doesn’t yet share the identical
canary-journeys spec file that React and Vue run byte-for-byte. See the
status page for the exact line.
What about Svelte and Solid?
Section titled “What about Svelte and Solid?”No code exists yet. The architecture is built for thin adapters over the same shared engine, so they fit the same long-term model Angular proved out, but they stay in architecture diagrams and roadmap text only until that work starts.