I have more than a year of experience building applications for Android, iOS and Windows with Xamarin. Overall, I much prefer my experience with Xamarin than th

I have more than a year of experience building applications for Android, iOS and Windows with Xamarin. Overall, I much prefer my experience with Xamarin than the alternatives. Keep in mind that I did have prior experience with C#, .NET, and Visual Studio. As far as "recommendations on developing for multiple mobile platforms", I'd be happy to answer slightly more specific questions. > As far as I understand it, if you are big and have the resources, your best bet is still to develop separate native apps for each platform. If you have different teams for each platform, it makes sense to go native and duplicate the effort. As soon as you want to share code or resources (including employees) between more than one platform, Xamarin starts making sense. If you have a small mobile development team (1-2 people), you'll probably need to either pick a single platform, or go with Xamarin. If you plan to have a Windows app, Xamarin makes sense. If the business is already using Microsoft technologies (Windows, .NET, C#, Visual Studio, TFS, or even Typescript), then Xamarin makes a lot of sense. However, Xamarin is not a silver bullet. It does comes with some trade-offs (in addition to those mentionned in the article). - You still need a Mac (either as your main machine, or on the network). - Compile time is a bit slower. - You don't get access to the latest Android SDK on day one (you do with iOS, though). - You can't use any existing iOS/Android libraries out of the box. Someone (which could be you) need to manually "bind" the Java/Objective-C library interface to C# first. - Application startup time might be a bit longer on iOS.