Between Xamarin and ReactNative which one would be a better choice for creating Mobile Applications

IMHO it's really a matter of style and preference. Xamarin is more 'old school' in that it is a heavy/robust structured framework and more of a defined/prejudiced means of accomplishing any given feature. This can be good or bad depending on your preference. Xamarin has a large pre-developed set of features that can be leveraged. Xamarin is also heavily OOP and not functional. While Functional is possible in Xamarin, it steers you towards OOP.

React/Native, Flutter, etc are more lightweight and flexible frameworks that are less defined/prejudiced. This gives you more freedom to be creative and also to shoot yourself in the foot (or feet). These frameworks are moving away from OOP and more towards functional programming. While OOP is possible in these frameworks, they steer you towards functional.

Personally, I'm using ReasonML with ReactNative for mobile development:

Here are some useful links that helped get me started:

blog.callstack.io/getting-started-...

blog.behrends.io/how-to-setup-reas...

github.com/reasonml-community/bs-r...

imaginarycloud.com/blog/reasonml-r...

reasonmlhub.com/exploring-reasonml...

reasonmlhub.com/exploring-reasonml...

I've previously used the Appcelerator platform to build iOS and Android apps, but then I switched to React Native and I can only say good things about it. The community really seems to grow in the past few years and you can easily find any sort of packages or solutions to any issues you may run into.

Here are some good resources I used to get started with React Native:

• reactjs.org/docs/getting-started.html (you'll have to understand how React works before diving into React Native, but you mentioned that you're already familiar with React so you can skip this)
• redux.js.org/basics (optional if you're just getting started with React Native, but when you'll be building more complex apps, you may need to reach out for Redux)
• facebook.github.io/react-native/
• reactnativeexpress.com/

Packages:

• reactnavigation.org (use this package when you want to navigate between screens or create some sort of tabbed application. It's very well documented and I had no issues using it.)
• github.com/react-native-community (an awesome organization which created a lot of great packages for the community)
• github.com/zo0r/react-native-push-...
• github.com/invertase/react-native-...

App Icons + Splash Screens setup (that's always a tricky part so the links below def helped me):

• medium.com/@scottianstewart/react-...
• medium.com/handlebar-labs/how-to-a...

Happy coding! 👨‍💻👍

It depends on the project and your & your team's experience.

My personal take (also for other technical decisions):

The more unknowns in a project, the more I'd tend to pick the more mature/boring one.

Your team has significantly more experience with one method against the other? Pick that one.

The app is not doing anything fancy and you're the sole dev? Throw a coin 🙃

The app has to do something which you never implemented before? Try to do a proof of concept in both, and use that experience to decide how to go forward.

Btw now you made me curious to try out Xamarin. I used a bit C# with Unity and really liked it. I may try to do a mobile app for devlids with it.

Pick the tech stack you'd feel comfortable maintaining through the life of the product