We are currently using xamarin for our iOS app development. We use xamarin for our Android app development as well. We get to choose what platforms we want to use depending on the budget we have to work with. The biggest downside is that it is very difficult to get a good price for xamarin, but we are slowly working on that.
I think most of you in the developer community would agree that having a good price is the best advantage that xamarin offers. It is important to note though that this has been one of the most common problems with xamarin (and other mobile development services, like WPF and Silverlight) that has been around for years. Most of the time the price of xamarin is the same as the price of the platform with the same architecture.
Xamarin is doing a lot of things right, but that’s not to say it doesn’t have its share of issues. For example it can be difficult to deal with the fact that every time you update xamarin you need to also update all your other projects. It’s a bit of a chicken and egg problem.
What about the other two? The other two people are pretty much the same. I know these people a little different. They use the same web client and server, but the web client has a lot more things to manage. Xamarin is the way to go.
As a developer, you need to pay attention to every single one of your projects. It is not just the xamarin code that needs to be up to date, it is the entire application. If you are developing a web application, it makes sense to update all of that. But for a desktop application, it is important to update only the core of your application.
It’s important to have a clear and concise description of your project.
Xamarin is a great tool for developing apps for the web, but it is not a perfect solution. One of the problems I have seen when developing for the web is that you don’t always update the web client. You can update the web client because most websites have a web content management system (CMS), but not all websites have one. And because you have to update the web client, you have to update your desktop application to accommodate for the new features.
Well, now you can update your desktop application to take advantage of these new features. We have seen it work for us. And we are so glad that we did. The problem we ran into with xamarin is that the developer documentation is sparse and generally not the greatest. For example, I was hoping for a way to programmatically add a WebPart to an existing web site. Unfortunately, this is not possible. This is a major problem.
As it turns out, the developer documentation was a bit sparse, but the xamarin team has been making a lot of progress over the last few months to provide developers with a better way of documenting the API. This is good, but it still needs to be better. It’s also important to note that there are a number of new developer features coming out for xamarin in the next few months, and this documentation is still not there yet.
I know at least one developer who has had to struggle to get the documentation updated. Hopefully the docs will get there soon.