Kendo UI Helps Us Work Easier
May 30, 2018

Kendo UI Helps Us Work Easier

Alan Hurt | TrustRadius Reviewer
Score 10 out of 10
Vetted Review
Verified User

Overall Satisfaction with Kendo UI

Noblis has a team that supports government acquisitions and provides a comprehensive web-based collaboration and documentation tool tailored to support any acquisition. Kendo UI helped us build the software to allow collaboration, track workflow and securely manage massive amounts of documentation while also allowing us to quickly develop new 'on-demand' solutions that typically arise from each individual acquisition process. Without Kendo UI, we would have had to spend countless hours creating our own tools or trying to patch together disparate components into a cohesive framework.
  • Like many developers, we rely heavily on grids to display data. One of the real strengths of Kendo UI is the grid component. It provides immense flexibility and allows us to quickly and easily provide almost any kind of requested data view.
  • Recently, Kendo UI has expanded from being strictly jQuery based to include an Angular, React or Vue based version. By embracing this, we now have more options for developing software and are better able to utilize developer skills. Did I mention these versions are all free with the Kendo UI pro license? Definitely, a great thing not to have to hassle with licensing.
  • Kendo UI has over 70 components with a rich API set. The documentation for all of this, from API properties and methods to component overviews to 'how to use' examples is a truly great resource. In addition, there are now 'Getting Started' videos for all flavors of Kendo UI. All of this has made bringing new developers into the mix fairly easy as they have a huge ecosystem from which to learn Kendo UI.
  • Kendo UI is always moving forward and staying current with latest development trends. While that is beneficial, that can cause some issues when supporting customers (particularly government) that don't move their IT infrastructure along nearly as fast. A prime example is web font icons. Great and easy to use, but where Kendo UI utilizes web font icons as the sole means of displaying an icon, not all organizations (again, especially government) allow the use of these. There have been times where Kendo UI became unusable and we had to downgrade to a version a few years old. Makes continued payment for licenses sometimes feel wasted as we may not be able to always use the new releases
  • Kendo UI has a wonderful feedback system and they do indeed listen to the community. However, there do seem to be some instances where there is large support for a new feature/component and it never gets addressed. It is easy to understand that not all ideas are easy or even prudent to implement, but would be nice to see a better follow-up on ideas with a current status
  • Refreshing Kendo UI grids is simple, yet the standard API method causes the grid to return to the default state. We have many use cases where we would love to update the grid data but need current grid state (such as expanded detail rows, sorts, filters, etc) preserved after the grid is updated so that users do not have to perform grid actions again to return to the desired state.
  • The core product we use to support government acquisitions is built with Kendo UI and this has been the primary reason we have been able to create several 'spin-off' projects, such as a grant management application and technical document libraries, with minimal effort. This new lines of business have been created due to the ease of use when developing with Kendo UI
  • Kendo UI has allowed to greatly speed up development. By utilizing the same framework across multiple projects, we can spend more time on requirements and requested features and less time on developing the same UI components repeatedly. In terms of numbers, we have been able to prototype new features in days rather than needing an entire sprint. This is very valuable to our customers who are often requesting new functionality while they are actively using our acquisition tools and speed is of importance.
Kendo UI is well suited for grid-based applications. Additionally, dashboards, scheduling, and content management are also excellent applications where Kendo UI shines. You can even do online spreadsheets via a component. Where we struggle with Kendo UI is scenarios where users update data that is displayed in the grid, but we cannot always keep the current grid state intact once the grid update has been performed.