Xamarin Platform Reviews

I use Xamarin Platform to design application UIs, integrate APIs, and create special features.

Xamarin Platform's best features are its single codebase, the support from Microsoft, and the free libraries.

Xamarin Platform's performance base could be improved. In the next release, Xamarin Platform should include gradients and a looping feature in its path

I've been working with Xamarin Platform for over two years.

Xamarin Platform is stable.

Xamarin Platform is scalable.

Microsoft's support is one of Xamarin Platform's best features.

The initial setup was straightforward.

Xamarin Platform is open-source, but there are fees for deployment, the API Store and Play Store, and using third-party libraries.

I would rate Xamarin Platform eight out of ten.

We use the Xamarin Platform to develop applications. We develop mobile Android and iOS applications.

The best part while using the Xamarin Platform is a cross-platform application. We could execute iOS and Android while writing a single line of code. The most important feature of the Xamarin Platforms was this.

I believe there is already a better version in.NET MAUI. Xamarin Platform has already been shut down in the month of May 2024, according to my knowledge. Support will be discontinued in the month of May 2024.

It already has a completely new version. It has already vastly improved.

The architecture in the Xamarin Platform has to improve, there are some features missing.

There are no borders. The main thing that the Xamarin Platform lacks is a user interface. It is somewhat difficult when we are creating the UI.

Borders and sheets are two of the most important features that are missing in Xamarin. The frame is heavyweight. Sheets, nowadays, we see looking sheets on every platform and in every application. It will come from the bottom. When you finish paying, it will come from the bottom. It's similar to the system's successfully completed sheet.

I have had 15 months of experience with the Xamarin Platform.

I believe we are currently using a three to four-year-old version because this is a long-running project.

The Xamarin Platform is a stable solution.

Xamarin Platform is scalable. We can add to it.

In our company, we have approximately 20 developers.

I have never used the help of the technical support team.

In my company, the majority of the software we use is Microsoft-only, such as MVC,.NET MVC, Power Apps, PowerPoint, and Power Apps CRM. The majority of the software we use in my company are Microsoft products.

My company is 99.9% dependent on Microsoft products.

It is easy to install.

While using Visual Studio, it is easy to use the Xamarin Platform.

The time it takes to install Xamarin is dependent on the internet speed. 

We can easily install Xamarin in 30 to 40 minutes, depending on internet speed.

It is extremely quick If you have high-speed internet as well as some RAM and systems processor. It will be very fast if it has an i7 processor.

There is no requirement for a license. It is available for free as an open-source product.

If you are new to the Xamarin Platform or thinking about using it, my advice is to start with.NET MAUI instead, because Microsoft support for the Xamarin Platform will be discontinued in 2024.

.NET MAUI is a new tool and platform for developing everything.

I would rate Xamarin Platform an eight out of ten.

I am not giving it a ten, because I don't know the other languages. Flutter is a major competitor for Xamarin in mobile applications. But I'm not familiar with Flutter. That's why I'm giving it an eight.

We mainly build mobile solutions for enterprises. In most of the cases, it does require a lot of complex domain knowledge and multiple integrations with various internal systems, pretty often legacy ones. 

We decided to work with Xamarin, since it does give us a lot of advantages compared to fully native solutions, which use Java or Swift/Objective-C. First, it allows us to reuse our knowledge of C# and .NET Framework. Next, since .NET and Java are the most common choices for enterprise platforms, it allows us to reuse some parts of business logic without the need to re-write/port them. Then, there is the possibility to apply well-known MVVM patterns to both Android and iOS targeting apps with reuse of up to 70% codebase between platforms, not to mention automated testing possibilities.

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.

The possibility to share business domain model-related code between iOS and Android.

It would be great to have some quirks of Xamarin.Forms solved. However, the number of community developed libraries and components are growing rapidly, so this should be another advantage soon. 

Nowadays, it is common to find a problem that you would need to develop from the start since there are no third-party components to reuse.

It does have its drawbacks. From time to time, it is a bit harder to code some specific scenarios compared to the native approach. Since Xamarin is the another layer of abstraction, it also adds its own bugs to the whole process. However, the overall experience is really positive. The benefits listed above are much higher than the costs associated with the overhead needed to work with Xamarin.

