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 10.0 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
I did not experience the other product that has such an integrated and user-friendly feature. It works more like an everyday query with the UI element in a totally aesthetic and attractive view. With the Kendo library, we don't need to develop every UI component from the …
We currently use data tables in most of our applications that require a grid to be able to asynchronously perform CRUD operations on our web applications. It has served us well but Kendo UI has more widgets and better documentation to get the job done. Given the time, we would …
We wanted to use software which is easy to learn and implement for UI. we did some research and used few controls and we found that we can go with kendo UI. Look and feel wise Kendo fits perfectly. so we decided to use it through out the product. it is good software in …
The Kendo UI controls are more professional in appearance, better documented and simpler to integrate into our software applications. It takes us less time to implement the Kendo UI controls in our projects than comparable offerings from other vendors or open-source …
We honestly didn't look at very many others, we asked other people who work on similar tasks in the area and made our selection based off of their recommendations of Telerik and our experience using the open-source components for a trial. When Telerik/Kendo got the job done …
When we purchased Kendo UI, it was Telerik, and it was much further ahead at that time than Syncfusion was. This is the main reason we opted for Kendo. The controls also looked much more polished that Syncfusion's controls did at that time--and they still do, in the current …
Kendo UI is superior to Infragistics Ignite UI. Kendo UI elements are more reliable and compatible. Kendo UI provide more features and is easier to implement
Other products were not evaluated because Kendo UI was established as a solid option and we already leveraged UI for Ajax and UI for Winforms controls. I have experience with dojo/dijit, YUI, and jQuery controls but all are substantially more primitive that Kendo and related …
Kendo is easy to set up and upgrade. It is easy to use for developers and we can make attractive UI, so it automatically increases business. Kendo UI provides more control on UI fields as it has various properties associated with it. We can use the mask property for accepting …
Kendo is more configurable. It has a great support base and community. It's well suited to integrate with ASP.NET MVC. It's well suited to integrate with AngularJS. You can create generic and dynamic controls which are configurable. With grids it provides higher …
While the more expensive to use for a small shop(for example syncfusion is free to start), the quality paid for itself in no time flat. Other options are either half baked, have lock in and will become quite expensive once you hit a treshhold, or plain simply didn't mesh with …
The Telerik controls were just easier for us to use and implement. Our evaluation of control packages was over 9 years ago, so it is hard to recall the major differences. Generally, the team preferred what Telerik had to offer, particularly the fact that the bundle provided …
Progress Telerik UI provides a large amount of language support, demos, and documentation. While the competition is still great in their own right, Progress Telerik UI has provided enough resources to cover a number of current and future projects without having to expand to …
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.
Progress Telerik UI is the most complete multi-framework/platform in existence. Without it, you will find yourself having to traverse half a dozen other component providers each with varying degrees of license requirements and update schedules. Sure you might find a single …
I purchased Telerik because its components seemed great and were priced more attractively than Syncfusion. Unfortunately, after hitting major product limitations with Telerik's Document Processing for PDF I now find myself migrating from Telerik to Syncfusion. This has been an …
Telerik Support (pre-progress) is awesome, way better than Infragistics or Syncfusion. Syncfusion is a little cheaper. They all have Grid components (like Excel) then there are a few edge cases of having different controls to another to show off. Once you know what UI tech you …
[Progress Telerik UI] had a specific set of controls that were suited directly to our application space. Telerik also provided a Xamarin solution for very similar pricing, which should allow us to speed up our app development.
Progress Telerik UI ultimately had the smoothest/lowest learning curve for developers and it's an established product that incoming team members likely have some experience with.
The existing Microsoft technologies already support many of the controls provided by Progress Telerik UI and may be used as an alternative, of course. They will not have the full-featured functionality you will find in Progress Telerik UI but are available. There are also other …
Using Progress Telerik UI on the front end and Spring on the back end, you can focus on your business logic in the middle. There is no need to reinvent the wheel. This allows you to focus on what's under the hood. These have both been a pleasure to work with.
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 …
We have not used any other product for UI. We are using Telerik from start and continuing using it. Features offered by Telerik are sufficient for our product and we are fully utilizing all features provided by Telerik. Performance of all UI controls are great so over all …
Super easy to use and integrate into Visual Studio. The MVC helpers greatly simplify development. The controls are easy to implement and the online examples are excellent.
I am much more pleased with what we've gotten from Telerik UI in terms of controls and ease of use. The controls have great functionality and were easy to integrate into what we are wanting to accomplish. DevExpress never wowed us and that's why we went with Progress and have …
Thanks to the functionalities contained in Telerik tools we are able to create complex interfaces and satisfy the requests of our customers. Especially for increasingly frequent requests to use applications on mobile devices. With Telerik we have been able to solve many …
Kendo UI works well if developing web UI applications which have simple layout designs. - Good A scenario where there are a lot of Kendo widgets on a single UI page, and each has a complex initialization. - Not so good
Progress Telerik UI is one of the best web design and development solutions for Dot Net based applications. It has extensible support for ASP.NET Core, C#, WCF, and ASP.NET WebForms. It overall improves the design structure for the applications and provides multiple customization options to meet the requirements of clients and end-users.
Kendo Grid for presenting a timeline of research grants as they are being approved. Our users love the ability to export the data to various mime formats.
Kendo Scheduler for presenting the upcoming calendar events in the available conference rooms in a building. This is used together with a 3rd party vendor API for appointment booking.
Kendo Treeview is used to present a hierarchy of topics that our users can navigate through easily.
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.
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.
The Telerik UI has become part of our staple development tools. We can not be as productive without the feature set available to us in the Telerik UI ASP.NET AJAX control package.
My initial score would be 10, but I am aware of the high price for its implementation. Therefore, I would recommend it only in large projects where a large profit margin can be obtained. But in general, I recommend it. I am currently using it without problems.
The UX of their UI is very well thought out, the micro-interactions are intuitive - thus great for your end user as less training is needed. Using the software, there [are] loads to get you going, you can download their whole demo site and see how each demo works. There is more now on github to get you started, also much on an awesome CDN that's well bedded in so your app is speedy and up to date.
Overall, we are satisfied with the support offered by the Progress Kendo UI team. We had raised few helpline incidents in the past and they have been resolved timely by the team. Also, we were satisfied with the level of information and support provided by the team.
Progress Telerik UI customer support is pretty good. The ticketing system allows a thread of questions, answers, and attachments of code and screenshots. Response time is fairly quick and often has code snippets or pointers to online examples that could be relevant. There is a large amount of community support forums to get answers or post questions. In addition there is a forum of posted code samples for the various controls. The Progress update tool easily tells you what products have been updated and allows you to install the updates on your development system. Release notes can be displayed to see what's new.
I think the main thing is to get into a Kendo mindset. Components that I've used in the past had a much different mindset and I think it got in my way. Sometimes I would use something different if I felt that the Kendo component was being too obstinate. I would go back later and replace that with the Kendo component when I had time to work with it further.
I did not experience the other product that has such an integrated and user-friendly feature. It works more like an everyday query with the UI element in a totally aesthetic and attractive view. With the Kendo library, we don't need to develop every UI component from the beginning. It was one of the faster development of applications.
The Telerik controls were just easier for us to use and implement. Our evaluation of control packages was over 9 years ago, so it is hard to recall the major differences. Generally, the team preferred what Telerik had to offer, particularly the fact that the bundle provided controls, not just for the ASP.NET context, but also Windows applications, and the cross-platform contexts as well.
Positive impact is that it helps development team to focus on business logic rather than developing UI control and that resulted in good productivity savings. productivity saving is significant (like 30% of product development cost).
Provides rapid development - it has helped me create multiple web applications in MVC and Angular within a one-month time frame.
Our clients were facing challenges (taking time to load applications, grid view, and generating reports ) with asp.net web applications. Using Kendo UI we have migrated the ASP.NET application to MVC within a one-month time frame. The client was very happy with the application's performance and responsive UI.