Xamarin.Forms reduced the effort and time to build and market our solution, market our features, and get our solution into production. We have Android and iOS. When using Xamarin.Android and Xamarin.iOS, we have to write the same solution two times, one for each platform. But with Xamarin, if we write the solution once, it will run on both platforms. We can reuse as much as 90% to 95% of the code, which, in our case, was written in Xamarin.Forms to be used across both Android and iOS. The other 5% we wrote needed to be tailored for the specific platform. Suppose we want to create some niche or some specific features that are not available in Xamarin.Forms would be the 5% we need to write for each platform. Xamarin.Forms help reduce the effort required to build across platforms and solutions and time to market.

With Xamarin Platform we are able to create hybrid applications that run cross-platform on Android and iOS, removing the headache of building and deploying separate applications for each platform.

It is great that Microsoft supports many libraries for digital forms and Xamarin. The Xamarin community is big. They respond, and so many developers share their knowledge on the framework, core custom control and details on implementation.

In the App Center we can not only deploy our apps, but we can also carry out user analysis; which page particular users have visited, whether the app has crashed, and what the root cause of that crash might have been, so that we can fix the issue.  This functionality allows us to provide a better user experience.

With the help of Xamarin.Forms, we can effectively realize a cross-platform app with a very small team of 1-2 developers, targeting both iOS and Android platforms.

In a purely native development environment, you would typically find a developer specializing in one of the major platforms. If the objective is to create a mobile experience for more than one platform at the same time, you typically need distinct resources for each platform. Often times they create the same code/logic in different programming languages for each platform. In this scenario, the Xamarin platform can reduce overhead significantly through code-share and reuse. The typical team size for a Xamarin project is significantly reduced compared to purely native projects.

When we create applications, we usually need applications for both platforms. For example, we have a vendor that provides services on both Android and iOS applications. So usually, if we want to create an application for Android and iOS, we have to create two applications, one in Android, like Java or Kotlin, and one in iOS, like Swift or Objective C. But, using the Xamarin Platform, we don't have to create two applications. Instead, we create one Xamarin form application. We write code in that solution and build it according to our specifications.

It has significantly reduced the skill barrier for development and testers. Our company is mostly a Microsoft stack house, so most developers either use, or are familiar with, C# and .NET. Removing the need to become proficient in two other languages, makes adoption easier. Though it should be noted that developers still have to become familiar/proficient with the iOS and Android SDKs and the lifecycles of the native apps.

The ability to reuse significant amounts of code between platforms, have a single code repository, and a single development team for all platforms has massive advantages. It significantly reduces development and test costs, and ensures that there is synergy between the platforms on product features and user experience. However, the most important impact is the reduction in product lifecycle costs.

Microsoft has since released .NET MAUI (Multi-platform App UI), which offers some significant improvements over Xamarin.Forms.

One of the key improvements is the streamlined architecture. Previously, with Xamarin.Forms, you had multiple projects within a solution. .NET MAUI simplifies this with a single-project architecture, which saves development time.

Additionally, in Xamarin.Forms, you sometimes had to write platform-specific code for Android or iOS to meet certain client requirements. .NET MAUI largely eliminates this need by consolidating everything into that single project. It also supports the latest .NET versions (six, seven, eight), offering better performance and access to newer features. Overall, .NET MAUI seems to have addressed these potential areas for improvement within the Xamarin framework.

Managing code is useful using TFS, so a separate code managing software was not required. Authenticating user to app is easy using Azure authentication, which is supported in Xamarin

I have been using Xamarin Platform for four years and learning new things each day. Being just an Asp.NET C# developer, I feel more confident because, for me, developing apps for iOS and Android is a dream came true, without migrating to Objective-C or Java.

Also, it’s cost-effective when you don’t require more native developers for each platform. You can train one C# developer for Xamarin using free resources or even provide paid training, and he or she alone can deliver your apps for each platform.

Xamarin brought various benefits to our clients. For example, we were able to optimize the service organization for one of our clients. Customers can use now a branded mobile application to submit issues within the customer products. It allows for QR code scanning with error details. It makes it much easier for customers to report issues and for service employees to collect all necessary data, then quickly respond to the customer’s needs.

All of our mobile developers can easily substitute for each other on different projects and platforms.

• Because of the C# programming language, we can train our .NET developers to learn Xamarin and develop mobile apps easily. 
• It helps us to easily integrate and implement Azure Cloud API services. 
• We can track mobile usage with the help of the mobile device center.

Creating mobile apps became quicker as we started to use the code base function.

It usually saves time for application development. We write once and the code works everywhere.

• A much larger portion of shared codebase
• Better usage of software patterns
• Better knowledge sharing among team members
• More streamlined, standardized development and testing processes.

The company that I work for develops white label applications. Xamarin makes it easy to create white label applications for all platforms.

Xamarin.Forms exposes a complete cross-platform UI toolkit for .NET developers. In our case, we used existing C#/.NET knowledge to build native iOS and Android. The advantage is that a single team can target multiple platforms (Android, iOS, and Windows) on a shared C# codebase.

We have a lot of applications, which cater to different types of end users. These have really helped us in creating a connected system, which has enhanced the productivity and usefulness of different products.

Easy set up Automation framework with Specflow (BDD Approach) and NUnit. Same code works for both android and iOS (If locators are same). Even though if locators different we can use the same code with different locators (Using conditions). It helped to automate iOs and android apps for our client within show time which helped them for regression testing (daily basis) so manual effort reduced.   

We have some projects on the sport-level worldwide, not only in Europe. One of our examining apps is the GDPR tool. We want to expand the GDPR tool to mobile apps for local sports and in other non-profit organizations. That's the reason why we want to develop mobile apps in the Xamarin Platform, so we can connect local organizations to sports, tourism, and non-profit organizations. That's our focus.

From a developer's point of view, with the help of Xamarin, we can focus on the functionality, rather than spending time coding differently for iOS and Android.