We chose to use Storybook for our react native projects as it allows us to develop components in isolation.
For mobile applications, the naive method of development would be to manually navigate to the page that contains whatever you are working on. While this is fine for simple apps, this does not scale well, especially if the component is nested deep inside the app. This problem is further amplified if the component depends on data from the API, as we have run into issues with dirty data, and even react native's auto-refresh behavior when modifying state-related files, such as redux or redux-saga.
Therefore, we use a combination of storybook and axios-mocks to streamline our development process.