Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

AngularJS
AngularJS

22.1K
14.5K
+ 1
5.2K
Next.js
Next.js

894
578
+ 1
68
Add tool

AngularJS vs Next.js: What are the differences?

AngularJS: Superheroic JavaScript MVW Framework. AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML鈥檚 syntax to express your application鈥檚 components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding; Next.js: *A small framework for server-rendered universal JavaScript apps *. Next.js is a minimalistic framework for server-rendered React applications.

AngularJS can be classified as a tool in the "Javascript MVC Frameworks" category, while Next.js is grouped under "Frameworks (Full Stack)".

"Quick to develop" is the primary reason why developers consider AngularJS over the competitors, whereas "Automatic server rendering and code splitting" was stated as the key factor in picking Next.js.

AngularJS and Next.js are both open source tools. It seems that AngularJS with 59.6K GitHub stars and 28.9K forks on GitHub has more adoption than Next.js with 38.7K GitHub stars and 4.69K GitHub forks.

Google, Lyft, and Udemy are some of the popular companies that use AngularJS, whereas Next.js is used by CircleCI, Avocode, and SeatGeek. AngularJS has a broader approval, being mentioned in 2799 company stacks & 1860 developers stacks; compared to Next.js, which is listed in 82 company stacks and 69 developer stacks.

What is AngularJS?

AngularJS lets you write client-side web applications as if you had a smarter browser. It lets you use good old HTML (or HAML, Jade and friends!) as your template language and lets you extend HTML鈥檚 syntax to express your application鈥檚 components clearly and succinctly. It automatically synchronizes data from your UI (view) with your JavaScript objects (model) through 2-way data binding.

What is Next.js?

Next.js is a minimalistic framework for server-rendered React applications.
Get Advice Icon

Need advice about which tool to choose?Ask the StackShare community!

Why do developers choose AngularJS?
Why do developers choose Next.js?

