React vs. Progress Telerik

React is a JavaScript user interface construction library that works well for:

• Developing web apps with dynamic and complicated user interfaces.
• creating reusable UI elements that may be used in other applications.
• creating single-page applications with dynamic content updates that don't require a page reload.
• The Virtual DOM's effective updating mechanism allows it to handle large volumes of data updates.

React, on the other hand, might be less suitable for:

• Websites that are simple, stagnant, and have no interaction. Other libraries or simple HTML, CSS, and JavaScript may be a better fit in such circumstances.
• Web sockets may be a better choice for applications that need real-time updates, such as chat or gaming apps.
• When creating mobile apps, React Native is a better option.
• Server side rendering only, as React is designed to run on the client side.

Progress Telerik UI is one of the best web design and development solutions for Dot Net based applications. It has extensible support for ASP.NET Core, C#, WCF, and ASP.NET WebForms. It overall improves the design structure for the applications and provides multiple customization options to meet the requirements of clients and end-users.

Incentivized

• Solid backing by large organization (Facebook) thats committed to keeping the development on the project. In my mind, this is the number one priority for any library because without this: time is wasted on getting up-to speed on a library that you will never use, have a codebase with a library thats hard to maintain because few years down the lane, hiring devs to maintain an unsupported library is very difficult.
• As with any libraries, open source community's support is critical for success of any framework because this allows for more pre-built components that could be used right out-of-box => makes Development using React a breeze.
• React's Stateful and Stateless components make organizing your code a breeze. These components would also allow for writing clean Unit Tests on the logic.
• React's component lifecycle. It offers a variety of lifecycle methods, that allows for handling different scenarios of loading and manipulating data in the UI.
• I found React's documentation very well maintained with plenty of examples explaining each feature.
• Responsiveness is a very important criteria in selecting a UI and React is very responsive. It does some neat optimizations on re-rendering using virtual DOM and would only re-render parts of the DOM that changed. These optimizations makes React Applications feel really fast.
• React Native would allow for building applications that span across web and mobile interfaces (iOS and Android). This makes learning React even more enticing, because using a single library, you could build applications that span across Web, iOS and Android.
• create-react-app is an effort by Facebook (creators of React) that makes getting started with React really easy. It does all the heavy lifting of configurations for you and allow you to focus on just development.
• Small footprint, minified React + React DOM is under 150Kb, that makes loading UI's with react really fast.
• React + Enzyme (backed by Airbnb) + Sinon + Mocha + Chai makes unit testing the UI components fun and improves the overall maintainability of the project.

Incentivized

• Telerik enables rapid application development for the demonstration of concepts.
• It provides a good set of themes and functional additions to a UI development environment.
• Each control is packed with valuable features.
• The support team is responsive and very knowledgeable about making their product work in whatever situation you need.

Incentivized

• React's state management can get hairy if you have a deeply nested component and need to pass things up or down the tree very far. This is where libraries like Redux come in, however.
• The progressive nature of its development and change cycles can leave information outdated online faster than other frameworks. This can make finding help or documentation on 3rd party sites frustrating.
• The learning curve on "thinking in React" can be slightly higher than other more familiar patterns of web development.
• Building an app in it can be cumbersome to set up with webpack, but things like Create React App can get you going in a jiffy.

Incentivized

• I have not worked with the App Builder but I think a GUI for dragging and dropping components to build a web page would be great.
• In addition to the app builder there should some tools to design a responsive web application to see the results for different screen sizes.

Incentivized

The Telerik UI has become part of our staple development tools. We can not be as productive without the feature set available to us in the Telerik UI ASP.NET AJAX control package.

There are a few things that may take some getting used to when coming to a modern JS frontend. Tools like Babel and Webpack (or abstractions that hide their details from you) are often a starting point and JSX can be confusing at first. But assuming the developer is already familiar with modern frontend tools, React is a very natural fit and makes creating user interfaces a joy.

Incentivized

The UX of their UI is very well thought out, the micro-interactions are intuitive - thus great for your end user as less training is needed. Using the software, there [are] loads to get you going, you can download their whole demo site and see how each demo works. There is more now on github to get you started, also much on an awesome CDN that's well bedded in so your app is speedy and up to date.

Since it's open-source and very popular, the community support for React and related tools and libraries is excellent. There are a lot of people using the same tools, and so issues tend to get fixed quickly and "recipes" are easy to come by. And since it's backed by Facebook, they have a dedicated engineering team working on the progression of React.

Incentivized

Progress Telerik UI customer support is pretty good. The ticketing system allows a thread of questions, answers, and attachments of code and screenshots. Response time is fairly quick and often has code snippets or pointers to online examples that could be relevant. There is a large amount of community support forums to get answers or post questions. In addition there is a forum of posted code samples for the various controls. The Progress update tool easily tells you what products have been updated and allows you to install the updates on your development system. Release notes can be displayed to see what's new.

Incentivized

The controls work very well as long as they are used as intended. Built-in functionality should be used whenever possible,

Incentivized

There are other options for building SPAs, and the two most common aside from React are Vue and Angular. React has been the leader of the pack for a while and has been an innovator. Angular is good for companies that want an opinionated framework so that it standardizes practices. However, Angular is known to be more difficult to work with and unnecessarily complex. Vue is seen as taking the best from React and Angular, and it is built for incremental upgrades. Vue has a passionate and growing user base, but it hasn't quite caught React in popularity.

Incentivized

The Telerik controls were just easier for us to use and implement. Our evaluation of control packages was over 9 years ago, so it is hard to recall the major differences. Generally, the team preferred what Telerik had to offer, particularly the fact that the bundle provided controls, not just for the ASP.NET context, but also Windows applications, and the cross-platform contexts as well.

• Since we're still in the conversion cycle, all the data is not in. But React has had a positive impact on Developer productivity and the ability to produce efficient, highly flexible UX. This in turn, enhances our customer experience, which is generally the most important component of our ROI.
• Conversion has been difficult since it requires a change of mindset. Most developers have adapted quite well, but the process has been lengthy, and 2 years in, we are still not fully converted. This essentially is a temporary negative impact on ROI.

Incentivized

• Provides rapid development - it has helped me create multiple web applications in MVC and Angular within a one-month time frame.
• Our clients were facing challenges (taking time to load applications, grid view, and generating reports ) with asp.net web applications. Using Kendo UI we have migrated the ASP.NET application to MVC within a one-month time frame. The client was very happy with the application's performance and responsive UI.

Incentivized