Transitioning to react-native-screens

[lodev09]

Hey everyone 👋

Thanks so much for using and supporting react-native-true-sheet! I originally created this library because there weren’t any native bottom sheet solutions available for React Native at the time.

Now, things have changed. The team behind react-native-screens has started working on their own native bottom sheet, which integrates better with react-navigation and supports the new React Native architecture. Since this aligns better with where the ecosystem is going, I’ve decided to shift my focus there.

I’ve opened a draft PR in there to bring some of the features from true-sheet over. It’s still a WIP, but I’m excited about where it’s headed!

software-mansion/react-native-screens#2902

Going forward, I won’t be adding new features to react-native-true-sheet, and I recommend checking out the upcoming bottom sheet in react-native-screens as it develops.

Thanks again for being part of this project ❤️

[akuul]

Thank you for all the work you did ! ❤️

[codydorsettlynn]

Is there any chance you could update your docs to include an example of how the react-native-screens pattern works?

I don't love that the react-navigation modals (implementing react-native-screens) require being in the root stack and the component-in-screen pattern of true sheet was very attractive to me as well as the way nesting sheets were supported. It allowed for very useful compound components that use multiple sheets for filters, drill downs, etc.

The documentation for react-native-screens leaves a lot to be desired. Honestly its a shame this project is being abandoned, its considerably more approachable than the alternatives. Have you considered implementing your API using react-native-screens as a base?
That notwithstanding, I appreciate all your hard work on the project.

[lodev09]

@codydorsettlynn I totally agree.. RN screens kinda hard to implement if you just want simple sheets to show.

Have you considered implementing your API using react-native-screens as a base?

I did consider it but haven't got the time to explore yet. Specially on IOS, not sure how much work it needs for it to work with rn-screens. Also for New arch, I would need to convert the whole project into Objective-C 🤦‍♂️

I think those are the big blockers right now and transitioning to rn-screens in the meantime is the easiest.

I appreciate your feedback, hopefully it gets easier for us in the future.

[lovegaoshi]

thank you for your work as always!

would you consider adding this announcement in the readme.md section? have to admit I'm a little heartbroken after migrating my menu components into bottom sheets, then saw this while searching for keyboard avoiding techniques in the discussion section.