5 ms·
Super news, but I think more and more people will go React Native way... Especially after React Native Mac OS X recent release!
by ddon 11y ago
Super news, but I think more and more people will go React Native way... Especially after React Native Mac OS X recent release!
- jbigelow76 11y agoProbably not C# (and to a lesser extent F#) enterprise .NET developers.
- st3v3r 11y agoNo, but I don't think that group was big into writing apps to begin with.
- tigershark 11y agoI was learning react native, after this I will try Xamarin. Much better to be able to use c# (that I use for work) than JavaScript.
- kayoone 11y agoNot so sure about that, for most Windows developers Xamarin will offer more benefits and it is extremely mature by now. React-Native is still pretty early on Android for example.
- nbevans 11y agoSeems unlikely. Xamarin supports F# and C# and is aligned 1:1 to the native platform.
- usea 11y agoAt my previous job, mobile projects were all done in xamarin (after like 2013/14 or so) and the developers who did those projects raved about it, often. If I were going to make a mobile app right now, I would definitely use it. However, I'm much more at home in C# than I am javascript. To each their own.
- cableshaft 11y agoI don't know. I've been spending some time learning React-Native, but it's in fits and starts. There are several things that trip me up. I've got the basics pretty much down now, but now I'm banging my head against local storage and wrapping my head around Redux in general. It is interesting, but time consuming. And I don't have much leisure time right now. 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. The language and syntax never got in the way, it was more just having to look up the corresponding UI elements (especially Android, where I have less experience) and get those working from time to time. As such, I could generally code like a fiend and get tons accomplished in a short period of time. That being said, I really, really like how most of the React Native code is the same, and it's quite possible I'll get to that point with React Native also.
- 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.
- miguelrochefort 11y agoIt seems like Microsoft will help you with that too. https://github.com/Microsoft/vscode-react-native https://github.com/Microsoft/vscode-react-native