Xamarin comes in various flavors. At the technical level, we use something called Xamarin.Forms, which is the most popular flavor of Xamarin. You also have some older flavors like Xamarin.Android and Xamarin.iOS. Those are specifically targeted for native app development, whereas Xamarin.Forms are more for cross-platform app development, where you can write code once, and it will run on all supported platforms like Android and iOS.

However, Xamarin will be "decommissioned," though that's probably not the right word because Microsoft has introduced something called MAUI as a successor to Xamarin.Forms. Microsoft acquired Xamarin, built on top of it, and introduced many features after they acquired Xamarin. Xamarin has some flaws, but since it's been there for eight to nine years, there are known workarounds for existing issues found through the developer community. On the contrary, MAUI is a new product full of bugs because it was introduced very early. It's an extremely buggy solution introduced by Microsoft, which is why, if you do some research, you will discover that there are currently no enterprise solutions that use MAUI. Microsoft is then going to lose its limited foothold. Even though MAUI was introduced more than a year ago, there has been no large-scale adoption by any enterprise. Microsoft is kind of forcing all these companies to move from Xamarin to MAUI, but none of them are willing to do that because it's such a poor product, including my organization. However, the first two or three iterations of Microsoft's products were full of bugs before they radically overhauled their solutions. MAUI is useful for small hobby projects or individual developers who want to play around with mobile development. Many of these organizations will now move to other solutions like React Native, an open-source solution from Facebook, or Flutter from Google. Likewise, they might choose native solutions like Android Studio with Kotlin or iOS with Xcode.

Xamarin has a very limited market share in the mobile development space. There are hardly any job openings for Xamarin. On some sites, there would be fewer than 50 job openings for Xamarin. By contrast, with React Native, you would find the number of openings for it to be much more than Xamarin. The same goes even if you search for something like iOS or Android. This suggests that Xamarin is used by a very small percentage of enterprise clients.

We use App Center when deploying the solution, and it automates deployment. Likewise, If you want to update the version of the app on the Apple Store or Google Play, you just have to trigger a build on App Center, and then it takes care of building and deploying the app to the App Store or Google Play.

I rate Xamarin a five out of five. The way I see it right now is that there are three big players in the market for cross-platform development. We have Flutter offered by Google, React Native offered by Facebook, and Xamarin offered by Microsoft. If React Native would be eight in popularity and adoption, Xamarin would be maybe five point five or five out of ten. Flutter is a relatively new technology, but it's picking up very rapidly. It has already surpassed Xamarin or will surpass it very soon. Xamarin will retire in a year or so, and MAUI is in bad shape. I expect Flutter and React Native to be the two most popular technologies for cross-platform mobile development.

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.

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.

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. 

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.

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. 

The platform is easy to learn as many tutorials are available on YouTube. Additionally, many Microsoft MVPs offer demos and resources that simplify the learning process.

When deciding on a mobile application development framework, it's essential to consider your specific requirements. Evaluate the pros and cons of each available option, including alternatives. The choice ultimately depends on how well the technology aligns with your project needs and your comfort level with learning and adapting to new tools.

I rate it a 9 out of 10.

I rate this solution a nine out of ten. I rate it a nine because it is a great framework tool for them to develop mobile apps within .NET., and only minimal XAML knowledge is required. If they don't have the XAML knowledge, the developer can design within C#. In addition, the community in Xamarin Platform is big, and many developers and program managers from Microsoft Azure. They inform of tips and tricks whenever new information is available about Xamarin on YouTube, Twitter, or websites. As a result, all developers contribute to design challenges.

We have so many developer teams for many frameworks and languages. Xamarin Platform is suitable for the developer who knows the C#, .NET framework and is familiar with XAML. They can easily do mobile app development in Xamarin.Forms.

Regarding additional features, they have already introduced MAUI .NET 6.0, and they are upgrading these Xamarin.Forms to MAUI. I think they are supporting Xamarin.Forms next year, and after that, all the applications will move to .NET MAUI. I believe they have already introduced many features in .NET MAUI and are working on other features to introduce in .NET 7.0 and .NET 8.0. Every quarter, the .NET products release new features and fix bugs.

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.

I would rate this solution a seven out of ten.

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.

I would recommend that anyone that is considering implementing Xamarin into their organization first learn all about the product. You can learn directly via Microsoft videos. After, you can learn about the languages Xamarin uses. 

Once you have developed your applications by yourself, and you have learned about the fundamental of Xamarin.Forms, then you can start the practicalities of a test project. Then you can start your project, but it takes some time to learn.

Overall, I would rate Xamarin Platform a nine out of ten.

We have been using Xamarin for over four years on multiple app projects of varying sizes, complexity, and code-reuse, ranging from fully featured custom UI social networking applications to data-driven forms apps with a maximum degree of codeshare and minimal UI.

Xamarin can sure look like the one hammer that makes every project look like a nail, but it is not. Here at Seamgen, we consider it another tool in our toolbox, suitable to successfully realize our customer's ideas.

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. 

I would tell potential users to look at the new updates coming in over the next three or four months, as those are critical. The best place for you to start with Xamarin is by following the contributors on YouTube. I know there are many paid courses, but they aren't good or worth the money. It's best to take a course directly provided by the content creator or contributor.

On a scale from one to ten, I would give Xamarin an eight.

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.

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 have been using Xamarin for about seven years, since before it was Xamarin (it used to be MonoTouch and MonoDroid).

This is a good platform.

I rate Xamarin Platform an eight out of ten.

I give the solution an eight out of ten.

I recommend the solution to others.

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

I would rate Xamarin Platform eight out of ten.

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.

If you are already heavily invested in the .NET platform and C# development, Xamarin is the quickest way to make native iOS apps.

Their leadership is exceptional at both listening to the customer base and delivering innovative, best-in-class products. A company that takes great care of its people. 

Xamarin has just been bought by Microsoft. What an endorsement!

I would rate Xamarin Platform an eight out of 10 because, while developing applications using Xamarin Platform you will come across some library issues which need to be taken care of first. But I would strongly recommend Xamarin Platform because it’s a reliable technology compared with what is out there in the market and a plus-point is support for C# language. 

My only advice is that you please do a proof of concept before diving straight into development. It is always good to see beyond what you want and the requirements of your project. First, do some benchmarking of the requirements and then go for implementation of your solution.

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.

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

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

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

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

I have been using this solution for the past three years. I have developed many iOS and Android apps using Xamarin classic as well as Xamarin.Forms. In a nutshell, I would say that for those who love C# and mobile, this platform is a blessing.

I would like to rate this solution as a seven out of 10. The reason for this rating is that this solution is definitely better than others. We can share a lot of code among the different platforms and can also use our C# skills, which we love. In addition, we can get native UI, native API access, and native performance. Still, there are a lot of areas in which Microsoft can make it better. And I must say, they are working on it.

Architecture is the key point of every successful project and this is applicable to Xamarin as well. When implementing any project, one needs to be sure the app is following all the design patterns like MVVM, dependency injection, etc.