3 ms·

There are two sides of Xamarin. It builds native apps and you can use their native UI systems. So you can build a native Android UI and a native iOS UI next to

by andix 6y ago

There are two sides of Xamarin. It builds native apps and you can use their native UI systems. So you can build a native Android UI and a native iOS UI next to each other. This will give you perfectly native apps with the ability to share as much code as possible. The other side is Xamarin.Forms and its designated successor MAUI. Here you have the typical Microsoft UI problem. It is quite an unfinished framework. You can build everything with it, but if you do something else than the showcase app, you are going to have a difficult time. Xamarin is for sure not going to die soon.

Yuioup 6y ago
Xamarin.Forms isn't just unfinished. It's total garbage. Plus you can't share UI code between Android and iOS. You still need to build the UI's natively with no code reuse. Plus building and cross-compiling between Windows and Mac is hacky and painfully slow. I wish Microsoft would get rid of Xamarin. Every Visual Studio update has a bugfix for it, usually relating to iOS.
- eddhead 6y ago
  It's 100% UI code reuse between both platforms and MAUI takes it up to Mac and Windows. I've delivered several apps with more then hundred thousand users and the turnaround time for XF apps is generally 3-4x faster than native. You don't know what you're talking about clearly.
  - TrueGeek 6y ago
    Same. OP says "going to die soon" of a framework that's been around for 9 years and is being invested in heavily. I've been working on Xamarin projects for years and have done very well with it. Doing consulting I've done plenty of projects in React Native and played with Flutter a bit but Xamarin really is a great framework.
- miffy900 6y ago
  > Plus you can't share UI code between Android and iOS. You still need to build the UI's natively with no code reuse. Utterly false - Xamarin Forms is totally cross-platform UI; you're probably mistaking it for Xamarin Native, which is used as a target renderer for each platform. Look at this sample project: https://github.com/xamarin/xamarin-forms-samples/tree/master/TipCalc/TipCalc https://github.com/xamarin/xamarin-forms-samples/tree/master... The .iOS and .Android project folders target each platform respectively, with a single project shared between them that defines UI that is rendered onto each platform. You claim to have experience with using it, but obviously haven't done anything even as simple as a HelloWorld.

by andix 6y ago

Yuioup 6y ago

Xamarin.Forms isn't just unfinished. It's total garbage. Plus you can't share UI code between Android and iOS. You still need to build the UI's natively with no code reuse. Plus building and cross-compiling between Windows and Mac is hacky and painfully slow. I wish Microsoft would get rid of Xamarin. Every Visual Studio update has a bugfix for it, usually relating to iOS.

eddhead 6y ago
It's 100% UI code reuse between both platforms and MAUI takes it up to Mac and Windows. I've delivered several apps with more then hundred thousand users and the turnaround time for XF apps is generally 3-4x faster than native. You don't know what you're talking about clearly.
- TrueGeek 6y ago
  Same. OP says "going to die soon" of a framework that's been around for 9 years and is being invested in heavily. I've been working on Xamarin projects for years and have done very well with it. Doing consulting I've done plenty of projects in React Native and played with Flutter a bit but Xamarin really is a great framework.
miffy900 6y ago
> Plus you can't share UI code between Android and iOS. You still need to build the UI's natively with no code reuse. Utterly false - Xamarin Forms is totally cross-platform UI; you're probably mistaking it for Xamarin Native, which is used as a target renderer for each platform. Look at this sample project: https://github.com/xamarin/xamarin-forms-samples/tree/master/TipCalc/TipCalc https://github.com/xamarin/xamarin-forms-samples/tree/master... The .iOS and .Android project folders target each platform respectively, with a single project shared between them that defines UI that is rendered onto each platform. You claim to have experience with using it, but obviously haven't done anything even as simple as a HelloWorld.