Kendo UI is a JavaScript UI toolkit that allows users to build responsive web-based apps integrated into their framework of choice (jQuery, Angular, React, or Vue). The vendor’s value proposition is that Kendo UI offers a large library of popular and configurable components ranging from sophisticated grids and charts to basic buttons, so users don’t have to waste development time building their UI. The vendor also says the large library of customizable themes means users can easily deploy a…
$999
per developer, royalty-free
Progress Telerik
Score 9.3 out of 10
N/A
With Telerik UI libraries, Progress aims to equip .NET ninjas with a full arsenal of weapons, helping to create beautiful, modern and future-proof applications quickly and intuitively. The vendor states that with its over 1,250 UI components for all .NET platforms, as well as various themes, skins and customization options, Telerik users report cutting development time by up to 50 percent. Web
We selected Kendo UI because we were using Telerik controls already, and Kendo was included in our license. Other than that we have found the package mature enough to support our workflows which include some tricky scenarios: file upload, text editor, grids with grouping and …
Senior Software Developer - ALS Life Sciences Division | Environmental
Chose Progress Kendo UI
Actually, I did not try any other. When I arrived Kendo was already a standard tool in the organization. Outside of ALS, I've had contact with other web suits from Telerik and also from SyncFusion.
Telerik ASP.NET controls have a significant advantage over DevExpress -- automated web tests, rich API for testing web pages containing Telerik controls. Telerik also has less strict license terms: - Telerik software is licensed on a per-seat basis - DevExpress software is …
We have experienced working with Telerik UI tool set from 2002, KENDO UI born 2011 it has built 100% Javascript like a Telerik UI is a 100% Web Tool. Because this tool was born in 2002 before their competitors then Progress has a lot of experience around of this kind of tools. …
We used to use Component One but changed over to Telerik controls because they seemed to stay on top of the industry trends and the pricing was reasonable. The implementation was easy and the developers all voted for Telerik. We even used their reporting engine as well. The …
TelerikASP.NET Controls are still more feature rich than Kendo UI, so I prefer to use them wherever possible. Open source controls are used only for special scenarios.
One of our partner companies is using Kendo UI for jQuery. In order to exploit synergies with our partner we selected Telerik Kendo UI for jQuery. Other selection criterias were a) the longevity of Telerik, b) the Support, c) the Performance and d) the scalability.
Infragistics. We currently have an active license, but are using Kendo UI much more. The documentation and examples ultimately made the difference in deciding where to expend our efforts. There is only so much time in the day to spend trying to learn new products. We will put …
I felt that all three of these offerings were close, but Kendo seemed to be a little easier to work with inside our Node/Angular environment!
Verified User
Engineer
Chose Progress Kendo UI
We went with Kendo after evaluating the different options because Telerik has a good reputation in the .Net developer world, and the initial review showed that Kendo would be easier to use and look better with minimal effort on our part. In the end it came down to the fact …
Kendo UI stacks up greatly against other controls libraries like JQWidget and so on. It may be more expensive, but with what your getting from Kendo UI I can understand it (I still wish it was a little less expensive). But Kendo UI controls look and function better, and are …
We worked with Telerik since 2011. At first we used their controls for Silverlight and with time we continued using their tools like Kendo UI since we had positive experiences. In the beginning we took Telerik tools on a trial basis, and after a test period we liked their …
Verified User
Director
Chose Progress Kendo UI
No other. Before Kendo I used various open source jquery plugins and Telerik's Ajax platform. Telerik's Ajax was a component for old asp.net forms. Jquery was alternative which was better connected with ASP.NET MVC pattern. But none of this framework provides functionality like …
Directly at the begging of Telerik, we choose Telerik as our main component solution. When Telerik added Kendo to the family of their products we made a decision to słowy move out from ASP.NET Ajax to Kendo UI. After a long time, we see that it was a very good decision and we …
I think that this was case of luck - we downloaded Kendo UI stack and immediately after initial test that was it. No further chargeable components were used but we use some of free components coming through Bootstrap templates like Dropzone, Switch and few more. Overall we do …
Telerik UI for Blazor is much more usable than Kendo UI. I was never a fan of Kendo UI, but I like using Telerik UI For Blazor due to the ease of implementation for the components.
Verified User
Professional
Chose Progress Telerik
We have been implementing our own custom code using the ASP.NET framework, and it has taken us a lot longer to implement functionality. When we transitioned to using Progress Telerik UI components, it exponentially sped up our development time and improved the look of our …