Kendo UI React in an industrial on premise web application
Updated October 14, 2020

Kendo UI React in an industrial on premise web application

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

Overall Satisfaction with Progress Kendo UI

We use Kendo UI components within our industrial product's web interface. It is a part of our core product and is used by all customers. Consequently, it is important that it performs well and is bug free. We migrated to Kendo after updating our technology stack to React and needing a new control library as a result.
  • Large component library
  • Written natively in React
  • Great documentation
  • Support system is not very good. We had a few issues with our components which we traced back to flaws in the product.
  • Performance of the grid component could have been a bit better.
  • Style and customization is doable, but not the easiest.
  • We needed a new control library, and successfully migrated from our old library to kendo. It works and our customers are still happy. ROI is more or less the same as it was before...
We liked Kendo because it was natively written in React and well documented. Also, it has a large selection of UI controls which gave us confidence that it would have everything we needed.
There are a lot of controls that we actually ended up not needing. I think Kendo is ideally suited for web applications that have a more broad customer base and a more typical browser profile (large mobile base, and a good mix of different browser types and screen sizes).

Using Progress Kendo UI

1 - Kendo is primarily used by our Front End software developers. We purchased it for a product, which as since entered "legacy" status, so only a single developer maintains it.
1 - Kendo is used only by software developers on our front end team.
  • Customers interacting with our product for numerous functions of our GUI
  • Support agents using our product to extract information about the customer's installation
  • Developers need to be able to test the system internally, and debug it when problems are found.
  • Their grid system is very powerful. It has allowed us to add functionality such as sorting and filtering to our product which was not planned.
  • Kendo makes it easy to style their UI components. This allowed us to implement a theme system, for users to chose "Light" or "dark"
  • We are evaluating Kendo as the component library in our next-gen product.
  • Progress offers other UI libraries, not just for React, that we may use (for instance with our .NET/WPF applications)
Since we are using Kendo on a legacy product, there is likely a time when we will no longer support it. We are evaluating Kendo for our future product, in which case we may continue to use Kendo for an extended period of time.