I am working on two react-native repos at the moment, and they both share an entire navigation section, say blog. Things I need to consider:

1. Both the apps will have almost the exact page/screen, so it would be beneficial to pull it out and share it across apps. Most of the changes to the page components would be required on both the apps, so this would reduce duplication and maintain consistency.
2. If I consider the entire screen as a complex component and add it to the component library (both UI and logic), this would solve quite a few headaches.
3. However, there is a chance of tiny changes on the screen that would be specific to a single app, and not show them on the other app.
4. This might mean I would end up exposing props on this gigantic component and then letting it seep onto the child components. This could get messy.
5. This also means I would then be dealing with a gigantic potentially inflexible component.

Considering all the pros and cons, I am not quite sure if this would be the right way to proceed. Is there a better way of tackling this problem? I could just have the same screen duplicated on both the apps, but this causes the headache of updating both the apps resulting in multiple app store releases.

Any suggestions would be really helpful. Thank you.