Look at the emerging WASM projects such as Blazor or Ooui. The obvious path seems to be to have a strong HTML based suite, i.e Kendo, ported to Blazor. However another option would be to improve the Xamarin forms components to have comparable functionality to their desktop counterpartys so they can be used in LOB applications under Ooui. The current Xamarin components are too mobile centric. A third option, which admittedly seems like a bit of a long shot at present, would be to take Moonlight, strip out the plugin stuff, strip out all but the layout code, and redo that to write to an HTML Canvas. Now that's probably outside your scope although in my opinion its the most attractive of the 3 options. In summary I suggest you look at providing a full featured UI component suite that runs under wasm.
WASM is best thing that has happened in last years for .net developers. Pleaso do both and create enterprise components that can be used in Blazor grid/table,charts, etc and also for xamarin.forms ooui.
Maybe you can start with blazor wrappers for current js components and then move to rewrite in wasm for better performance.
We'd prefer Telerik controls in a XAML based framework, but Blazor is a great step in that direction.
The ideal thing for companies that develop Desktop applications is to use Ooui with Xamarin Forms and third party companies to develop their controls (Grids, Ribbons, etc.) for Xamarin Forms and that these user interfaces can run in a browser (WASM and Ooui).
Ivan Danchev commented
Thank you for logging this feature request. We will investigate the possibilities for integrating our products with WASM.
+3 add Blazor UI components