Mobile Apps

General discussion


Roadblocks, pain points, and problems of React Native vs native

By orjanbv ·
I'm researching the use of React Native as a cross-platform mobile app solution, as opposed to developing two apps separately using native languages. The research is for a company which is considering rewriting their existing app in React Native, with hopes of eliminating some of the need for developers with Swift and Java experience, and to achieve less lead-time for new features in the future. To do so I'm developing a React Native app from a set of given functional requirements and user stories to explore and discover possible roadblocks and problems which should be considered when making a decision. However, I've realized that the functional requirements might be too narrow, and that I might miss some problems by not touching the area.

I'm interested in hearing of recurring roadblocks, pain points and problems encountered/experienced when using React Native instead of native, especially from developers who have experience in using both.

This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

Roadblocks, pain points, and problems of React Native vs native

by sarahmorganmedia In reply to Roadblocks, pain points, ...

I understand you might be in dilemma about what to choose between reactive native and native. As per cost, react native is less expensive than native.

When we talk about interactivity, A Native mobile application easily interacts with other native apps by accessing their data and offers an exceptional experience which is missing in react native.

The React Native apps has a limitation in using APIs into their development processes while the same is not the case with native.
I hope this helps!

Related Discussions

Related Forums