Xamarin Platform Reviews

It's just giving me that flexibility to save the resources right including hiring a different native developer so they can hire the Xamarin personnel who can handle both iOS and Android applications. It will save time, cost, and money. That's the main vision and why our company is using the Xamarin technology application. It's a common UI for both iOS and Android.

The product has a lot of features. 

The common UI is great. You can just write one XM channel core and it'll be used for both iOS and Android. That is a strong feature. 

It's just natively compiled on the device like other platforms. It can work across platform technology and is natively compiled to build onto both platforms. You can access the native features through the custom vendor, which we call Dependency Services. Dependency Service is another vital feature to access the native functionality of the different platforms, including iOS and Android. 

It's not too difficult to set up.

They should focus on the Xamarin compiling item. It's hard to find what the exact issue is on the Xamarin core. They have to focus more on the Xamarin compiling features and tools and maybe test some options.

We'd like to have some chat support functionality. It would be helpful if we got responses faster. 

They have to focus more on UI debugging. It may suddenly crash without a known reason. They have to focus more on the performance or debugging things and, or course, publish more packages to support both iOS and Android.

I have been working on this platform since 2015. I would say it's been almost seven years.

It is stable, however, we expect more rappers so that we don't need to write a lot of code to get the native features. They should make available a lot of the frameworks so that it is easy to understand. We've also had to do some debugging.

I've found the Android version scalable. In general, I'd say you can expand it. 

We're using it in the IT department, and I have been working with this company since 2015, and it's used all over.

In our department, we have maybe five or six people who work mostly on the Xamarin side.

We tend to get a quick reply. Sometimes we have to wait for a couple of business days. I'd be happy if they gave us some kind of chat system so that I could quickly get a response instead of waiting on an email from the Microsoft team.

It's not difficult to set up Xamarin. It'll come with the visual studio directly and you can click it. Even for the beginner to install Xamarin, it's pretty straightforward.

The deployment for both iOS and Android is good. Sometimes with Android, it is taking time. iOS is faster. For example, iOS is a couple of seconds, maybe 10 or 15 seconds. Android has a lot of dependencies. Therefore, compared to iOS, Android is slow; however, generally, it'll deploy within 15 to 20 seconds or maybe 25 seconds sometimes.

We took the Visual Studio licensing. If you take that license, this product comes with it. 

It might be $400 or $500 per year. We are using the Enterprise version of the software. They might pay per year or per developer. I'm not sure of the exact rate.

I tend to work with the most up-to-date version. 

We are using the Azure cloud to deploy the application. Our CHD is configured on the Azure pipeline.

I'd rate the solution eight out of ten. I've worked with it for a long time and like the product in general. 

The strongest use case for this solution is developing cross-platform mobile apps. Most people are building both Android and iOS, and Xamarin lets you reduce your development efforts and build it from a single code base. You can build for Windows and Mac from it also, but most people are using it to build mobile apps.

Xamarin.Forms is a framework that's coupled with the Xamarin platform, and I think one of the biggest productivity gains is that you can build a single UI using Xamarin.Forms and it runs on both platforms. Plus, it gives you the ability to use C-Sharp, which is a very mature, robust language. The combination of forms for cross-platform UI and C-Sharp for the programming language are my two favorite features.

The solution struggles a little bit with binding libraries. If you want to use something like Google Maps or a third-party component that's been built for Android or iOS but isn't part of the actual Android or iOS platform, you have to build these things called binding libraries. It's a tedious process and the tooling doesn't do a lot to help you with it. The really common libraries usually have bindings already built that you can use, but if you get stuck having to build binding libraries, it's a lot of work.

I'm a Mac user and I'm not a huge fan of the Visual Studio for Mac because it's not as strong of a tool as the Visual Studio for Windows, and you don't have the same features on both. That's why I have to resort to a different IDE. I generally work in JetBrains Rider because it's a much better IDE for Mac. The IDE support on Mac lags, but they do have a new version of Visual Studio out, so I can't say I've given it a fair chance yet.

I have been using this solution for about ten years.

I think the stability is slightly stronger when building iOS apps. When you build an iOS app, there's nothing that is really restrictive, so you should be able to achieve the same type of performance, look, feel, and quality of using Swift and all the native iOS stuff.

The Android apps run pretty well, too. I noticed a little bit of a performance hit on the Android side, but that's because there's some pretty complicated architecture stuff. Overall, I would say you can build very high quality apps with the solution.

