# Why choose KendoUI
*About KendoUI*
## 3.2 Why choose KendoUI
We expect at least two classes of Aurelia-KendoUI components users
1. Existing Telerik KendoUI SDK customers, seeking for the state of the art front end framework, where Aurelia is by far the best alternative
2. Existing Aurelia developers, who are tired of "manual" adaptation of various UI toolkits, all of which expose the same JavaScript based interface as Telerik KendoUI SDK does. While the set of Aurelia KendoUI components is the first in the series of [**Aurelia-UI-Toolkits**](https://github.com/aurelia-ui-toolkits) authored bridges, we plan to continue enriching Aurelia development environment with interfaces to other JavaScript toolkits as well. \
### Ultimate Performance with Minimum Resources
Fast and light. Every Kendo UI widget is rendered with the fastest possible mark-up to deliver ultimate JavaScript performance. \
### Mobile-Friendly and Responsive
Touch support, easy mobile rendering, responsive capabilities and integration with Bootstrap. [**Learn more**](http://www.telerik.com/kendo-ui/responsive-features) about the rich Kendo UI responsive features. \
### Built-In, Customizable Themes
Apply one of the 16 built-in themes, (KendoUI Default theme shown as selected) \
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://aurelia-ui-toolkits-1.gitbook.io/kendoui-bridge-docs/about-kendoui/why-choose-kendoui.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.