Description

I have a very specific scenario for my Brownfield app but encountered other developers that share the same implementation limitation -- not specific for this library, but more common to use React Native in a brownfield app -- and I would like to propose something for this library -- that I don't know if is possible yet -- that is to run the

Why it is needed ?

I was developing a chat message feature to my native Android/iOS app and the decision was to implement using React Native, sharing the implementation details between different platforms.

The App is fully Native and a section of it would be to implement this feature, as we have some native bottom navigation, the best solution would be to implement them inside an Android Fragment or iOS Container. Because of that we had some limitations as to implement Navigation, Bottom Sheets and other features so we looked at react native libraries that are rendered in the Native Realm and not in the React Root View, for instance, react-native-true-sheet is an example where the bottom sheet gets rendered in the Native, bypassing the Fragment/Container giving the impression of a native component. This doesn't happen with react-native-bottom-sheet as it only gets rendered inside the fragment that is the RootView.

The same happened when we got to implement the Video Playback feature from a video message, react-native-video renders on the RootView creating a bad experience since only the Fragment would be displaying the video and not the entire phone screen.

So the Idea would be to render the Video component in the Native realm bypassing cases where React Native is running inside a Fragment/Container. This would imply the possibility to pass a header-like component to close the screen, or use the phone navigation gesture/button, but adding the possibility to customize it would be nice.

Possible implementation

No response

Code sample

No response