# Why the Team Transitioned Its Frontend from Angular to React

DevFeed: [Why the Team Transitioned Its Frontend from Angular to React](<https://devfeed.tech/articles/reacting-to-change-28631.md>)

Original publisher: [Read original article](<https://eng.localytics.com/reacting-to-change/>)

Author: Nate Tenczar

Published: 2017-02-02T20:33:59Z

Content type: opinion

Language: en

Sources: [Localytics](<https://devfeed.tech/sources/localytics.md>)

Topics: [React](<https://devfeed.tech/topics/react.md>), [Angular](<https://devfeed.tech/topics/angular.md>), [frontend development](<https://devfeed.tech/topics/frontend-development.md>), [JavaScript](<https://devfeed.tech/topics/javascript.md>)

Tags: [angular](<https://devfeed.tech/tags/angular.md>), [frameworks](<https://devfeed.tech/tags/frameworks.md>), [frontend](<https://devfeed.tech/tags/frontend.md>), [javascript](<https://devfeed.tech/tags/javascript.md>), [react](<https://devfeed.tech/tags/react.md>)

## AI overview

The article explains how the team evaluated its frontend development environment and decided to transition from Angular to React. It cites React's growing user base, state-management solutions, and existing internal use, while emphasizing that the opinions reflect the team's specific use case.

## Source excerpt

If you sit quietly enough while reading this article you'll hear a sound. It's the faint tapping of fingers on a keyboard, off in the distance in parts unknown. Those self-assured fingers are putting together yet another think piece on JavaScript in this--the