React Reviews

34 Ratings
<a href='https://www.trustradius.com/static/about-trustradius-scoring' target='_blank' rel='nofollow noopener noreferrer'>trScore algorithm: Learn more.</a>
Score 9.4 out of 101

Do you work for this company? Manage this listing

Overall Rating

Reviewer's Company Size

Last Updated

By Topic

Industry

Department

Experience

Job Type

Role

Reviews (1-8 of 8)

César Costas Carrera profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
React is used by the front end team to build our website. It allows the team to work in a modular way, creating components that can be either reusable (saving development time in future developments) or exclusive (encapsulating the unique logic and preventing it to be broken by other developments). Working with React allows the business to scale quickly.
  • Modular development.
  • Server-side rendering.
  • Small learning curve.
  • I would like to see a separation between React as a javascript tool attached to the DOM and JSX the Virtual DOM rendering engine. With that separation, static sites (which are already rendered and don't need JSX) would be able to be even smaller.
  • A React app might get messy producing lots of re-renders.
If you're writing a site with multiple pages, and any kind of interactivity (click, navigation, opening modals, etc.), React is a suitable option.

If you're writing a single page, with no navigation and just displaying information (you probably don't even need javascript), then React is an overload.
Read César Costas Carrera's full review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
Many teams in our organization are using React for both our web properties and several mobile apps (using React Native). It is the default client-side framework and mobile app stack for any new work as well. This lets engineers easily collaborate between different projects and also share components.
  • Lots of compatible libraries and tools
  • Fantastic developer experience and mental model
  • Easy to layer abstractions and compose large pages from small components
  • Without using tools like Gatsby or Next, React encourages large client-side bundles with no content available immediately.
  • Usually, you need to put together your own "framework" from other tools since React is just the view layer.
  • React Native is still maturing, though there is a lot of activity on that project latey.
React is great for very interactive experiences like search filters, dynamic forms, graphs and charts, and anything else where immediate interaction vastly improves the user experience. For very simple content that could be server-rendered and there are existing rails (or similar) backend in place, that can often be a better choice. But the advantages of a static React frontend are easy cachability on a CDN, pre-rendered content with tools like Gatsby, and easy deployment to platforms like Netlify or Amazon S3. React Native is also a fantastic tool for creating cross-platform applications that need to run on both iOS and Android.
Read this authenticated review
Erik Ralston profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
React, and its ecosystem of thirty-party modules, is the primary front-end library for our products at LiveTiles. It provides a dynamic HTML templating system, plus event and state-handling for our applications. This provides better reusability of code by making interfaces as modular components, plus provides an easy onboarding path for new front-end developers.
  • Intuitive templating language (JSX) that provides a dynamic rendering of HTML elements, along with an easy model to tie back to JavaScript implemented in your components.
  • Component-based views that guide the developer to modular and reusable pieces to your interface.
  • Streamlined state management with immutable properties and mutable state within each component with one-day data-binding to tie them to the view
  • When you hear someone say "React is a LIBRARY, not a FRAMEWORK", they're right. It's only the View layer of the application and nothing else. Some developers get this wrong, put too much application logic into their React components, then end up with no separation of concerns.
  • It's so easy to get started that it's hard to realize when you're doing it wrong. Developers who are early into React can come up with issues like nesting the Props and State of their components wrong, leading to issues like re-rendering all of a list of items rather than just one item.
  • It's so ubiquitous that there are certain developers I've met who have never done direct DOM manipulation. While it's easy to make something in React in most cases, developers need to make sure they know how to use the Js API as well as the convenient library.
In a so-called "Single Page Application (SPA)" or "Progressive Web Application (PWA)," or any app where there's user interaction without leaving the current page, React is excellent for providing a flexible presentation layer or view layer. While it doesn't provide a full data model, it does provide basic state management around components that integrates with virtually any other client-side framework. Also, with "React Native", the mobile implementation of the same library, one can write JSX and have it render components in a mobile app.

React is likely not a good fit for websites with a big emphasis on Search Engine Optimization (SEO). The requirement to render the UI with JavaScript means it's unlikely to be easily crawled by a search engine. This means it's unsuitable for applications like Marketing websites or blogs. Similarly, React doesn't work for situations where you can only use static HTML (EG, HTML e-mail).







Read Erik Ralston's full review
No photo available
Score 10 out of 10
Vetted Review
Verified User
Review Source
We have adopted React as the UI library for all of our different applications and products. It allows us to build scalable user interfaces - both for performance for the client, as well as scalable for in the code base. As our company continues to grow and scale, React remains intuitive and simple to work with. It allows us to build complex single page applications while providing an incredible developer experience.
  • React is fantastic for building performant user interfaces. Our web app is snappy and great for our customers.
  • React has the philosophy of doing one thing and doing it well which is the view layer of the application. This makes it incredibly intuitive and flexible for developers to use.
  • React has lead the way in being able to write modular and structured code. It is a drastic improvement since the days of spaghetti jQuery code.
  • React has an unmatched community. The amount of tools and libraries available is fantastic, and there plenty of solutions available online for common problems.
  • Since React only does one area of the web app (the view layer), this means the developer must patch together the rest of their web app instead of having a single go-to solution. Additional things you need include are routing and state management.
  • React was the leader for building web apps using component architecture. This means that it did get some things wrong, such as making complex classes and having some things difficult to understand. Other libraries have benefited from the learnings of React.
  • The React world moves quickly, and this can mean that code can become outdated quickly. This rapid change can be fatiguing for developers.
