It is about time for me to write something about Kendo UI. At first I was very skeptical about this framework. I am not trying to state that Kendo UI is not good; the truth is far from it. It was a fear that people don’t want to read a review of a commercially available framework when there are numerous free of charge. If this is a deterrent in any way, then skip this article. Kendo UI may be the best HTML5 framework in existence, but it will not be useful unless there is a willingness to pay few hundred dollars (per developer / per server-side technology).
Kendo UI consists of few components. First one is web component which provides you with a simple and consistent programming interface, polished and innovative UI widgets for the web, powered by jQuery, HTML5 & CSS3, a MVVM framework, themes and template support. This is also an only open source part of framework.
The second component is a mobile app development framework that will be used for this article examples, mainly because good mobile performance separates good HTML5 frameworks from average ones.
Why Kendo UI
Kendo UI supports every major desktop and mobile browser including IE7, which is pretty impressive. From a mobile perspective, WinPhone8, iOS, Android and Blackberry platforms are supported. Unlike jQuery Mobile Kendo UI widgets match the theming and functionality behavior of native controls available for iOS, Android, BlackBerry and WinPhone8 development, including buttons, navigation, and lists. There’s another great thing, if you want to create a hybrid mobile app you only need to do it once, Phonegap is here to wrap our app into a native package, just like with jQuery Mobile.
- Support for major desktop and mobile browsers, not just web-kit browsers. Not to mention support for major mobile platforms
- Code is optimized for major mobile platforms. Android app will use optimizations made from Android platform, same thing goes for iOS and rest of them.
- Nothing particular
UI and visual impression
UI looks stunning, it is not the best looking HTML5 framework I ever so but it pretty close. High CSS3 usage is pretty obvious, box-shadows and gradients are used everywhere. For some reason, overall app performance doesn’t suffer because of it. This is relatively important because jQuery Mobile 1.4 abandon a lot of its CSS in a hope it will improve overall app performance, not to mention CSS3 background gradient is known performance killer (on mobile devices).
There’s one more thing that left a great impression on me, unlike jQuery Mobile, Kendo UI mobile app will behave/look differently depending on a platform. This is a big step over a jQuery Mobile UI, whose theme feels like iOS UI, which is relatively OK on iOS, but, at least for me, fails on Android. It can go even further if different layouts are used on different platforms that can be quickly turned on ( an example can be found in an example below).
Widgets in both jQuery UI and Kendo UI support themes and styling via CSS. Both frameworks also provide a number of themes out-of-the-box along with a means of creating custom themes. Widgets and themes are customizable, it can be done manually or through provided visual tools.
Link to the jsFiddle example: http://jsfiddle.net/Gajotres/LGwM7/
As you can see in an example below mobile UI renders by default as an iOS on desktop browsers, if you view it from an Android browser it will have android look and feel.
Unfortunately jsFiddle and Kendo UI don’t work together correctly when viewed from mobile devices so take a look here: http://example.gajotres.net/kendoui/index.html. You will see 2 completely different applications depending on iOS or Android device.
[dl url=”http://example.gajotres.net/kendoui/kendu-ui-example.rar” title=”Kendo UI Example” desc=”” type=”.rar” align=”left”]
- Native look depending on platform and platform version. For example, app will look different when watched on different iOS versions.
- App performance don’t suffer from heavy CSS3 usage.
- Again nothing particular