Xamarin Platform Reviews

I used this solution for three years.

I am not using this solution anymore, but I had Visual Studio and Xamarin installed — we were using components of Xamarin.

We were trying to integrate some PSPDFKit functionality. We wanted to open up a PDF document to the last page that the person opened it. If it was a five-page document and they opened it on page two and then when they closed it, they wanted it to open back up to the page where they left off. They were trying to get the PDF to be sticky.

The product owners that were looking at it liked the functionality. There was a competing product library called PSPDFKit. They wanted to get rid of that because it costs a lot of money; however, they wanted the functionality that the PSPDFKit had, inside Xamarin. There were some issues with it that they were trying to resolve.

When they put their ticket in, Microsoft pointed to Xamarin and Xamarin pointed at Microsoft, to say who's going to fix it. That's where it got left off. Xamarin was never able to utilize that module for the PDF. They had to keep the PSPDFKit software, that's the current state. 

The software itself was pretty good. The problem that I faced was that the communication, the roles, and the responsibilities, weren't defined between Microsoft and Xamarin, that's really where the problem was in my opinion. Nobody was taking ownership of that. 

Let's say you have two platforms on-prem. If you're an iPad user, you want the look and feel of the iPad; if you are a Surface Pro user, you want the look and feel of the Surface Pro. What I feel is of the utmost importance in regards to Xamarin, is to make sure that when you do something, whatever the object is, you get the object that the iPad user expects. Conversely, if you're a Surface Pro user, you get the object that the Surface Pro user expects.

I was in favor of it, it had the capabilities. I was impressed by the way they were thinking of moving it forward, scalability-wise.

The developer activity was complex, but it was understandable. From my perspective, I wanted to minimize the number of software vendors we were working with, and consolidate where features were overlapping. The reason I was trying to do that was to try and save the government some money. I was thinking I was still paying X dollars for one contract for three years, and Y dollars for another contract, and the features were all the same — what's the use of paying for both?

I believe the initial implementation took two years. They developed a working product that was in production. Xamarin was included in that initial design.

They had good documentation regarding implementation, but I understand it was evolving and integrating into Visual Studio.

When someone's building something, they want the capability to do so across the platform; initially, there was a goal to build something for iOS, something for Windows, and something for Android. The first thing they dropped was the Android approach. They ended up keeping the iPad and Windows. You write the code once and it generates in both, or in multiple outputs. 

In our situation, we were supporting it on the iPad — 95% of the people used one. A very select few people used Microsoft Surface. It's a tremendous effort to keep both going, although that's the whole purpose of having Xamarin.

It's a great concept. I think it worked well. The concept of doing it is still not perfect. When we generated some code on the iPad, we would get fewer bugs, and with Surface Pro, we would get more bugs.

The same code was pushing a bug on Surface Pro, but not on the iPad. That's basically a fact of maturity over their capabilities. From a business point of view, it didn't make sense for the use case that we had — it was a huge cost for a few users. In many situations, Xamarin has a purpose. There are good reasons to build it once and have it work on both platforms.

Not from a technical point of view, but from the business side, if I was consulting to a large government organization and looking at the cost-effectiveness, I would suggest they have iPads or Surface Pros and give them to their public users — make them decide upfront instead of going down both paths, doubling the paths.

On the market, compared to everyone else, they're the top solution. They're the best solution out there that I could see. On a scale from one to ten, I would give Xamarin Platform a rating of nine. If they become bug-free, I would give them a rating of ten.

We have worked on Android and iOS applications using the Xamarin Platform. In addition, we have used it to build Android and iOS applications.

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.

Xamarin Platform is a platform that uses C Sharp and allows you to create hybrid applications. The best part of this solution is that you can create one solution in C Sharp. It works for both Android and iOS.

They can improve their marketing to have more popularity as other solutions in the market. I haven't seen that many limitations in the Xamarin Platform. It's pretty UI-heavy, and some may say that Xamarin applications are a bit slow, but that is probably only if the developer hasn't followed the instructions.

Creating an application works like a native application, but the file size is a bit big, so you have to make certain layers. That is one drawback, but it is understandable because we use an external platform. When we build the project, the C Sharp code and the Xamarin Platform get converted into the native code in Android and iOS, so we have to have a middle layer bundled inside our application.

In the past, when we wanted to select a file from our mobile storage, we could not, and that feature was missing, so we had to implement it in native code and then use it in our code. But now they have created Xamarin Essential, which has all those features.

We have been using this solution for six years and use version 4.7. Xamarin Platform is used for hybrid mobile applications and building app solutions for Android, iOS, and Windows.

It is a stable solution.

It is a scalable solution. Mostly the developers at our organization use this solution. Microsoft acquired Xamarin, so it is part of their Visual Studio and maintenance is done by Microsoft.

Before using the Xamarin Platform, we used a hybrid technology solution, like Paladin, but it was difficult to use. If a company is using C Sharp or .NET to build their products, they'll want their current team to work on it so C Sharp developers can easily move into the Xamarin Platform to create the hybrid application. It depends on your client and requirements if you're going with Xamarin Platform or React Native.

Our deployment process is simple. It happens in-house, and we don't use a third party. We create an application on Google Play Store, the same as deploying regular Android applications with one additional step of archiving it. So, from Visual Studio, you archive it, sign the application, and then upload the .AAB file on the Google Play store or iOS. You create an archive from here and can upload it using the file uploader Mac provides.

