Why not to use exisitng library ?

[Kebechet]

Describe the bug
This is more of a concern. Why do you try to recreate a component library from scratch ? Why not to use some open-source variant ? like MudBlazor and if needed just customize the design or do some abstraction layer between ?

[codymullins]

This is a fair question! There are several open source libraries available for Blazor, this is true. For most projects, these libraries will work perfectly fine.

We have some unique needs and really want to dig in on performance to make sure our end users have the best experience possible. For example, our page builder is going to support dragging and dropping components for an entire page, which could have tons of state and lots of renderings being triggered. We want to make sure our components work the absolute best they can, so our non-technical end-users have a really delightful experience.

With that said, we plan to allow our customers to use any component library they want, which will likely require some support from third party component library maintainers as well as some legwork on our end. In order to ship fast, though, we are only focusing on first party components for now.

[Kebechet]

Interesting take but wouldn't be more time efficient to choose one of those other libraries (maybe some of them are really performant as well) and in case there are performance downsides just to contribute with a PR to improve them ?