Hello Team;
I'd like to make a suggestion.

When one of the third party vendors became involved in producing Blazor components, they opted to wrap their existing 65+ JS components as "Blazor" components. At first, I though that's not as good as Native components that Telerik is doing.

But, as I then read more about their plan, they basically offered a full solutions from their JS library to developers, so we, the developers can start building a complete business application and as long as the vendor doesn't change the Wrapper API and only change the back end, their changes should work on the developer side.
Their idea was, to give us a jump start with JS and we start using counterpart Native Blazor components, and as as they become available, the components get changed to Native Blazor, and the apps written by us continue working.
I think this is a great strategy to have the full suite available to us from start to build apps than waiting for each Native component to be build.

My suggestion is to do the same, i.e. the word processing component where it is needed and we can build our app using the JS Word processor and by the time we are ready, Telerik might have the Word processor replaced by Native Blazor. This way we can build our apps with a full suite from the start than waiting for essential components to be built.

I hope the team would consider such strategy if possible.
Thanks!

..Ben