multiplatform always sounds like a good (especially to PHBs that think they can cut down on work and developers), but actual implementation is full of potholes and surprises...usually tooling is much weaker than apps done in native platform tools and you end up getting slowed down a lot...or you have these weird inconsistencies that make it really write once, test everywhere, fiddle on each platform to get it to work, add workarounds on each platform, etc. This has happened time and time again...Java, Xamarin, R/N, etc.... I take any new attempt w/ a big grain of salt 😉
09/07/2018, 1:44 AM
Don't you mean cross-platform instead of multi-platform? With the multi-platform approach native tools can be used.
09/07/2018, 10:24 AM
Yep but in this context, it's still K/N with crossplatform modules. You're introducing extra tooling and debugging issues...