The scalability is more based on your backend than Xamarin itself, but there are no real restrictions. You can add developers to the team and there's no restrictions with Xamarin that you wouldn't encounter with any other mobile development platform.

I'm a contractor, and my last customer had five developers using the solution. 
I heard about one mobile team in Denver at Charter Communications that had 25 people on it, but that's a lot. I would say most teams and companies that I've worked with have between two and six developers using the solution.

This is a Microsoft product and you go through the same channels for tech support that you do for any other Microsoft products. I would say they're pretty good at getting back to us. Parts of Xamarin are maintained by an open source team, so that's always a challenge as to what responses you sometimes get from them. 

I would say they're as good as any other solution on support. I almost always find solutions on Stack Overflow before I hear back from them, because there's a pretty big community there. I did a lot of work at Cinemark and we had two to three million users a month and I've never run into anything that we weren't able to solve pretty quickly, within a day or so.

On a scale of one to five, with one being bad and five being excellent, I would rate their technical support team as a four.

Positive

The setup is moderately complex. In general, I don't think development for a nice mobile is very simple, but I wouldn't say that it's super complex. .Net itself is a pretty productive programming language, so it helps you with a lot of things, but there's definitely a learning curve to get up to speed on it.

It takes a day to get the solution configured on your workstation, if you know what you're doing. The reason I say that is because you have to install the Android SDK, the iOS SDK, and then you have to install Xamarin on top of all that. All of them have to be installed and configured correctly for everything to work, so there's a lot of dependencies. I think it probably takes at least a day to get a workstation set up and configured, and then you're off and running. 

In regards to DevOps and all that, in most places I've worked, you have developers with their individual machines configured. Then when you merge your code into a git repository, the builds are automatically done and either sift to the testing team or are uploaded to the app stores, depending on where you are in the project. That might take a week or so to get going, but just as an individual developer, it takes about a day.

There's no licensing cost for Xamarin. Like the rest of .Net, it's open source, but there is a licensing cost if you want to use the IDE. There's a number of different development environments you can use. 

You can use just traditional Visual Studio. I license Visual Studio Professional. It's about a thousand dollars a year and Xamarin comes with it. 

I also license another IDE, which I could run independently. That one is called JetBrains Rider, and it's only about $200 a year. You could do all of your Xamarin development with that if you didn't care to license the other stuff. 

The actual platform itself technically doesn't require anything. If you wanted to download Visual Studio Code, which is a free IDE, and figure out all the plugins to get everything to build and work the way you wanted, you could actually technically develop for free, but I don't think many people do that.

I would tell people considering this solution that there's a lot of training available. There's a lot of documentation on Microsoft's website and apps for getting started. Places like Pluralsight also have a lot of video training. I would recommend downloading the IDE and going through some of the Microsoft tutorials initially, and then jumping into Pluralsight to find some deeper training.

I would rate this solution pretty high. I would give it a nine out of ten. I've never had the Xamarin platform cause a project to fail. In other words, I've been successful in every project where we've tried to apply it and, except for external problems with the requirements or things like that, I've never run into any technical problem that I couldn't solve with Xamarin. The apps that you can produce can be very professional depending on how much time you put in and you can dramatically reduce the amount of code you have to write to support two platforms.

We use the solution for inventory management in our warehouse and also for unbound deliveries.

The solution is easy to understand and has banking integrated. The shorter development time, the bugging and as well as availability of a lot of documentation on the web. Also the native integration is easy.

The monitoring of the remote devices is not good as it should be extended along. It would be useful if the log is more integrated with the central console. I am not sure it can be accessed but it would be better.

I have been using the solution for six to seven months.

It is a stable solution.

It is a scalable solution. There are four to five users using the solution. Some are in the US, some in Europe and some in Spain.

We have not used the technical support as there is a lot of information on the web.

The initial setup was easy. We used the MDM for the deployment as it can be deployed to remote devices. The deployment took two days but the problem was after that for fixing and backing. The maintenance becomes difficult because there is a problem with the log. If there would be a better log that would be transmitted to a central console would be better because we have to get the log from the remote device and analyse what happened

I think the solution is free.

I recommend other users to use it, like the native integration or native development or native features. We use the SAP so they have to consider which kind of integration they should adapt to with SAP. I rate the overall solution a nine 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.

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.