Going Mobile With React Native

Re:Going Mobile With React Native by whizzkid on Friday July 07, 2017 @08:38AM (#14717860)

I see, thanks for getting into details.

I guess, if you are one-man team RN makes good sense since you don't have time to write native for 2 platforms from the beginning. If your app takes off, then switch to native for scaling. Is it possible to partly switch from RN to native? something like convert components one by one to native components, while still running RN for some parts?

[ Parent | on HN ]

Re:Going Mobile With React Native by FRex on Friday July 07, 2017 @08:47AM (#14717903)

Why not use Xamarin's stuff to do it all in C# instead then?

[ Parent | on HN ]

Re:Going Mobile With React Native by doublerebel on Friday July 07, 2017 @10:43AM (#14718701)

Because Xamarin and all the other cross-platform libraries are as bad or much worse.

Most apps don't need native performance, and most that do only need it in a single component. Really good software architects and devs know where a framework like RN is valuable.

[ Parent | on HN ]

Re:Going Mobile With React Native by LeoNatan25 on Friday July 07, 2017 @09:31AM (#14718157)

Xamarin is a good choice indeed. Their constant work to create native mapping is very impressive.

[ Parent | on HN ]

Re:Going Mobile With React Native by calvin_c on Friday July 07, 2017 @09:50AM (#14718274)

Yes, that is certainly possible. It doesn’t have to be 100% either way, you could do any combination of React Native and proper Native you want.

[ Parent | on HN ]