React is great for people who are trying to build complex single page web applications. It is intuitive for developers, encourages modularity through components, and provides a web app this will scale. React may not be suited as well for simple websites or static content. However, this is changing with frameworks like Gatsby which allow you to build static HTML websites using React.
Read this authenticated review
Larry Reed profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
React is being adopted as a standard in our organization. When I started using it two years ago, I was one of the early adopters. A few projects had adapted it for part of their system and a number of other projects had announced their intention to move in that direction. Shortly thereafter, we built a new system of design patterns to make our UX more consistent, and this project began building in React. At this point, many projects have begun to convert to it, the design pattern system is fully implemented with it, and fundamental architecture plans for the future are based on it.

The main business problem it addresses is to provide an efficient UX implementation and form the basis for common code development across front end applicatiions. It also is part of our plan to move from Python web apps to NodeJS web apps.
  • React is designed around the notion of generated html as opposed to templated html. This provides more flexibility in building elements on a page, and allows developers to create html that is programmatically configured based on runtime considerations.
  • React uses JSX, which is HTML templating integrated into javascript code. This simplifies the generation of complex structures, especially those that vary based on runtime and interactive data.
  • React is more efficient because it generates a virtual DOM rather than directly building in in the actual DOM. By building 'offline' in this manner, the DOM generation is faster. After building, it can be installed in one operation.
  • React only builds those portions of the display that have changed, making display updates more efficient.
  • Debugging React is challenging. Bugs in react code generate stack traces internal to React and it is often totally unclear how it relates to the code you actually wrote.
  • Relating your React elements to corresponding DOM elements is difficult. The intentional separation of virtual and actual DOM also makes it difficult to map the elements to the structures in the DOM. This is partially ameliorated by the use of the React dev tool, which provides a DOM-like view of the React elements, but the tool still does not provide a direct correspondence with the DOM that is often necessary to figure out why something isn't right.
  • Because JSX is React-specific and not a language feature, a special compilation process is necessary to convert JSX code to normal JS. Coming from a C++ background, compiling things doesn't bother me, but many JS developers are used to a less structured development.
React is really great when you want to build something that is highly fluid, with a lot of data driven display elements. It allows you to describe the DOM in programmatic terms, which makes your display output faster and more efficient. But if you have a highly static page, then it adds a lot of overhead just to get something basic up.
Read Larry Reed's full review
Brendon Lamb profile photo
November 25, 2018

React = Winning

Score 10 out of 10
Vetted Review
Verified User
Review Source
We use it for all of our application development UI needs. Building a UI (and ultimately UX) in JavaScript is great... JSX makes tons of sense and has allowed me to solo-develop Riders Share (in tandem with a handful of other projects/libraries) very quickly.
  • State drive UI & UX
  • Pairs well with React Semantic UI
  • Pairs well with MeteorJS
  • Helps you to structure/organize code in a sensible way
  • Learning curve
  • Frequent changes (but they're always good about backwards compatibility)
React is great for web application development, especially for SPAs (Single Page Apps) - it maybe less suited for traditional website development.
Read Brendon Lamb's full review
Anudeep Palanki profile photo
Score 10 out of 10
Vetted Review
Verified User
Review Source
React is one of the more popular frameworks being used across our organization for developing web interfaces. React is a library that allows for efficient compartmentalization of the code that allows managing code bases on large user interfaces a breeze. It also does several optimizations on the expensive re-rendering process to make the the user interfaces with large data responsive.
  • 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.
  • React could get very frustrating unless you start thinking in React. React enforces a top down hierarchy of data flow and offers no way for the data to communicate backwards. This is a big shift in mindset coming from Angular 1.x. This constraint is really a big factor that determines how to organize your code and how you might want to write your own Components.
  • Because of the self imposed top down hierarchy, you end up having a heavy parents with dumb children. Because parents would need to the bulk of the work, they usually manage the state, while passing callbacks to the child components. If not properly designed, this could lead to the callback hell, where you could have callbacks passing through like multiple children.
  • As with any library, you will have to iterate through multiple designs to come up with a ways to avoid "heavy parent components" in React. One obvious solution is using some open source tools like Redux, but we opted for a variation of it to suit our needs.
Well suited for:
- Building performance intensive web interfaces.
- Making responsive user interfaces that deal with large data.
- Asynchronously retrieving data and partial DOM updates.
- Clean organized code.
- Building interfaces in multiple platforms (thanks to React Native)

Its less suited if:
- You are unwilling to think in React.
Read Anudeep Palanki's full review
Joshua Weaver profile photo
Score 9 out of 10
Vetted Review
Verified User
Review Source
React has been used as a web front-end layer for a few different projects. We have a couple of web applications that we have chosen to use React for. It addressed the need for something that was forward-thinking and progressive in its approach to development. It allows us to structure the client-side logic and presentation code in a more maintainable way.
  • React makes managing state both easy and hard (depending on the context of the situation). So I am using it as both a pro and a con.
  • React makes organizing your code quite easy.
  • React is fast.
  • It can be used on the front end and also rendered server-side.
  • The Ecosystem is enormous for being so young. Wide-spread adoption has helped this and gives you plenty of areas to find help.
  • React Native is an amazing tool that gets you into Mobile Development using the skills you learn in React Web development
  • 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.
If I were just adding small components that needed to do simple things in a web page, I would probably not choose React. It kinda feels like a big hammer for a little nail like that. There is a bit more overhead in library size to accomplish smaller tasks.

With that being said, I feel like React is a great choice for medium to larger size web applications that have lots of moving parts. Using it will help you structure your app more efficiently overall.

There are some areas that are still frustrating and include lots of boilerplate with React (which have been alleviated with certain libraries).
  • Just getting started can be a battle - Use Create React App to get off the ground faster
  • State management can get difficult - Use Redux if necessary
  • Form handling can be laborious - Use Formik or something similar
Read Joshua Weaver's full review

About React

React Technical Details

Operating Systems: Unspecified
Mobile Application:No