Saves time, money and makes me look good.
September 06, 2018

Saves time, money and makes me look good.

Anonymous | TrustRadius Reviewer
Score 9 out of 10
Vetted Review
Verified User

Overall Satisfaction with Kendo UI

We use Kendo UI across a broad range of product teams within the Americas business.

It's niche in our development stack is related to reusable components that dev teams can leverage to reduce development time and allow them to focus more time on business outcomes. We spend less time reinventing the wheel on each project with a standardized component library.
  • Consistent look, feel and quality across development UI components
  • A huge amount of components that can be leveraged in different ways for building applications
  • Continuous enhancement and product roadmap
  • Full customization of UI is sometimes difficult
  • Our design team occasionally resists "cookie cutter" components and wants to build something more unique and custom
  • Need more rapid and expansive SPA options
  • Reduced developer time
  • Reduced bugs
  • Faster delivery to our business
I'll be honest, we never really did a "bake off" when evaluating UI components. I think initially we had a need for a solution and at the time Kendo UI was a good fit. Once we got it in house it grew organically as projects were developed and delivered. So not sure if there is a huge side by side comparison that I can provide in that context.
If you are building line of business applications for internal use, this is a no brainer as it allows a lot of time saving and cost reduction in the long run.

If your end use cases/scenarios require ultimate flexibility and custom ui experiences - you may want to avoid standard libraries such as Kendo UI. But that isn't necessarily a knock against Kendo - you'd have the same issue with any component library.