react-native VS react-native-joystick

Lastly, we just released a new version of React Native Storybook: RN Storybook 7. It brings major performance and compatibility improvements, including automatic story loading, improved error handling, stronger types, and much more.

There’s still a massive amount of potential with RN Storybook project and we’d love new contributors to help us get there. Find the project here and share your feedback, interest, or support.

I’m being tasked with migrating a “kitchen sink” of components (currently rendered with a feature flag & Stack navigation) to a more separate feature. They’ve decided on Storybook. I didn’t ask why as my contractor role wasn’t available to help w decision making at the time.

Also heres the pr where I'm adding support for require.context to React Native Storybook https://github.com/storybookjs/react-native/pull/501

Do you use Storybook? I ran into similar issues where promises didn't resolve due to this issue: https://github.com/storybookjs/react-native/issues/20

If those drawbacks aren't dealbreakers, then I think you will be happy with the results. However If you are unable to use this package because you need a native mobile experience then consider using @storybook/react-native. You could even use both if it makes sense for your use case.

I recently set up Storybook for a React Native/TypeScript project. It wasn't so different from using Storybook for web dev, but there were a few catches. I found their official tutorial to be outdated sometimes, and their Github README was up-to-date but didn't have all the information I wanted.

take a look at: https://github.com/storybookjs/react-native/issues/133

I've tried a few ways of implementing this. Firstly, based on the library here (https://github.com/ionkorol/react-native-joystick) which utilises `react-native-gesture-handler`. It allows for multiple, simultaneous touches, however, runs incredibly slow.