Xamarin Information Reviews & Insights

We use Xamarin for all of our mobile app development. Like working in C# and in Visual Studio.

Using Xamarin with Visual Studio allows us to create mobile apps without learning a new IDE or tool. It does make publishing a little more complex than I think it should be, but that's just my opinion.

Xamarin is well suited for mobile app development. It's nice to share almost all of our code between Apple and Android as well as between phones and tablets. We have our own PC tool, I don't use it for PC or Mac development but would like to go there with some shared code at some point.

Xamarin Forms allows us to get a line of business apps written quickly that can be run on Android or iOS with minimal fuss.

Great for line of business applications. Not so great for cross-platform games (use something like Unity instead).

Xamarin was used in a couple of projects by my organization. When it comes to faster development one should go for it. Yes, there are challenges but compared to developing two separate applications for the same purpose in different platforms this is the best choice. This application is better in performance compared to hybrid applications.

Business application its the best bet. For game-like applications, it may not be the best bet.

I've been using Xamarin for 100% of my mobile work since 2012. In my current organization, we have a Xamarin mobile app for nearly all of our projects.

I've introduced Xamarin to multiple organizations. Unless you have engineers who insist on not knowing C#, there are rarely any instances where it's not the best choice.

As an independent consultant, I use Xamarin with many small companies. Often, they bring me on in the early stages to evaluate and recommend improvements to their mobile strategy. Xamarin addresses the business problem of speed and resources. With Xamarin, you can develop mobile apps faster as well as utilizing existing resources. Some companies may have existing .NET developers in which case Xamarin fits well and the learning curve of mobile is less because of the familiarity with .NET.

Xamarin is well suited for several reasons. The first, it allows companies to share code across platforms. If the app has a lot of business logic and a fairly simple UI, Xamarin is great for this use case. Xamarin also works well if the developers who will work on the app are already fluent in .NET.
Xamarin is less appropriate if the company has a lot of developers. If there are plenty of resources to develop apps natively then the headache of dealing with Xamarin's issues are not worth the effort. If the UI is very complex and has difficult animations it's difficult to debug visual/performance issues in Xamarin.

We use Xamarin for cross-platform development. We like the idea of a code base sharing between platforms. Our apps are either built with Xamarin, or will be built with Xamarin. The problems it addresses is the amount of time and money it costs to have two full native applications.

Xamarin is great for any scenario, even if you don't utilize Xamarin Forms, which is the code sharing capability. But even if you just utilized the platform specific code, it's still all in C#. Makes it easy to not only maintain, but later hire developers who might not have any Xamarin experience to be able to come on board quickly and make an effect.