I still hear debates on which way to go. I can imagine a scenario where you might need to build your custom control or even controls suite. And if application screen mockups are created, approved and promised without a development/coding team, the custom control scenario chances go higher. That usually ends up in more expensive products.
In case your business is not selling controls, they are tools to solve the problem and the problem to be solved. And probably it’s better to take a step back and check how existing tools can solve one’s business problem in an application.
The final product most likely is going to end up being more reliable, powerful and less expensive when the existing library is used.
I think picking that one control library should go after the main idea of the application and its core functionality, but before describing detailed functionality, look and feel of your application.
This should reduce the risk of developers burning time on customizing ready-to-use controls versus using those controls to solve a business problem.
For the last few years, I’ve been having a good time with Kendo UI for Angular controls.
I picked Grid as an example. It is a powerful control that is needed in most applications.
We need node.js and @angular/cli to start Angular app. If you never started an Angular app, the style guide is probably the best place to go.
I created youtube playlist. You can watch the whole thing or go to the piece below you’re interested in.
We’ll ng new kendo-grid application & serve it with ng s -o. Click here to watch the video
Clear some markup, ng add @progress/kendo-angular-grid video
Kendo UI for Angular grid filtering, paging, sorting video
Angular checks types in templates strictly, compiler reports errors; errors fix video
Add Angular feature module, generate component in it, move grid inside that component video
Reinventing a wheel is expensive. Your great app idea comes first; second, decide on the library of controls (Kendo is a good one :)) and other tooling; third, promise screen mocks with specific behavior, look and feel to your customers. It is going to result in faster, smoother delivery of the product video