4 ms·

> stuff like Xamarin Forms and abandoning it half-way through Eh? I've worked on projects using Xamarin Forms, and they turned out just fine. Yes, it would be

> stuff like Xamarin Forms and abandoning it half-way through Eh? I've worked on projects using Xamarin Forms, and they turned out just fine. Yes, it would be nice if there were a few more controls in the main Xamarin Forms library, but I don't see a problem with the community picking up some of the slack (which they have).

mikece 6y ago
"I've worked on projects using Xamarin Forms, and they turned out just fine." Same here, but it is my experience with Xamarin that has led me to conclude that it's the wrong choice almost 100% of the time. Sure, it can be made to work but at the end of the day you're coercing C# to do something it was not designed to do. For mobile I am convinced that PWA/hybrid mobile is the correct choice 95% of the time with the remaining 5% being platform native apps written in Android Studio with Kotline or Java (or Xcode with Swift or Obj-C). Anything else is just an exercise in sticking non-round pegs into a round hole.
- GordonS 6y ago
  > at the end of the day you're coercing C# to do something it was not designed to do Hmm, not sure I can agree with this statement, as I don't see what would make C# itself unsuitable here. > For mobile I am convinced that PWA/hybrid mobile is the correct choice 95% of the time But this I fully agree with :) While the Xamarin Forms projects I've worked on turned out well, I feel like the whole experience of developing, experimenting, building, debugging and testing would all have been so much easier with a PWA. A PWA would also make it much easier to build what your UI designer really wants, instead of having to compromise all the time with what is readily available - having CSS at your fingertips makes all the difference.