alloy / reactnativeexperiments Goto Github PK

c1e83a3

What I do is create the collection view + layout (+ view controller) from the shadow view so that I can ask it for its -collectionViewContentSize when the shadow view is asked to determine the view’s size and then later assign it to the component view for hosting.

It works fine, but it feels weird, so just want to check if that’s the best way to do this or if there’s a way I overlooked to access the real component views from the shadow view at the time of layout.

The Artsy app has a tab bar with navigation stacks with many types of resource VCs (artworks, artists, etc) that though surfing can pretty much get pushed onto the stacks anywhere.

For our RN experimentation we want to start by implementing just 1 resource VC with RN and thus that VC and React view should integrate into the app as if it were any other UIKit based VC.

I have been doing some experimenting and really just wanted to know if this is a good way to go about it, or if I’m doing it completely wrong.

Prototype app setup

• There’s 1 bridge instance, which is shared throughout the application.
• I have this native module which provides a React API to manipulate the navigation stack. As per the RN documentation it’s built to work as a singleton and holds references to view controllers that host RCTRootView instances. (The ‘reference’ is simply the pointer to the VC.)
• I create an instance of the navigator module, which I then provide to the bridge.
• When a VC that hosts a RCTRootView is created, I register it with the navigator module and pass the VC’s pointer value to the React component.
• Finally, when a React component wants to e.g. push a view controller onto the current stack, it can use the exported navigator module API to do so.

This all appears to work fine.

Questions

• Should I not use a single bridge instance for the whole application and/or is there another benefit of having multiple bridge instances? The reasons I do are:
  • Instantiating a bridge can take a while, so less and early is better.
  • I’d like to update state throughout the navigation stack(s). (More about that below.)
• I’m interested in using Relay and was hoping that that meant that multiple RCTRootView instances that represent the same resource would get updated whenever the resource’s state changes. For instance, consider two VCs in different tabs that each represent the same ‘artwork’. The user ‘likes’ it in 1 navigation tree, switches to the tab with another navigation tree that holds the other VC.
  • However, if I understand it correctly, the various ‘apps’ in the AppRegistry are each root components rather than leafs in the same tree, which gives me the feeling that won’t work. Do you know happen to know if this is the case? (I have no Relay experience yet.)
  • Or if I need to hook this up manually, is there a way to get all live root component instances from the app registry?