Sign up to add, upvote and see more prosMake informed product decisions

    Be the first to leave a con
    What companies use AngularJS?
    What companies use Next.js?

    Sign up to get full access to all the companiesMake informed product decisions

    What tools integrate with AngularJS?
    What tools integrate with Next.js?

    Sign up to get full access to all the tool integrationsMake informed product decisions

    What are some alternatives to AngularJS and Next.js?
    JavaScript
    JavaScript is most known as the scripting language for Web pages, but used in many non-browser environments as well such as node.js or Apache CouchDB. It is a prototype-based, multi-paradigm scripting language that is dynamic,and supports object-oriented, imperative, and functional programming styles.
    Angular 2
    It is a TypeScript-based open-source web application framework. It is a development platform for building mobile and desktop web applications.
    React
    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project.
    Node.js
    Node.js uses an event-driven, non-blocking I/O model that makes it lightweight and efficient, perfect for data-intensive real-time applications that run across distributed devices.
    jQuery
    jQuery is a cross-platform JavaScript library designed to simplify the client-side scripting of HTML.
    See all alternatives
    Decisions about AngularJS and Next.js
    Jake Stein
    Jake Stein
    CEO at Stitch | 15 upvotes 150.1K views
    atStitchStitch
    AngularJS
    AngularJS
    React
    React
    CoffeeScript
    CoffeeScript
    JavaScript
    JavaScript
    ES6
    ES6

    Stitch鈥檚 frontend is used to configure data sources and destinations and monitor the status of each. Although we have been using AngularJS since its early days, we recently introduced React components into our front end, which many of our developers find easier to work with. We started using CoffeeScript when it was one of the few options for a more expressive alternative to vanilla JavaScript, but today we opt to instead write new code in ES6, which we feel is a more mature alternative.

    See more
    Spenser Coke
    Spenser Coke
    Product Engineer at Loanlink.de | 9 upvotes 227.7K views
    atLoanlink GmbhLoanlink Gmbh
    Rails
    Rails
    AngularJS
    AngularJS
    .NET
    .NET
    Node.js
    Node.js
    React
    React
    GitHub
    GitHub
    Trello
    Trello
    Zapier
    Zapier
    Mailchimp
    Mailchimp
    Google Drive
    Google Drive
    Vue.js
    Vue.js
    HTML5
    HTML5

    When starting a new company and building a new product w/ limited engineering we chose to optimize for expertise and rapid development, landing on Rails API, w/ AngularJS on the front.

    The reality is that we're building a CRUD app, so we considered going w/ vanilla Rails MVC to optimize velocity early on (it may not be sexy, but it gets the job done). Instead, we opted to split the codebase to allow for a richer front-end experience, focus on skill specificity when hiring, and give us the flexibility to be consumed by multiple clients in the future.

    We also considered .NET core or Node.js for the API layer, and React on the front-end, but our experiences dealing with mature Node APIs and the rapid-fire changes that comes with state management in React-land put us off, given our level of experience with those tools.

    We're using GitHub and Trello to track issues and projects, and a plethora of other tools to help the operational team, like Zapier, MailChimp, Google Drive with some basic Vue.js & HTML5 apps for smaller internal-facing web projects.

    See more
    Arik Fraimovich
    Arik Fraimovich
    AngularJS
    AngularJS
    Angular 2
    Angular 2
    React
    React
    Vue.js
    Vue.js

    When Redash was created 5 years ago we chose AngularJS as our frontend framework, but as AngularJS was replaced by Angular 2 we had to make a new choice. We decided that we won't migrate to Angular, but to either React or Vue.js. Eventually we decided to migrate to React for the following reasons:

    1. Many in our community are already using React internally and will be able to contribute.
    2. Using react2angular we can do the migration gradually over time instead of having to invest in a big rewrite while halting feature development.

    So far the gradual strategy pays off and in the last 3 major releases we already shipped React code in the Angular.js application.

    See more
    Adam Rabinovitch
    Adam Rabinovitch
    Global Technical Recruiting Lead & Engineering Evangelist at Beamery | 5 upvotes 96.9K views
    atBeameryBeamery
    AngularJS
    AngularJS
    React
    React
    Angular 2
    Angular 2
    Vue.js
    Vue.js
    Aurelia
    Aurelia
    Polymer
    Polymer
    #Hiring

    At Beamery we had a large, AngularJS app, built over several years. Our clients were happy, but we were not. We had several problems: Building new features was slow. AngularJS doesn鈥檛 scale nicely. Features clash with each other. Isolation doesn鈥檛 come as standard, you have to work hard to keep features separate. It takes time to get it right. #Hiring was hard, for all the reasons listed above. The app was slower than it needed to be because AngularJS was never built for speed. We wanted to render half a million contacts, and Angular was fighting us all the way.

    As time went by it become harder to find developers who would willingly choose AngularJS over React Angular 2 , Vue.js , Aurelia or Polymer .

    So we faced a choice. We could throw it all away and start again, we could upgrade to Angular 5, or the awesome option - we could use micro frontends. We chose the awesome option.

    See more
    React
    React
    Redux
    Redux
    AngularJS
    AngularJS
    React Native
    React Native
    redux-saga
    redux-saga
    Apache Cordova
    Apache Cordova
    #JavascriptMvcFrameworks

    We had contemplated a long time which #JavascriptMvcFrameworks to use, React and React Native vs AngularJS and Apache Cordova in both web and mobile. Eventually we chose react over angular since it was quicker to learn, less code for simple apps and quicker integration of third party javascript modules. for the full MVC we added Redux.js for state management and redux-saga for async calls and logic. since we also have mobile app along with the web, we can shere logic and model between web and mobile.

    See more
    Gianluca Bargelli
    Gianluca Bargelli
    React
    React
    AngularJS
    AngularJS
    Redux
    Redux
    MobX
    MobX

    We started rebuilding our dashboard components using React from AngularJS over 3 years ago and, in order to have predictable client-side state management we introduced Redux.js inside our stack because of the popularity it gained inside the JavaScript community; that said, the number of lines of codes needed to implement even the simplest form was unnecessarily high, from a simple form to a more complex component like our team management page.

    By switching our state management to MobX we removed approximately 40% of our boilerplate code and simplified our front-end development flow, which in the ends allowed us to focus more into product features rather than architectural choices.

    See more
    Divine Bawa
    Divine Bawa
    at PayHub Ghana Limited | 14 upvotes 195.9K views
    Node.js
    Node.js
    GraphQL
    GraphQL
    MySQL
    MySQL
    Prisma
    Prisma
    graphql-yoga
    graphql-yoga
    React
    React
    styled-components
    styled-components
    Next.js
    Next.js
    Apollo
    Apollo

    I just finished a web app meant for a business that offers training programs for certain professional courses. I chose this stack to test out my skills in graphql and react. I used Node.js , GraphQL , MySQL for the #Backend utilizing Prisma as a database interface for MySQL to provide CRUD APIs and graphql-yoga as a server. For the #frontend I chose React, styled-components for styling, Next.js for routing and SSR and Apollo for data management. I really liked the outcome and I will definitely use this stack in future projects.

    See more
    David Ritsema
    David Ritsema
    Frontend Architect at Herman Miller | 7 upvotes 32K views
    atHerman MillerHerman Miller
    Node.js
    Node.js
    React
    React
    Next.js
    Next.js
    prismic.io
    prismic.io

    When we started thinking about technology options for our own Design System, we wanted to focus on two primary goals

    1. Build a design system site using design system components - a living prototype
    2. Explore new ways of working to position our technical capabilities for the future

    We have a small team of developers responsible for the initial build so we knew that we couldn鈥檛 spend too much time maintaining infrastructure on the Backend. We also wanted freedom to make decisions on the Frontend with the ability to adapt over time.

    For this first iteration we decided to use Node.js, React, and Next.js. Content will be managed via headless CMS in prismic.io.

    1. Next.js so that we can run React serverside without worrying about server code.
    2. prismic.io so that our content is accessible via API and our frontend is fully independent.
    See more
    AngularJS
    AngularJS
    React
    React
    .NET Core
    .NET Core
    TypeScript
    TypeScript

    I use TypeScript because it's adoption by many developers, it's supported by many companies, and it's growth. AngularJS, React, @ASP.NET Core. I started using it in .NET Core, then for a job. Later I added more Angular experience and wrote more React software. It makes your code easier to understand and read... which means it makes other people's code easier to understand and read.

    See more
    Rafael Santos
    Rafael Santos
    CTO at Decision6 | 11 upvotes 22.2K views
    atDecision6Decision6
    AngularJS
    AngularJS
    React
    React
    Vue.js
    Vue.js

    Back in 2015, my company had a back-office dashboard that was originally built in AngularJS 1. Since Angular 2 presented drastic changes we decided to rethink the options and we looked at React and Vue.js. Besides, at the time, Vue had basically only one developer, its structure (100% oriented to components) and also its backward compatibility focus (Angular 1 to 2 no more) we preferred it against React cause it seemed more straightforward, clean and with a small learning curve. Now 4-5 years later we are very happy with our choice.

    See more
    Martin Johannesson
    Martin Johannesson
    Senior Software Developer at IT Minds | 11 upvotes 31.1K views
    atIT MindsIT Minds
    TypeScript
    TypeScript
    Node.js
    Node.js
    TypeORM
    TypeORM
    PostgreSQL
    PostgreSQL
    Apollo
    Apollo
    GraphQL
    GraphQL
    Next.js
    Next.js
    MongoDB
    MongoDB
    React
    React
    PWA
    PWA
    AMP
    AMP
    #B2B
    #Backend
    #Serverless

    At IT Minds we create customized internal or #B2B web and mobile apps. I have a go to stack that I pitch to our customers consisting of 3 core areas. 1) A data core #backend . 2) A micro #serverless #backend. 3) A user client #frontend.

    For the Data Core I create a backend using TypeScript Node.js and with TypeORM connecting to a PostgreSQL Exposing an action based api with Apollo GraphQL

    For the micro serverless backend, which purpose is verification for authentication, autorization, logins and the likes. It is created with Next.js api pages. Using MongoDB to store essential information, caching etc.

    Finally the frontend is built with React using Next.js , TypeScript and @Apollo. We create the frontend as a PWA and have a AMP landing page by default.

    See more
    Michael Mota
    Michael Mota
    CEO & Founder at AlterEstate | 4 upvotes 2.6K views
    Django
    Django
    GraphQL
    GraphQL
    Graphene
    Graphene
    Next.js
    Next.js

    I've been using Django for quite a long time and in my opinion I would never switch from it. My company is currently using Django with REST framework and a part in GraphQL using Graphene. On the frontend we use Next.js and so far everything has been running quite good. I've found limitations but manage to solve it.

    As someone mentioned before, if you are comfortable with Django, don't switch. There's no need since with django you can basically achieve anything. Of course this will depend on the project you want to build, but the scalability and flexibility django can offer it's just out of this world. (Don't want to sound like a fan boy haha but it really is).

    See more
    Bryam Rodriguez
    Bryam Rodriguez
    JavaScript
    JavaScript
    Bit
    Bit
    Python
    Python
    Next.js
    Next.js
    React Native
    React Native
    Redis
    Redis
    MongoDB
    MongoDB
    PostgreSQL
    PostgreSQL
    RSpec
    RSpec
    react-testing-library
    react-testing-library
    Jest
    Jest
    Create React App
    Create React App
    Redux
    Redux
    React
    React
    Rails
    Rails
    Ruby
    Ruby

    I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

    We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

    Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis 聽for cache and other time sensitive operations.

    We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

    Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

    See more
    Interest over time
    Reviews of AngularJS and Next.js
    No reviews found
    How developers use AngularJS and Next.js
    Avatar of shridhardalavi
    shridhardalavi uses AngularJSAngularJS

    AngularJS is a structural framework for dynamic web apps. With AngularJS, designers can use HTML as the template language and it allows for the extension of HTML's syntax to convey the application's components effortlessly. Angular makes much of the code you would otherwise have to write completely redundant. We can use Angular to build any kind of app, taking advantage of features like: Two-way binding, templating, RESTful api handling, modularization, AJAX handling, dependency injection, etc

    Avatar of Kalibrr
    Kalibrr uses AngularJSAngularJS

    All of our frontend code is on AngularJS. Directives, controllers, and services really help in organizing code in order to keep things maintainable, and two-way binding makes data input easy. The large ecosystem of modules for directives is fantastic, too.

    Avatar of Nikola Novakovic
    Nikola Novakovic uses AngularJSAngularJS

    When ever I need heavy user client side apps this is my tool of choice. There are a ton of JS frameworks out there, picked this one because of philosophy they are trying to put out there and great community. Two way data binding FTW!

    Avatar of Yaakov Gesher
    Yaakov Gesher uses AngularJSAngularJS

    The front end was built on an Angular template supplied by the client. We leveraged Angular's flexibility and speed to delivered complex matrices of data quickly and with great finesse.

    Avatar of InJoin
    InJoin uses AngularJSAngularJS

    We use Angular.js to build our front-end framework known as Frontkit, so our apps can get started faster with reliable, interactive components.

    How much does AngularJS cost?
    How much does Next.js cost?
    Pricing unavailable
    Pricing unavailable
    News about Next.js
    More news