Angular or React: Summary

Stas Demchuk

by Stas Demchuk on 09/16/2015


Angular and React, by default, solve different problems. Angular provides you a way to build your app without having to use a bunch of third party libraries for things like AJAX requests and DOM manipulation. Angular has everything needed to build a decent SPA out of the box. With that, it can have performance problems and can be overwhelming for people to learn.

You have to follow the "angular way" of doing things if you want to easily extend your application in the future. That's both good and bad, because you get nicely structured code that is more or less readable, but in some cases you will write a lot of code to just make your implementation look and work the way Angular wants.

If you have to build a lot of custom logic, think twice before choosing Angular. In the short term, it'll help you build an MVP with little amout of boilerplate code, but later on, you might end up spending time on fixing another hard-to-trace bug when you integrate new features into your app.

React is your best choice if you're really concerned about performance. You'll get a fast and efficient way to represent your data as a set of components, each of them responsible for its own part of the UI.

React will provide a way to decouple your application layers with ease and to reuse code pretty well. You'll have to write more boilerplate code than you would with Angular. Also, you won't build an SPA with just React, you'll need other components like React Router and Flux. The philosophy of React and Flux can be quite confusing at the beginning, so be ready to face a lot of weird decisions devs at Facebook made. But again, give it five minutes and you'll see that it's not that bad at all.

What influences your decision between angular and react? Let us know in the comments below!

Previous article in this series: Angular or React: Maintenance