Hello everyone, we're just getting started with Xamarin and I am evaluating our options as far as setup and architecture for a couple upcoming projects. The project that is coming up is an ASP.NET MVC SPA app (AngularJS + WebAPI) that we'll want to build native mobile apps (iOS/Android) for in phase 2. So, we're going to have a web-app that has an extensive admin/management area that is strictly web-based, then a front-end SPA that web-users can interact with. We're hoping to use the webapi dependant service layer to communicate with the native mobile apps that we're hoping to build in Xamarin. I've investigated PCLs and understand the concepts/benefits, looks great.
Now, the question is, since we're going to want to support iOS and Android, my understanding is we can achieve greater code reuse if we use a framework like mvvmcross. I've watched the video series by the creator, and it seems like its fine frameork. A concern is that things appear to have changed since the videos were made, and I am not seeing updated examples/tutorials (although the creator seems incredibly dedicated to the project with answers/support!!). So back to the question.. is mvvmcross mature enough to use in a commercial product?
Question #2, since longevity is a major concern, would it be better for us to just stick with plain jane Xamarin iOS/Android projects and not rely on something like mvvmcross? Are we doubling the workload on our devs if we do this?
As you can probably tell, I want the answer to be that we should use mvvmcross, because I am a fan of the MVVM pattern. My biggest concern is the lack of updated tutorials which leads me to think that things are moving fast and it may be better to not use it until things settle down a bit?
I'd love to hear comments on this.
Thank-you very much in advance!