Progress Telerik Reviews and Ratings

Use Cases and Deployment Scope

We've used Progress Telerik for several MAUI and WinUI3 apps. We've found it very helpful for controls like rich text editing and tabs that seem common but for some reason do not have great tooling built-in (or in the community toolkit). So ultimately, we used Progress Telerik to plug the gap in several different platforms where the built-in tooling was not sufficient.

Likelihood to Recommend

Progress Telerik is, in my opinion, easily the best third-party for out-of-the-box controls and has a wide range of useful controls across many platforms.

If your scenario is simple and you need powerful and professional tooling, Progress Telerik is the way to go.

In scenarios where deep customization/integration is needed, I would recommend using native or community toolkit controls.

Use Cases and Deployment Scope

I've been using Progress Telerik's products in these platforms:

- ASP.Net Webforms

- ASP.Net Core

- Xamarin

- JQuery

- Angular

They help me include complex functionality into my apps very easily.

Likelihood to Recommend

Well suited if you need to add complex capabilities to your apps.

I can't think of a scenario where it is less appropriate.

Use Cases and Deployment Scope

We have different web applications that use grids, forms , and schedulers. Using Progress Telerik components, we simply used grids with templated, and a very good looking scheduler with many useful features. Communication of component with the backend using data source features are simple. In addition to these components we used cards and graphs as well.

Likelihood to Recommend

My company started using Progress Telerik after I used the trial version and later recommended it to the other developers and finally the company used it as an official tool for web development. In the application that we started using Telerik, we needed to have a scheduler and the Scheduler component did great. The only problem I has is the documentation on the website. I had to bookmark some pages to find them easily.

Use Cases and Deployment Scope

We use the Progress Telerik control libraries to save time and simplify development of ASP.NET MVC and Blazor applications, and we're moving into using the MAUI pieces as well. Some controls feel like overkill, since the packages include things like textboxes - which DO have some minor extra features, but not enough to switch them out in my opinion. But it also includes advanced ones such as image editors, popovers, cards, skeletons, graphs and so much more that save tons of time when we develop any kind of LOB application.

Likelihood to Recommend

As soon as you need more than the most basic of features in your application, chances are that Progress Telerik has you covered. Personally, we've used graphing and list components frequently, and reporting and input components more often than not. It can be a bit difficult to combine the layout of the Progress Telerik components with your existing, non Progress Telerik controls, but it's definitively doable.

Use Cases and Deployment Scope

We use the Telerik UI ASP.Net AJAX controls on our intranet web-application software deployed to various automotive customers. The controls helped accelerate the creation of screens and dashboards with a consistent user experience. Further, the controls added features and functions without requiring boiler-plate code to be added (such as the Grid control providing filtering, sorting, and paging right out of the box without any additional code work). Other controls (such as the Tree Drop Down), provide great user experience with little to no additional customization required to get the web control to behave / present in the fashion we need. Finally, the demos from Telerik provide excellent references for determining how to do things. The only draw back is on the documentation side, where if you step out of the demo examples, it can be difficult to find the information you need on the document site, and determine what and why you need to something special. Overall, I would emphatically recommend the use of Telerik UI controls to vastly improve the UI experience for your end-users, and accelerate the development time involved in creating the User Interface screens.

Likelihood to Recommend

We have used the Telerik UI controls for our Admin user experience. We found that this lead to consistent user experience, with feature rich functions already provided. Effectively this meant that hour for hour, using the Telerik UI improved productivity in creating screens with more functions than using the default controls in ASP.Net. At this point most of our focus with the Telerik controls is User Interface oriented.

Use Cases and Deployment Scope

I use Telerik UI to develop Web Based applications using MVC. The use of the software components is extremely easy and very powerful. The presentation of the data using the Grids/Graphs/Reports is the biggest selling point in showing our customers the software that was developed using the Telerik controls.

Likelihood to Recommend

The use of the Telerik Data Grid to be able to data-mine is a very powerful tool. To be able to quickly sort, group, filter, and export data that is presented in the grid has been one of the major selling points we use in selling our software is that is was designed using the Telerik Data Grid.

Use Cases and Deployment Scope

We use Progress Telerik UI, specifically for Blazor in multiple applications throughout our company for both internal and external customers. The pre-built components are used for several areas of visualizing data and data manipulation.

Likelihood to Recommend

TileLayout is a quick way to setup customized dashboards for users Forms can inherit objects without having to spend a lot of time building out inputs. Charts are extremely easy to implement and broken up to help simplify customization. The CSS file is extremely large and needs to be slimmed down and simplified to allow multiple elements to use single a css class instead of multiple elements using multiple classes.

Use Cases and Deployment Scope

We specifically use it for Blazor UI Components, across multiple projects in order to cut development time down.

Likelihood to Recommend

It's great in business/internal applications where design and styling are less important. It's not as ideal in highly developed and designed environments where the app is customer-facing.

Use Cases and Deployment Scope

We use Progress Telerik UI for many of our commercial applications as well as custom-built applications. I like the completeness of the suite as I rarely have to go outside of the suite for UI components. We use Winforms, WPF, Xamarin, MVC and ASP/WebForms. Because we drift between the many platforms and webforms, I like that there is a familiar feel when switching between something like a web app and a desktop app when dealing with a grid for instance. I like the Progress Telerik UI control panel to manage versions that I have installed on various platforms.

Likelihood to Recommend

Well suited for web apps that need rich UIs that can utilize modern browsers Well suited for thick desktop apps with moderately powerful PCs. Well suited for presenting great dashboards, and the rad grid is second to none. Great for creating HMIs. Not so well suited for old browsers or on low-powered windows pc running thick apps. Such as a windows based tablet. Tablets running windows

Use Cases and Deployment Scope

We use Telerik UI in our enterprise software solutions built on top of WPF and ASP.NET MVC. It reduces our time building user interface from scratch by our own so we decided to use cutting edge Telerik UI to fast track our development and delivery process. Using Telerik user interface it does not need more expertise rather your current resources can take care of the migration from native to Telerik UI.

Likelihood to Recommend

It suits in enterprise software applications to reduces time building user interface from scratch and rather using cutting edge Telerik UI to fast track the development and delivery process. It has feature rick reporting tools which is most attractive in term of if you have lots of reporting in your application. Small companies may find it difficult to use due to its cost.