Overview

jQuery UI

Stacks40.6K

Followers13.3K

Votes899

GitHub Stars11.3K

Forks5.3K

Kendo UI

Stacks297

Followers359

Votes33

GitHub Stars2.6K

Forks1.9K

Kendo UI vs jQuery UI: What are the differences?

Introduction

Kendo UI and jQuery UI are two popular JavaScript frameworks that help developers create rich and interactive web applications. While both frameworks provide a wide range of UI components and support for various functionalities, there are several key differences between them.

Architecture: Kendo UI is built on top of jQuery, which means that it leverages the functionality and performance optimizations provided by jQuery. This integration allows Kendo UI to have a smaller footprint and better performance compared to jQuery UI.
Commercial vs Open-Source: Kendo UI is a commercial framework developed by Telerik and requires a paid license for certain features and support. On the other hand, jQuery UI is an open-source project maintained by the jQuery Foundation and is freely available for use.
Component Variety: Kendo UI offers a wide range of pre-built UI components and widgets, including charts, grids, calendars, and more. jQuery UI, while also providing a set of UI components, has a more limited selection compared to Kendo UI.
Customization and Theming: Kendo UI provides a higher level of customization and theming options out of the box. It offers a variety of themes and allows developers to easily modify the appearance and behavior of components. In contrast, jQuery UI has a more basic theming system and limited customization options.
Mobile Support: Kendo UI is designed with mobile-friendly features and responsive design in mind. It offers a set of mobile UI components and provides seamless integration with popular mobile frameworks like Apache Cordova (PhoneGap). jQuery UI, while it can be used in mobile applications, does not have the same level of mobile-specific features and optimizations as Kendo UI.
Documentation and Support: Kendo UI has extensive documentation and a dedicated support team, providing resources and assistance to developers. It also offers official training and certification programs. jQuery UI, being an open-source project, has documentation and community support but may not have the same level of official support and resources as Kendo UI.

In summary, Kendo UI and jQuery UI have key differences in terms of architecture, commercial vs open-source nature, component variety, customization and theming options, mobile support, and documentation/support resources.

🔥 Trending in UI Components on StackShare

FigForm UI Components

FigForm

Try it View Docs Alternatives

Try

1

2

Advice on jQuery UI, Kendo UI

James

Lead Application Architect at TekPartners

Apr 13, 2022

Decided

Full disclosure; I worked for both Telerik and Infragistics in Developer Relations for these projects. From my point of view, neither is a clear "winner" in this space. Kendo has some nice features and Ignite doesn't have and vice versa. We ended up picking Kendo because we needed to settle on one of these, and most of our clients already owned Kendo because it came with some other Telerik product. That's it. It could have very easily gone the other way, but Telerik kinda won the ground war here, so...

Having said that, the only tool we really use is the grid (the rest of them are no better than Flowbite/HTML5/etc. controls. And even then, we really need to be leveraging the advanced functionality of the grid before telling the client they'll have to buy a support license.

16.7k views16.7k

Comments

Detailed Comparison

jQuery UI	Kendo UI
Whether you're building highly interactive web applications or you just need to add a date picker to a form control, jQuery UI is the perfect choice.	Fast, light, complete: 70+ jQuery-based UI widgets in one powerful toolset. AngularJS integration, Bootstrap support, mobile controls, offline data solution.
-	Ultimate Performance with Minimum Resources;Mobile-Friendly and Responsive;Built-In, Customizable Themes ;Open Source Core
Statistics
GitHub Stars 11.3K	GitHub Stars 2.6K
GitHub Forks 5.3K	GitHub Forks 1.9K
Stacks 40.6K	Stacks 297
Followers 13.3K	Followers 359
Votes 899	Votes 33
Pros & Cons
Pros 215 Ui components 156 Cross-browser 121 Easy 100 It's jquery 81 Open source Cons 1 Does not contain charts or graphs	Pros 15 Collection of controls 5 Speed 4 Multi-framework support 4 Mobile 2 AngularJS Cons 4 Massive footprint 3 Slow 1 Awdawd 1 Spotty Documentation 1 Expensive
Integrations
No integrations available	Bootstrap AngularJS

What are some alternatives to jQuery UI, Kendo UI?

jQuery

jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML.

AngularJS

AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML’s syntax to express your application’s components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.

React

Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.

Vue.js

It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API.

Svelte

If you've ever built a JavaScript application, the chances are you've encountered – or at least heard of – frameworks like React, Angular, Vue and Ractive. Like Svelte, these tools all share a goal of making it easy to build slick interactive user interfaces. Rather than interpreting your application code at run time, your app is converted into ideal JavaScript at build time. That means you don't pay the performance cost of the framework's abstractions, or incur a penalty when your app first loads.

Flux

Flux is the application architecture that Facebook uses for building client-side web applications. It complements React's composable view components by utilizing a unidirectional data flow. It's more of a pattern rather than a formal framework, and you can start using Flux immediately without a lot of new code.

Famo.us

Famo.us is a free and open source JavaScript platform for building mobile apps and desktop experiences. What makes Famo.us unique is its JavaScript rendering engine and 3D physics engine that gives developers the power and tools to build native quality apps and animations using pure JavaScript.

Riot

Riot brings custom tags to all browsers. Think React + Polymer but with enjoyable syntax and a small learning curve.

Marko

Marko is a really fast and lightweight HTML-based templating engine that compiles templates to readable Node.js-compatible JavaScript modules, and it works on the server and in the browser. It supports streaming, async rendering and custom tags.

Preact

Preact is an attempt to recreate the core value proposition of React (or similar libraries like Mithril) using as little code as possible, with first-class support for ES2015. Currently the library is around 3kb (minified & gzipped).