Proof

@expensify/react-native-hybrid-app

native-seam only: the published wrapper runs unchanged over a ReactNativeHybridApp TurboModule that reports a standalone (non-hybrid) build, which is what a browser preview is

50%

API coverage

No visual proof cases have been published for this package yet. The registry summary below describes what the compat layer implements.

Working

the full Spec surface loads and every method matches its upstream return type — isHybridApp() is false so the bundle stays on its standalone branch instead of the legacy-shell path, getHybridAppSettings and getInitialURL reject NOT_IMPLEMENTED "This method is not available in standalone New Expensify app" as the standalone iOS build does, and the sign-in, sign-out, account-switch and onboarding calls are accepted

Missing

there is no second native shell to hand off to, so the legacy-app transition, its session and auth-token exchange, and closeReactNativeApp have no effect