yes you Kendo
Updated October 19, 2020
yes you Kendo
Score 9 out of 10
Vetted Review
Verified User
Overall Satisfaction with Progress Kendo UI
We use kendo UI components in our internet banking solution, in an ASP.NET MVC based architecture.
the choice has been made by the it department, and the dev team integrated it
these components are very useful for complex ux (like grid hierarchy) or for its rich built in features (that we don’t have to redevelop or to encapsulate in a custom framework)
the choice has been made by the it department, and the dev team integrated it
these components are very useful for complex ux (like grid hierarchy) or for its rich built in features (that we don’t have to redevelop or to encapsulate in a custom framework)
Pros
- Very easy ajaxified hierarchical data grid with pdf/excel exports
- Easily skinnable ajaxified components
- The kendo UI has been very easily integrated into our nuget local server
- Very responsive support through tickets
- frequent software updates
Cons
- kendo UI should be at the same level as ASP.NET AJAX components (number of components, AJAX)
- ROI : we spared a lot of time implementing advanced scenarii that are built in the components (hierarchical grid, exports, ajax)
- advanced components capabilities can inspire new ux/ui features in your product
- Infragistics Ignite UI
Telerik support beats'em all
we tried both a while ago, many things led us to prefer telerik / kendo ui, and the quality of the components added to the support reactivityans the quality of the software documentation (and also the rythm of updates and releases) made us keep working with telerik ui components.
we tried both a while ago, many things led us to prefer telerik / kendo ui, and the quality of the components added to the support reactivityans the quality of the software documentation (and also the rythm of updates and releases) made us keep working with telerik ui components.
Do you think Progress Kendo UI delivers good value for the price?
Yes
Are you happy with Progress Kendo UI's feature set?
Yes
Did Progress Kendo UI live up to sales and marketing promises?
Yes
Did implementation of Progress Kendo UI go as expected?
Yes
Would you buy Progress Kendo UI again?
Yes
Using Progress Kendo UI
6 - the components are used by the development team, that includes development engineers and ux ui designers
other teams are involved in the software lifecycle but don’t directly use the components or interact with the support
some business analysts sometimes take a look at the telerik website, in order to find some design / ux ui ideas
other teams are involved in the software lifecycle but don’t directly use the components or interact with the support
some business analysts sometimes take a look at the telerik website, in order to find some design / ux ui ideas
1 - Every member of our development team is used to go to kendo website and find support and solutions for every requirement or any problem he could find during the development process.
the senior tech lead of the team has many years of experience with kendo and so gives quick support for bginners, hints and makes the architectural decisions for the team
the senior tech lead of the team has many years of experience with kendo and so gives quick support for bginners, hints and makes the architectural decisions for the team
- new software development
- time to market improvement
- software quality improvement
- kendo packages in our inhouse nuget server
- make kendo updates easier in a devops environment (with azure devops server)
- prepare tech transition to react framework
- widget based screens
- documents processing softwares developed instead of purchased
- chatbot ui
Evaluating Progress Kendo UI and Competitors
- Price
- Product Features
- Product Usability
- Prior Experience with the Product
most important factor : my knowledge of the product
I know quite well and since 2007 both the product and the vendor (I developed with it in another company that relied on telerik for all of its platform’s ui ux)
experienced it almost every year since
i knew it would be the best for my team now
I know quite well and since 2007 both the product and the vendor (I developed with it in another company that relied on telerik for all of its platform’s ui ux)
experienced it almost every year since
i knew it would be the best for my team now
i don’t think that i might change my evaluation because i know the product well and i tried it for years, enjoying the support and the product’s quality
without that knowledge i think i would compare the three major components vendors, paying great attention to the support and updates rythm - maybe i would make the same choice again
without that knowledge i think i would compare the three major components vendors, paying great attention to the support and updates rythm - maybe i would make the same choice again
Progress Kendo UI Implementation
- Implemented in-house
- Third-party professional services
we rely on a major local dev company, building a long term partnership
So we choosed a company that had previous experience with Keno ui components and that was able to reactively evolve with kendo updates, while giving added value based on kendo components.
we made our choice 3 years ago, among 4 major it companies
So we choosed a company that had previous experience with Keno ui components and that was able to reactively evolve with kendo updates, while giving added value based on kendo components.
we made our choice 3 years ago, among 4 major it companies
Yes - the first pahe was basically a smooth knowledge transfer phase :
most of kendo based devs were done by our engineers, with our partner standing by
then in a second phase, our partner gradually took in charge component devs, until having full control on our solution, mastering both previous developments and kendo’s last release and capabilities
most of kendo based devs were done by our engineers, with our partner standing by
then in a second phase, our partner gradually took in charge component devs, until having full control on our solution, mastering both previous developments and kendo’s last release and capabilities
Change management was a small part of the implementation and was well-handled - you have to show the benefits of the new components to the dev team, so that they understand what advantages they can find in using it
then you can set the change as a kind of challenge for the team, or an achievement they have to reach
after that, you can make a collegial review after 3 or 6 months so that every member of the team keeps involved
then you can set the change as a kind of challenge for the team, or an achievement they have to reach
after that, you can make a collegial review after 3 or 6 months so that every member of the team keeps involved
- making dev team familiar with new components capabilities
- making dev team aware of kendo support (vendor support instead of stackoverflow)
Progress Kendo UI Support
| Pros | Cons |
|---|---|
Quick Resolution Good followup Knowledgeable team Problems get solved Kept well informed No escalation required Immediate help available Support understands my problem Support cares about my success Quick Initial Response | None |
Yes - Even though the support takes a very little time to answer 24 hours with a normal licence)
premium support gives us the possibility to get priority answers within a few hours (4 hours i think) and remote screen sharing assistance, that has been very useful for specific scenarios that are hard to describe
premium support gives us the possibility to get priority answers within a few hours (4 hours i think) and remote screen sharing assistance, that has been very useful for specific scenarios that are hard to describe
we once were in a very difficult rush time before a major release. we had a very specific and hard to develop scenario to implement with almost no time to do it. we were expecting a panic overnight development rush to solve the problem. we sent a support ticket before even trying to find a solution. even though he noticed that, and after we explained our desperate situation, the support engineer kindly gave us very useful help (that really wasn’t part of his support job) and saved us from last minute crashes
Using Progress Kendo UI
| Pros | Cons |
|---|---|
Like to use Relatively simple Easy to use Well integrated Consistent Convenient Feel confident using Familiar | None |
- components capabilities integration
- getting support
- components skinning
- very specific complex component behavior implementation
Comments
Please log in to join the conversation