I do all the deployments myself and need 30 minutes to create a full application and deploy it for Android. For iOS, it takes about five minutes.

It is a free platform.

I rate this solution a nine out of ten. Most people choose React Native over the Xamarin Platform because it is more prevalent in the market. Xamarin Platform requires learning because it is an old language. It uses C Sharp, so not everyone can work with it. It is a bit difficult at first, but once you start working on it and get the hang of it, you can do everything in the Xamarin Platform.

We use Xamarin almost exclusively for development of native mobile applications, even when single platform. The development hardware that we use are MacBook Pros with 16GB RAM and min 500GB SSDs. We run Windows 10 in a Boot Camp partition and virtualized using parallels. We have Xcode installed on the iOS partition and Visual Studio 2017 installed on both Windows and Mac partitions, along with Android SDK and NDK.

We use Xamarin.Android and Xamarin.iOS for apps with a complex UI, and use Xamarin.Forms where applicable.

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.

It allows the development of truly native applications in C# using the power of .NET framework and Visual Studio.

Xamarin allows the same development and build environment to be used for all platforms and code to be controlled in a single code repository. Shared logic, such as business logic and models, can be shared between the platforms, which significantly reduces development, test, and maintenance efforts. Typically, this leads to around 75-80% code reuse between the platforms. If Xamarin.Forms can be used, then this reuse typically rises to around 95%.

Xamarin also leverages the full power of the .NET Framework, including things like lambdas, LINQ, properties, bindings, commands, etc. Lastly, it uses the Visual Studio IDE, by far the most powerful and complete IDE available, making development and maintenance much easier.

The Xamarin SDK provides C# bindings to all native iOS and Android SDK APIs, as well as access to the .NET framework and builds to a native package. The Xamarin Mono run time runs a .NET CSR alongside the native run time with a bridge between them, and handles memory management and garbage collection.

App behavior is completely native and performance is near native (depending on the app architecture, but can be even faster than native if the business logic is computationally intensive). App size and memory footprint is slightly larger than native, due to the need for the inclusion of the .NET and Xamarin libraries. In a debug build, this can be significant. However, in release mode, the build process uses a rigorous linking process which removed most of the unused classes and methods from the managed DLLs. As a result, the average app size increases in a release build by only 5 to 6MB.

The most common issues involved are with the IDE and build process. The worst build issue concerns are the caching process MSBuild uses to reduce the build time. It is unnecessarily complex (internally) and will sometimes leave cached files which should have been removed, even when a full solution clean is performed. The work around involves closing the solution and deleting some project folders. Occasionally, IntelliSense loses sync with the code and provides visual error indicators when no error exists.

Xamarin.Forms does have some short comings, especially surrounding performance. Launch time on Android is a particular issue because Xamarin.Forms loads all the external assemblies during initialization. Support for lazy loading or merging of assembles would significantly reduce this, but Microsoft is still committed to a solution. Support of platform specific behavior could also still be improved. However, I believe strongly that Xamarin.Forms is the future of cross-platform native mobile development.

I have been using Xamarin for about seven years, since before it was Xamarin (it used to be MonoTouch and MonoDroid).

I am using the Xamarin Platform because I am using Visual Studio or Xamarin Studio.

The most valuable feature of the Xamarin Platform is that both the UI are the same in Android and iOS, in one project and Android and iOS, are applications for developing PCL projects. Additionally, the dashboard is good.

The Xamarin.Forms could improve.

I have been using the Xamarin Platform for approximately two years.

Xamarin Platform is stable.

The scalability of the Xamarin Platform is good.

We have four developers using this solution in my organization.

I have not contacted the support from Xamarin Platform.

The initial setup of the Xamarin Platform is easy and takes one day.

Xamarin Platform is a free open-source solution.

This is a good platform.

I rate Xamarin Platform an eight out of ten.

The primary use case of this solution is to reduce the development of applications. For example, when we develop an application for both Android and iOS, instead of writing two different applications using Java and Quest, we write everything in Xamarin Platform and that one application can run on Android and iOS.

The solution saves us time by containing all the development work in one application instead of two and it's well-documented. The solution is consolidated, meaning that it's been on the market for many years. Xamarin Platform is stable, it works, and it is very simple.

The solution always has room for improvement with price, integration, stability, and documentation.

I have been using the solution for one year.

The solution is stable.

The solution is used to develop apps for mobile devices so there is no limit. We have 10 developers using the solution in our organization.

The initial setup is very simple.

The deployment was completed in-house.

There is no license fee because the solution is open-source.

I give the solution an eight out of ten.

I recommend the solution to others.

I'm a developer and we are customers of Xamarin. 

We are a 5-member team and Xamarin provides us with a tool kit that crossbreeds from hybrid applications. We write a single line of code that works both with android and iOS. It's a main feature of Xamarin and makes the product very user-friendly. 

The application platform could be improved. We've had some compatibility issues on the android side with the different versions although they work fine with iOS. The product lacks some controls and enhancements that would provide additional features that we need.

The solution is stable. 

The customer support is quite good, they've helped me several times. 

Positive

The initial setup is very straightforward. Implementation takes about an hour. 

This is an open-source solution and there are no costs on the Xamarin side. If you're using it with iOS then you need to purchase a membership which is about USD$100 per year. 

I recommend Xamarin Platform, it's a good solution and I rate it eight out of 10. 

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.