I've used Xamarin before it got opensourced (paid license) and stayed away from the Xamarin.Forms because of my other crossplatform framework experiences. I choose to use native projects with sharing the business logic as you (but I've used ReactiveUI). I highly recommend Xamarin with native projects. Best points for me:
with native projects you don't have to learn a new framework. Just using UIViewControllers on iOS and Activities on Android. This has a great benefit: Finding a solution to your problem is much easier, because you can get benefit from the solutions for swift / obj-c projects or java projects (since you writing the same framework)
using mvvm structure also can help to avoid very big UIViewControllers / AActivities since your business logic is in the shared code base.
As an ex Xamarin Forms developer, I strongly agree.
Are you still developing mobile apps?
If so, what stack did you pick this time?
Thanks for sharing.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I've used Xamarin before it got opensourced (paid license) and stayed away from the Xamarin.Forms because of my other crossplatform framework experiences. I choose to use native projects with sharing the business logic as you (but I've used ReactiveUI). I highly recommend Xamarin with native projects. Best points for me:
As an ex Xamarin Forms developer, I strongly agree.
Are you still developing mobile apps?
If so, what stack did you pick this time?
Thanks for sharing.