|
As far as my experience with Xamarin goes, it's not usable for production in any way. too many limitations and strange behaviors. No need in Azure and all that proprietary MS formats and things.
I prefer native solutions over those one-for-all frameworks.
|
|
|
|
|
Be careful. Unless you're using native functionality and / or you have a large development team then going native is (probably) the wrong approach[^] for most mobile enterprise apps.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
we do it for years. we evaluated many of those frameworks, xamarin was one of them. dumped it. never looked back.
|
|
|
|
|
That"s perhaps the problem. You tested Xamarin in the time and
Quote: never looked back.
So you todays opinion is from yesterday ...
I'm using it in my every day buisiness and see the positif evolution and all the possibilities. For me, if you are from the .Net area, it's the best bay to work on Android and iOS.
|
|
|
|
|
Our last evaluation was in Q3/2019 - so it's not more than six months old. and it couldn't even closely fit our needs.
|
|
|
|
|
Mike Barthold wrote: I prefer native solutions over those one-for-all frameworks.
I use Xamarin to build native Android (only) apps. Xamarin gives me the benefit of being able to use C#/.NET and leverage lots of well-tested and stable C# code (business logic) that's been in production for about ten years. Thus far, I've had no issues with it. If I had, I would have had to rewrite and rewrite my C# code in Java and maintain 2 code bases.
/ravi
|
|
|
|
|
Always need a web presence. Why do it twice? Why not html/hybrid?
|
|
|
|
|
Our first version of the app was in fact a hybrid developed using HTML / Javascript using Telerik Platform. This worked well enough but never really felt like an app. It always looked, behaved and felt like a web app running on the phone (which is essentially what it was).
After Telerik retired their Platform we were forced to re-develop our app. We looked at many different frameworks. The only one that met our requirements and played nicely with our existing technology stack, as well as giving us an app that looked, behaved and felt like an actual app, was Xamarin.
We have now released two versions of the app into the stores and are working on the next release. Xamarin is a great framework for building apps.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
gstolarov wrote: Always need a web presence.
That's not true. I work on an (Android) app that connects to the web but can also work disconnected. In fact, that's one of its major benefits.
/ravi
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
