ASP.NET vs. Progress Kendo UI

Well suited: for interfaces between machines data and applications. Made as a service. For web applications in factories where you don't have access to thick clients due to the environment. not well suited: quick measurements and fast data transitions between different applications. When time dependency is needed, then you better can choose other solutions.

Incentivized

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.

Incentivized

• It has a great documentation so new or experienced, you appreciate quick access to quality information
• It’s very fast, uses less memory than initially expected that has decreased our costs after moving from python
• It speaks the language of the design patterns really well, so our backend apps are written fast together and connect to frontend systems flawlessly

Incentivized

• 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.

Incentivized

• Net is just like plug and play, we have to focus on a logic of code rest part can be handled by ASP. Net framework.
• It's a best for only web development.
• One downside with ASP.NET is its reliance on the .NET framework.

Incentivized

• 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.

Incentivized

It is the backbone of all our products

Incentivized

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.

Incentivized

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

Incentivized

The errors that we have detected were not of great importance and the online support provided a temporary solution until the next release.

Incentivized

Reports sometimes take a bit of time to load

Incentivized

Very good, depending on the requirement and budget.

Incentivized

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.

Incentivized

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

Incentivized

We choose ASP.NET because our core business is working with the SAP HANA database using SAP Business One. We can develop state-of-the-art applications with Razor and Visual Studio 2022 fast and with excellent application performance response. Working SAP Hana with JAVA could be more challenging because it has fewer developers communities, and it could be harder to find a solution for a question.

Incentivized

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.

Never faced a problem even when we threw a large amount of data at it

Incentivized

• We realized positive returns due to interns and new employees already having experience due to the free academic versions available.
• Being able to evaluate the express version prior to purchase was helpful.
• Performance is adequate, but not as responsive as C++. I guess the trade-off is ease of use and being able to find qualified personnel.

Incentivized

• 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.

Incentivized