Xamarin 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 is used in my organization to create mobile and web applications that can share the same common logic. This is great for building cross-platform applications for any organization that needs it.

Xamarin is mainly used in the development team as it does require technical knowledge of building software. You can use it to solve many different business problems through applications built on the Xamarin platform.

If you are required to develop applications that are cross-platformed, Xamarin is a great tool to use. It will help save time and effort from your development team to be able to build applications seamlessly for android, IOS, Windows, and web on a single platform instead of requiring multiple tools to get the job done.

Xamarin comes in handy when you want to write cross-platform (for Android and iOS) applications without the need to code twice. It shortens development time and that's an advantage. Xamarin also helps developers building on .NET transition to mobile development without the need to learn additional programming languages- saves money and training time. Most of the time Xamarin is all good a part from a few times when you want to keep up with new features and Xamarin takes time to implement them.

Currently Xamarin is being used by our main corporate office for a number of applications. We are using it for quality assurance and sales. This allows us to have the same look and feel and functionality across multiple environments. Our sales and QA staff are located all over and have different mobile platforms.

Xamarin is perfect if you have senior .Net developers and do not want to have write code twice. Once for Android and once for IOS. This also allows you to have one code base platform that make changes much simpler and keeping both versions in sync. It would be nice if you could have some common settings files across the 2 that would inject into the pList file for example.

Xamarin is used to develop small mobile business apps for special customers. For example, we developed an app, where the user can download the data of customers including last service results and fill in a new service form; let the customer sign the form and send the form back to the office where it is approved and archived.

Xamarin is perfect for business apps. Developing games is probably better in native code. (But I have never developed games with xamarin.)

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.

The product development team was building a cross-platform endpoint security product in C# .NET and all used MacBook Pros, so Xamarin was the IDE of choice. It addressed the problem of being able to develop the Linux and Mac versions of the product without having to have a Linux VM for Linux development and also made it possible to develop the cross-platform portions of the software natively on their Macs, rather than using a Windows VM. Only Windows-specific development and testing needed to be done within a VM. As a product development startup, all but one employee used Xamarin.

Xamarin is definitely the best product to use for C# .NET programming on MacOS; for other uses it may not be the best IDE: different languages, different platforms, etc.

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.