3 ms·
"I've made stuff in Xamarin before, and it was a pretty smooth experience, except for needing to have separate UI code for each platform." That's what you SHOU
by st3v3r 11y ago
"I've made stuff in Xamarin before, and it was a pretty smooth experience, except for needing to have separate UI code for each platform."
That's what you SHOULD be doing. Trying to force the same UI on platforms with different paradigms and look and feel is a recipe for a shitty, shitty app.
- cableshaft 11y agoIt's not the same UI with React Native. It conforms to Native expectations (more or less) with each platform. It just wraps both of them in the same component name, and you can have separate files if you need to specify a parameter unique to a platform. So you still have platform specific code, it's just RN's approach gets you a lot closer with the same code.
- r2_au 11y agoThat's what Xamarin.Forms (https://www.xamarin.com/forms https://www.xamarin.com/forms) does, for iOS, Android and UWP (desktop, mobile, xbox). My preference is still to go the native UI route though. If you take an MVVM approach, you'll naturally keep the logic in the shared code - the models and viewmodels - and you then can build views specifically for each platform and bind them on.