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…
Kendo UI gives you a flexibility and reliability worth investing in. Many of those "free" frameworks might change and may require extensive manipulation. Some frameworks like Xamarin are limited to development in a narrow choice platforms or can only build for IOS with a …
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.
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. …
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.
If you are required to develop applications that are cross-platformed, Xamarin is a great tool to use. It will help save time and effort from your development team to be able to build applications seamlessly for android, IOS, Windows, and web on a single platform instead of requiring multiple tools to get the job done.
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.
Xamarin allows you to write cross platform code. This allows companies to build apps more quickly by writing less code. Having code abstracted and reused across multiple platforms allows for more testing and less issues overall.
The ability to use Visual Studio is a huge plus. Visual Studio is one of the best IDE's available and being able to write cross platforms apps while in a great IDE makes everything less painful.
Xamarin is now free with a large company backing. This means that bugs on the platform get fixed more quickly and there is a large community of developers.
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.
Xamarin has been great for developing different projects efficiently and effectively. It's nice to reuse the core business logic across different platforms so that there are less to maintain and little replications are needed. The biggest benefit is that C# programmers do not have to learn a different language to do mobile development.
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
If you are required to develop applications that are cross-platformed, Xamarin is a great tool to use. It will help save time and efforts from your development team to be able to build applications seamlessly for android, IOS, windows, and web on a single platform instead of requiring multiple tools to get the job done
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.
I never had to contact support for any help. Most of the problems we ran into, we were able to identify and use peer support through blogs and other internet sources to resolve the problems. There are plenty of sources online which provide tutorials, discuss problems, etc. Example: StackOverflow
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
Just with any programming tasks, have a plan first. Design out the system, spend time to build it correctly the first time and have plenty of testing and user acceptance opportunities. Xamarin was easy to implement for a C# programmer. However, you need to do tutorials to realize the platform's capabilities.
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.
Xamarin runs natively on MacOS, and the debugger and other integration and auto-complete tools are far better than Eclipse for C# .NET. It also carries much of the plugin/add-on capabilities that are so desirable on Atom. Eclipse is a better for generalized software development, provided a developer is comfortable switching between the IDE the command line for certain parts of their workflow, like building, package management, or debugging. But for C# .NET development on MacOS specifically, Xamarin is the best product I've used for the job.
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.
