Xamarin Platform Reviews

We are using the new release of Xamarin Platform (as .NET MAUI) to create hybrid applications, so we don't need to implement them individually in different platforms. We can simply deploy in a single codeless application which is automatically deployed to multiple platforms. This is the biggest reason why we chose Xamarin Platform to begin with, and the second major reason is that it is produced by Microsoft. Being a Microsoft product lets us do large, sophisticated things with it, and we currently have around 2,000 developers using it in my company. 

Generally, we use a mix of .NET MAUI, Xamarin.Forms version 5.5, and ADO.NET with Visual Studio to deploy mobile applications on Android and iOS through the Google Play Store and Apple Store, respectively, and we also have a CI/CD pipeline using App Center.

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.

My favorite feature of Xamarin platform is the Xamarin.Essentials package.

I also like the changes seen in Xamarin's upgrade from Xamarin.Forms to .NET MAUI, because in the older Xamarin Platform, Xamarin.Forms gave you multiple libraries of a particular level for a single platform, whereas .NET MAUI comprises a single, organized library that contains everything needed for both Android and iOS.

The debugging functionality could be improved in Xamarin Platform because sometimes it takes very long to move through the stages of setting up the application build to the final deployment on a mobile app that resides in a physical device.

I have about 5 years of experience with Xamarin Platform.

Xamarin Platform has been stable lately.

At the moment, we have around 2,000 users working with Xamarin Platform in my company. These are typically developers.

From my experience of using their support to resolve problems, I would rate them as very good.

The setup is easy; not difficult at all.

My company provided all the licenses that we need to support our use of Xamarin Platform.

Xamarin is an excellent platform that I could definitely recommend to others, despite the occasional issues we have had in the past.

I would rate Xamarin Platform an eight out of ten.

We use this solution mainly for mobile app development.

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.

This solution is a cross-form technology, meaning that we don't have to create separate code to deploy apps across different platforms. 

We also find this solution to be simple to use, with a very user-friendly environment.

We have noticed that there have been stability-based performance issues with this product, which need to be improved.

We would also like the notification feature that was available with previous versions, to be included again.

We have been using this solution for six years.

The stability of this solution has previously been an issue, and requires constant updates to maintain.

This is a scalable solution, but it requires some prior training to carry out upgrades effectively.

The support for this solution is good. There are multiple ways to resolve issues, including a Facebook group that has been set up by the provider.

The initial setup of this solution was very straightforward, and the deployment only took 10 minutes to carry out.

This is an open-source solution, but there is a subscription charge to use the App Center of around $100.

I would rate this solution a seven 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 use the Xamarin Platform for developing applications for businesses. I've worked and used the solution for property management companies, and the medical and education sector.  We consume APIs and distribute them within app stores.

The most valuable features of the Xamarin Platform are that it has cross-platform development, one code base serves a purpose on both, and the grid layout is a lifesaver.

Xamarin Platform can improve by making the enterprise documentation better. There's a lot of basic documentation of how to do many of the functions of the solution, but there's not much enterprise-level documentation.

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

The stability of the Xamarin Platform could improve.

Xamarin Platform is scalable.

I am the only one using this solution in my company.

Xamarin Platform could improve the support. Sometimes they're responsive, sometimes they're not.

I rate the support from Xamarin Platform a three out of five.

Neutral

The initial setup of the Xamarin Platform is straightforward. If you want a simple debug deployment it is simple, you only need to press play.

I manage all the way from design, testing, and deployment in the Xamarin Platform. Additionally, we have a web team.

If you are making applications with the Xamarin Platform and they make money then this solution will have a good ROI. However, if you are making applications that are not making money then it will not have a good ROI.

I evaluated other solutions, such as React, before choosing the Xamarin Platform. I'm a .NET developer and the Xamarin Platform was easy to use for me and this is why I choose it.

My advice to others is to look into tutorials, such as on YouTube. There are a lot of resources on YouTube. Additionally, there is a lot of documentation within Microsoft that's good.

I rate Xamarin Platform an eight out of ten.

Xamarin Platform is being used for building applications. For example, shopping and e-commerce applications.

The most valuable feature of the Xamarin Platform is the deployment.

Xamarin Platform can improve if there was a virtual test environment so we did not have to have a Mac system for the iOS testing. At this time You must have a Mac to deploy or generate IBA profiles. 

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

Xamarin Platform is a stable solution. I have published six to seven applications on the Apple Store and they are stable.

The scalability of the Xamarin Platform is good and it updates often.

The support of the Xamarin Platform is good. 

If you start from the beginning and face problems Microsoft support will find a solution. You will be placed in the queue for support from Microsoft, and depending on the issue the time for the response can vary. For example, if the question is the first time it has been asked or has occurred, it could take longer, but if someone has already found the solution previously, it could be a faster response.

Xamarin Platform deployment is very good, it is simple. You must have a virtual machine on your system for the Xamarin Platform to work. The full deployment takes a few days at the most.

