41–50 of 124 posts
Despite explaining that XP stands for "cross platform", I still think that this is mis-named and many will assume it relates to one of Microsoft's biggest ever brand names with global recognition. At first glance I decided not to read the article because I thought it irrelevant due to the XP.
Earlier quoted context omitted.
How do you use React Native on the web?
There are several React Native web players. One is used in their documentation site.
>With React and React Native, your web app can share most its logic with your iOS and Android apps, but the view layer needs to be implemented separately for each platform. As far as I understand, you don't need to do this in react-native. Only when you want to use some special features. Or am I missing something?
Yes, it's not possible. You can't just use your React code as React Native. There are many small API differences.
I'm not sure I want to switch to ReactXP. I really like being able to use the React Native Animated API on the web, and I can also use wrapper libraries such as react-native-animatable.
Right now we're considering using .NET and ReoGrid, since Qt is too expensive and we only target Windows anyways.
Earlier quoted context omitted.
Does Xamarian provide desktop widgets?
There is Xamarin.Forms, which is essentially cross platform XAML with a base set of widgets. It supports Android, iOS, UWP, and they are working on MacOS. No Linux yet.
I really want React for desktop apps. Currently we are running into some performance issues with large datasets and spreadsheets, and being able to offer a performant desktop app would be ideal. Right now we're considering using .NET and ReoGrid, since Qt is too expensive and we only target Windows anyways.
I think you should consider moving away from JS, it will probably save you from future problems.
>With React and React Native, your web app can share most its logic with your iOS and Android apps, but the view layer needs to be implemented separately for each platform. As far as I understand, you don't need to do this in react-native. Only when you want to use some special features. Or am I missing something?
But as we move further, we'll be looking into making the versions for both platform feel truly native, and that will require some changes to navigation components and the overall navigation paradigm (tabs vs. drawer, screens vs. cards etc.).
The platform differences are as much about design as about code, and I don't see how you can escape that work with any cross-platform framework. But React Native makes it very easy to implement in a way that lets us share all but a few components.
I really want React for desktop apps. Currently we are running into some performance issues with large datasets and spreadsheets, and being able to offer a performant desktop app would be ideal. Right now we're considering using .NET and ReoGrid, since Qt is too expensive and we only target Windows anyways.