ComponentOne Studio, from software company GrapeCity in Pittsburgh, Pennsylvania, provides Visual Studio controls.
$1,495
Per Year Per User
Progress Kendo UI
Score 8.0 out of 10
N/A
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
Pricing
ComponentOne
Progress Kendo UI
Editions & Modules
Enterprise
$1,495.00
Per Year Per User
Kendo UI with Priority Support
$999
per developer, royalty-free
DevCraft UI
$1,299
per developer, royalty-free
DevCraft Complete
$1,499
per developer, royalty-free
DevCraft Ultimate
$2,199
per developer, royalty-free
Offerings
Pricing Offerings
ComponentOne
Progress Kendo UI
Free Trial
No
Yes
Free/Freemium Version
No
No
Premium Consulting/Integration Services
No
Yes
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
—
More Pricing Information
Community Pulse
ComponentOne
Progress Kendo UI
Considered Both Products
ComponentOne
No answer on this topic
Progress Kendo UI
Verified User
Professional
Chose Progress Kendo UI
Kendo UI and the Telerik suite covered more of the technologies and platforms that we were working in (i.e. WinForms, MVC).
Senior Analyst, Business Data and Systems - Research and Innovation
Chose Progress Kendo UI
At the time of our product selection we identified better cross-browser compatibility and we estimated that turnaround for support was superior. At the time, the vendor had a higher positive feedback footprint among their user community.
We have tried Component One's stuff as well as jQuery UI. Component One is good for their grids, but it is easy to get behind with them. jQuery UI just looks stodgy. We also looked at EXT for a bit, but it was too proprietary.
I have worked with Angular Material and Bootstrap …
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 …
C1 is great for creating custom reports. We have client apps where we've created some fairly complicated reports such as invoices and real estate inspections. We also use the True DBGrid in many of our apps since it is so customizable. Its grouping and filtering features are very nice and can provide summary counts and totals at the bottom or right side of the grid that are very handy.
It allows us to extend the components or create new components in an easy way. The control suite is complete and powerful enough that you do not need to consider other competing packages. The controls are relatively easy to implement and when we ran into problems the documentation and online support were very reliable.
The True DBGrid control is nice for showing parent/child relationships and being able to drill down and show the child data. It also is nice for showing summary totals.
The report engine is great for building custom reports for Win Forms or web apps. It can do everything that Crystal Reports can do.
They have a good selection of controls that can do just about anything you can imagine.
Kendo UI controls provides rich set of features and capability that is required for enterprise products.
Performance of controls are satisfactory overall though few other vendors provides extraordinary performance for specific controls and for specific purpose. Kendo UI provides most of the required controls and with rich feature that made us to select Kendo UI controls for our development.
Kendo UI controls quality, in terms of performance, robustness and well defined interfaces are very positive notes.
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.
Nothing better has come along. I'm always on the lookout for new UI libraries and I have tried most of them. Kendo has done a good job of keeping my business. They aren't perfect, but no one has done it better as far as I can tell. I'll keep a look out and my rating may change in the future if they get complacent.
it's easy to implement in applications. The kendo widgets are able to be used in almost any type of business application which has a UI. For most part, once the developer has completed a project which uses Kendo, many time code can be copy/paste into a new application. Kendo UI documentation keeps improving so finding the answers to questions can be easy
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.
it took me about one day to make the components available for all the team members, including a quick demo, parallel setup in everyone’s workstation and packages deployment into our nuget server after 3 days of one to one support, everyone was able to use the components or find help in the documentation or resuest support
We have been in business since 1992, so we have used many different products over the years. The two other products we've primary used that are similar to ComponentOne, are Infragistics and Crystal Reports. Infragistics has a vast array of controls similar to ComponentOne. We use both to be honest and I'm not sure which one I would pick over the other. I guess that would depend on what you're trying to accomplish and if one had some control or capability that the other didn't. ComponentOne does have the reporting capabilities, where Infragistics does not.
At the time of our product selection we identified better cross-browser compatibility and we estimated that turnaround for support was superior. At the time, the vendor had a higher positive feedback footprint among their user community.
ComponentOne allows us to add additional features to our apps that wouldn't be found in apps written with just Visual Studio itself. That allows our clients to get more creative in their requirements, which in turn, means more work and billable hours for us!
Our apps appear more professional when using ComponentOne which helps us get projects for new clients.
ComponentOne also helps us to save clients some money since we are not having to develop things that it can do from scratch.
Kendo UI has saved us a ton of time in development.
We were able to get certain things to market faster due to the fact that we didn't have to piece multiple libraries together like is so common with modern web development.
Because of the price of the library, however, we have not been able to purchase upgrades every year.