Xamarin

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 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.

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 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 Forms allows us to get a line of business apps written quickly that can be run on Android or iOS with minimal fuss.

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.

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.

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.

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.

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.

We used Xamarin to develop cross-platform apps for taxi aggregation app in android, windows and IOS. It is used by my project team including android, IOS and Windows people to create applications in single code base, and it helped us to write quality code that runs consistently on different platorms