Why create a custom plugin using kendo.ui.widget instead of, say, jQuery?

[Jon]

I was asked this question by coworkers, and wanted to check my thoughts with you all, and ask if you have any others.

One obvious answer is that if we're using Kendo UI components frequently, this has the advantage of making our own both consistent and familiar.

I think the most important answer, though, is that by doing so we'll have access to all the framework features of the kendo components, which your site lists as: "Datasource, Templates, MVVM, Effects, Drag and Drop, Validator, Globalization, Styling, Integration." Are all of those Kendo features in fact available to custom widgets that have extended kendo.ui.widget?

Any other thoughts about a good response/justification to the question?

Thanks in advance,

Jon

[Petyo]

Hello Jon,

(Disclaimer: this is a very subjective perspective as I am one of the framework developers)

Generally speaking, the framework level components can be used without the need of creating a custom widget. However, building on top of the kendo Widget may yield a consistent codebase and unified approach towards the UI layer of the application. 

Kind regards,
Petyo
the Telerik team