Production ready?

[MaGomesP]

Hey @eds2002 , first of all, really cool library, today we're short on libraries that do cool shared transitions between navigation, so I just want to know if this is production-ready. Today I'm currently using react-navigation-shared-element, which is really outdated and doesn't even support the new arch, and could have some potential bugs, so I would like to know if this is a good option to migrate? Reading the docs, it seems that it supports the react native navigation library by having a wrapper based on the stack navigator. Can I encounter issues with stacks that don't need to use the transitions? Should I use the react native navigation stack for the use cases of not having the transitions, or should I not mix both stack navigators together?

[eds2002]

hey @MaGomesP thank you and great questions!

1. Should you migrate?

If specifically for SETS, i completely recommend reanimated shared element transitions, the bounds api was originally a meantime until v4.2 was released. You should 100% be satisfied with their implementation, and their implementation has no hacky ways as we do with native stack.

Should you need different screen transitions/customizable experience then try out the package.

2. There should be no issue with the mixing of stacks, whether your import from our library/react navigation. Screen logic is scoped based on its navigator, you can mix as youd like.

If you do end up using the package, hope you like it! Should issues come up lmk, actively maintaining