Re:Flutter: the good, the bad and the ugly
by vibrato on Saturday November 24, 2018 @04:55AM
(#18521306)
This mirrors my experience working with Xamarin. You had to know both everything going on at the native level and the c# .net and Xamarin levels as well.
Re:Flutter: the good, the bad and the ugly
by pjmlp on Monday November 26, 2018 @12:41AM
(#18531356)
This is why I always advocate for platform languages on production code.
Too many hours spent in the past writing FFI code, tracking down bugs not knowing if they were on the platform or 3rd party language runtime, missing integration with platform tooling.
Naturally I don't always succeed at that.
I could be wrong here, but from what I understood the cost of maintaining a hybrid RN + fully-native apps > full-native apps. I.e. What airbnb would gain by not having to code both android/iOS was lost by having to deal with all the RN non-sense (third-party libraries being deprecated, very fast non-backward compatible changes, etc.) but also having to always bridge the gap between what was RN and what was truly-native. At the end of the day, you look at your time and you realize that you spend more time trying to make it work with RN to "save time" rather than just coding it on both platform.
But then, most people using RN don't have to deal with this issue because they don't have an existing non-RN code base to bridge with RN.