The most useful feature of Kendo, in my opinion, is the combination of the DataSource and the frontend components. Using a DataSource with CRUD enables a rich user interface with strong built-in capabilities. For example, with a grid you get all the essential features (create, update, delete), and then with only a few modifications you can add extra options such as Excel or PDF export, pagination, filtering, and more, without additional development costs.
It helps me deliver multiple features in a short period of time. If I had to build the user interface manually, it would take much longer. Review collected by and hosted on G2.com.
The main downside is the error messages and logs. Sometimes, when we implement a feature, an error appears, but the message itself isn’t clear and doesn’t explain what it really means. It also doesn’t point to our own file; instead, it references a file inside the library with thousands of lines. Without more detailed information, it’s very hard to trace the exact issue. Review collected by and hosted on G2.com.







