3 ms·
«Beyond that everything else is either "shove html in a web view" or the xamarin approach which, and please correct me if I'm wrong, is closer to the approach o
by WorldMaker 11y ago
«Beyond that everything else is either "shove html in a web view" or the xamarin approach which, and please correct me if I'm wrong, is closer to the approach of QT in that it renders all its own controls.»
Xamarin uses native components, in a similar manner to react-native. (Or more accurately, the other way round, Xamarin pre-dating react-native.)
I also wish react-native or NativeScript would actually provide/finish Windows Mobile/UWP support, but I'm not currently holding my breath. (That said, at least Windows supports JS as a native build stack so maybe you don't really need react-native/NativeScript to support Windows, you just need some glue scripts...)
- BinaryIdiot 11y agoInteresting, thanks for the heads up! I was invited to their original Alpha (before they called it Xamarin) years ago and I could have sworn it did not work like that back then. So I'm assuming it's either changes or I'm mistaken.
- WorldMaker 11y agoSo far as I've followed Xamarin it has always been about native components, but they've not always been great with marketing that. The waters are also muddied a bit in that they have their Xamarin.Forms library now which is an abstraction layer over top of the native components (but at the end of the chain, still defers to the native components to actually do the work). It's easy to confuse Xamarin.Forms with a non-native toolkit, but it too is just a wrapper over top native tools.
- BinaryIdiot 11y agoFair enough. Thanks for the clarification!