In most cases, I develop apps for iOS and Android, but there are some rare cases that include UWP platform. My environment includes a Windows 10 PC with VS 2017 and a Mac mini with VS for Mac.

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

• One language for all platforms: C#
• XAML for UI in Xamarin.Forms
• Provides 100 percent coverage of APIs on each platform

I would like to see hot reload, similar to what Flutter has out-of-the-box. There is "Live Reload" but it’s still in preview and was only recently announced.

There have been some stability issues, mostly with VS 2017 for Windows when working with iOS.

No issues with scalability.

Community support is great. You can always ask on the Xamarin forum or Stack Overflow. If you are a member of Xamarin.University you can get a one-to-one hour with a technical instructor.

Xamarin is my first cross-platform framework.

Using early versions of Xamarin, especially VS on Windows for developing iOS, were a mess. But now, with the latest installer, it is really straightforward.

In most cases, it is sufficient to have free/community license. But if you plan to seriously develop production-level, highly polished apps, you need to use Xamarin.Profiler and the professional or enterprise license.

I rate it a 10 out of 10. It's the best cross-platform framework, and it continuously improves.

We have been using Xamarin for enterprise mobile application development. Primarily, we are targeting iPhone devices. This field mobility application helps end users to perform their duties and view 360 information about the work to be performed.

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

We very much like the XAML design techniques, multiple layout and pages, MVVMCross support, and portability across different platforms.

• It needs offline sync capabilities to store data on devices persistently. 
• Security features and data analytics need to be improved.

This is a free product, so there is zero investment on licenses and IDE.

This product is very easy to design and develop, and it is using C#. Microsoft is supporting this application, so product reliability increases.

• The ability to work in macOS for Xamarin iOS solutions
• Cross-platform support

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

Xamarin Studio should be more polished and support native functions (iOS, Android). It should be working like a charm.

I have used this solution for three years.

Generally, when iOS products get updates, some issues can happen with Xamarin. Crashes happen from time to time.

Most scalability is handled on the server side. In rare cases, some libraries weren’t supported, such as the TCP/IP stack.

Technical support is good.

Setup was actually pretty complex, as we had to get experience. We had some oddly written solutions provided from previous vendors of our customers. These were impossible to maintain.

By the third year, we got a solid ROI. It’s hard to measure, but is was probably over 200%.

Licensing and pricing have changed, as the product moved to Microsoft. Before that, it was fairly complex: $800 per developer place, for one platform only.

We did look at alternatives. However, other solutions were only hybrid platforms, which lagged behing when doing moderately complex projects.

You will need to invest a bit of time to become a good vendor using this framework.

I use Xamarin.Forms to develop mobile applications, which basically have the same functionality and cross-platform.

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

In Xamarin.Forms, it is valuable that one and the same code (including UI) work on all platforms. It is very convenient.

They need to take a step towards independence from the UI platform. It takes a lot of time to adapt the native controls.

Everything is fine. There have been difficulties with memory leaks, but usually they are not difficult to fix.

No issues. Everything is fine.

The support is not very good. Bugs remain very long openable.

Earlier, I tried to write code on native technologies, but still liked C# more. 

We switched because it makes cross-platform applications more expedient, faster, and cheaper.

Everything was simple. Besides, on GitHub there are always good examples. Although, you need to understand the native SDK a bit.

Good knowledge

Xamarin is free, or comes with Visual Studio. Therefore, it is very profitable.

I looked at Ionic and other HTML/JS platforms, but I considered this a bad decision. They were too slow and you had more problems with their frameworks than the benefits of their work.

Be sure to look at the lessons from Xamarin University, as well as test projects on GitHub.

Mobile applications for our music streaming service. 

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

• Cross-platform development saves time and provides consistencies. 
• C#: Simply the language. 
• Native UI: No compromises needed for final users. 
• MVVM: Clear concerns separation. 

The performance needs improvement, especially the dev tools, and also the ultimate output of the mobile applications.

Five years ago, we switched from native development to a cross-platform solution, we have never regretted this move.