It's reducing the cost and time to deploy and deliver your applications to different customers. You can deploy it on Android and iOS, which includes mobile devices and desktops.

Xamarin Platform

The price of the Xamarin Platform is not expensive. However, the price of the solution depends on the application that is made. For example, if you have small applications, it's different from large or enterprise applications.

The cost for us on average is $2,000 to $3,000 for all the projects. This involves starting from scratch until we deploy and package them to the Google Store or Play Store for publishing.

I would advise others to use the Xamarin Platform because it's the technology that is most stable in the market. There is always support from Microsoft and it is updated often.

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.

Xamarin is a framework for creating mobile applications. It can be deployed on any device for mobile app development. I am a user of this solution. 

This is a Microsoft-supported source platform so the technical support is very good and it's close to native. It's all compiled into related code and at the same time wraps old libraries or native libraries into cross-platform libraries which is great. I do a lot of proof of concepts, and part of the reason I like Xamarin is that I'm familiar with it and know my way around which saves me a lot of time. 

Xamarin is reaching its end of life and they're moving it to .NET MAUI, combining it with other platforms and creating a centralized framework. It's a big change that's affecting a lot of the good features and something they could have done in a more user-friendly way.

I've been using this solution for six years. 

I have had times when I ran into bugs which can take some time to sort out. I found out the hard way that these bugs can often take quite some time to resolve and that's obviously not ideal.

The solution is scalable, we can vertically build on top of it.

Customer support is good. 

The deployment is fairly straightforward. Since it's backed by Microsoft, the documentation is expensive. There are MVPs working around the clock to help get you up to speed, so implementation is a breeze. It's not really a problem. In that respect, it's much better than React Native. I've deployed this on my phone. 

Xamarin is open source, so it's free. If you're planning on development within a company, it might require purchasing the commercial version.

Until relatively recently, I used this solution all day, every day, but at this stage it would not be my go-to choice and I'd now prefer Flutter or React Native. If you're starting something new and you have experience with .NET, and are already in the environment of the ecosystem, then I would say that you could potentially use Xamarin. But if you are coming from a JS perspective, then I would recommend Flutter. If you're production ready, go with Flutter or React Native. 

The solution has served me well and I rate it eight out of 10. 

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.

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.

Our company uses the Native solution to build mobile apps in DevOps that we push to app stores. 

One of our clients is an insurance company and we are building a forms app that needs to be nice but not super smooth because the app is more about data input and output. 

The solution allows us to share libraries from the mobile app to our client's web project. 

The solution's most valuable asset is its shared code base in C# that is better for large apps. 

Code is transferred to the .NET framework and the standard libraries for shared code are great. 

The solution is reliable with a very manageable hierarchy that allows multiple roles and permissions.

The solution's pull request system is quite good and unit testing is useful. 

The solution does not include Hot Reload which is painful because it causes us to wait quite some time for huge builds. 

The solution does not allow for use of the latest or premium version of Visual Studio so we have to use the 2019 version. 

The layout interface and designer for Android Studio is more advanced than the iOS Builder. Most of our layouts have to be built in Xcode but broken connections and file updates are continuing issues. 

Standard libraries have not been updated in four years because the focus has been on newer products like Xamarin.Forms and .NET MAUI. 

To continue to use the solution, we have to bind SDKs after new Android or iOS platform releases. 

No support is offered that would make our lives easier so we rely instead on Rider as an ID for development because it includes ReSharper. 

The auto update system is not trusted because it has broken our builds on occasion. 

I have been using the solution for ten years. 

The solution is reliable and stable with no bugs. 

We disabled auto updates because on occasion they were breaking our builds. 

The solution is scalable because of C# which allows large builds across teams. 

I don't need assistance often and am satisfied with past technical support. 

One issue regarding Test Cloud was resolved.

Another issue involving the iOS platform was not resolved by support so I ended up fixing it with a workaround. 

In general, forums contain topics that include workarounds for very early in an issue's lifecycle. Our team has been successful in fixing issues internally. 

I used CodeGear for another project. 

The initial setup is straightforward. 

Setup issues are not with the solution but are caused by native items such as Android and iOS provisioning profiles and upload rights. 

Our company includes 30 developers who deploy the solution through a week-long process that includes multiple steps such as regression testing, Test Cloud, and internal processes. 

Once all steps are complete, we automatically upload to stores and promote the version to be used. 

We maintain apps we build for our clients. 

Android Studio is growing faster than Visual Studio or Xamarin Studio because they focus only on Android apps. 

The native development of Android Studio is not comparable to Visual Studio. 

MAUI is amazing because it offers multi-platform distribution.

The solution is good but doesn't fit every app or use case so you should consider all options. 

The solution's strength is in form apps but it is not the best option for small, pixel-perfect apps full of animation and transitions. 

The solution does not include native bindings so you have to create one which is a hideous process. Our company opted to work with a third-party for binding six iOS libraries. It was too tedious to have to go through a whole update cycle after changing one item. If an app relies on third-party bindings or libraries, I don't recommend using the solution.