Get Advice Icon

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

Next.js
Next.js

694
336
+ 1
50
PhoneGap
PhoneGap

420
330
+ 1
90
Add tool

Next.js vs PhoneGap: What are the differences?

What is Next.js? *A small framework for server-rendered universal JavaScript apps *. Next.js is a minimalistic framework for server-rendered React applications.

What is PhoneGap? Easilily create mobile apps using HTML, CSS, and JavaScript. PhoneGap is a web platform that exposes native mobile device apis and data to JavaScript. PhoneGap is a distribution of Apache Cordova. PhoneGap allows you to use standard web technologies such as HTML5, CSS3, and JavaScript for cross-platform development, avoiding each mobile platforms' native development language. Applications execute within wrappers targeted to each platform, and rely on standards-compliant API bindings to access each device's sensors, data, and network status.

Next.js belongs to "Frameworks (Full Stack)" category of the tech stack, while PhoneGap can be primarily classified under "Cross-Platform Mobile Development".

Some of the features offered by Next.js are:

  • Zero setup. Use the filesystem as an API
  • Only JavaScript. Everything is a function
  • Automatic server rendering and code splitting

On the other hand, PhoneGap provides the following key features:

  • Android
  • Blackberry
  • iOS

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

Next.js and PhoneGap are both open source tools. Next.js with 38.7K GitHub stars and 4.69K forks on GitHub appears to be more popular than PhoneGap with 4.15K GitHub stars and 975 GitHub forks.

According to the StackShare community, Next.js has a broader approval, being mentioned in 82 company stacks & 69 developers stacks; compared to PhoneGap, which is listed in 86 company stacks and 36 developer stacks.

What is Next.js?

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

What is PhoneGap?

PhoneGap is a web platform that exposes native mobile device apis and data to JavaScript. PhoneGap is a distribution of Apache Cordova. PhoneGap allows you to use standard web technologies such as HTML5, CSS3, and JavaScript for cross-platform development, avoiding each mobile platforms' native development language. Applications execute within wrappers targeted to each platform, and rely on standards-compliant API bindings to access each device's sensors, data, and network status.
Get Advice Icon

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

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

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

    Be the first to leave a con
    Jobs that mention Next.js and PhoneGap as a desired skillset
    What companies use Next.js?
    What companies use PhoneGap?

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

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

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

    What are some alternatives to Next.js and PhoneGap?
    Create React App
    Create React apps with no build configuration.
    Gatsby
    Gatsby lets you build blazing fast sites with your data, whatever the source. Liberate your sites from legacy CMSs and fly into the future.
    Hexo
    Hexo is a fast, simple and powerful blog framework. It parses your posts with Markdown or other render engine and generates static files with the beautiful theme. All of these just take seconds.
    LoopBack
    A highly-extensible, open-source Node.js framework that enables you to create dynamic end-to-end REST APIs with little or no coding. Connect to multiple data sources, write business logic in Node.js, glue on top of your existing services and data, connect using JS, iOS & Android SDKs.
    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.
    See all alternatives
    Decisions about Next.js and PhoneGap
    Sezgi Ulu莽am
    Sezgi Ulu莽am
    Sr. Software Engineer at StackShare | 6 upvotes 43.3K views
    Flutter
    Flutter
    React Native
    React Native
    PhoneGap
    PhoneGap
    Apache Cordova
    Apache Cordova
    #NativeApps
    #MobileFrameworks
    #JavaScript

    For a front end dev like me, using a mobile framework for side projects makes more sense than writing a native app. I had used Apache Cordova (formerly PhoneGap) before (because React Native didn't exist yet), and was happy with it. But once React Native came out, it made more sense to go that way instead. It's more efficient and smooth, since it doesn't have the simulation overhead, and has more access to hardware features. It feels cleaner since you don't need to deal with #WebView, using native UI widgets directly. I also considered Flutter . It looks promising, but is relatively new to the game, and React Native seems more stable for now.

    MobileFrameworks #JavaScript NativeApps

    See more
    Jonathan Pugh
    Jonathan Pugh
    Software Engineer / Project Manager / Technical Architect | 17 upvotes 121.3K views
    Pouchdb
    Pouchdb
    CouchDB
    CouchDB
    Font Awesome
    Font Awesome
    CSS 3
    CSS 3
    Apache Cordova
    Apache Cordova
    PhoneGap
    PhoneGap
    HTML5
    HTML5
    Ruby
    Ruby
    Babel
    Babel
    Webpack
    Webpack
    Visual Studio Code
    Visual Studio Code
    Figma
    Figma
    TypeScript
    TypeScript
    JavaScript
    JavaScript
    Framework7
    Framework7
    #Css
    #CSS3
    #SCSS
    #Sass
    #Less
    #Electron
    #HandleBars
    #Template7
    #Sketch
    #GraphQL
    #HTML5
    #GraphCool

    I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

    For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

    Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

    I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

    I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

    I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

    I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

    For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

    For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

    For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

    I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

    So that's my latest mobile stack. What tools do you use? Have you tried these ones?

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

    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 16.8K views
    atHerman MillerHerman Miller
    prismic.io
    prismic.io
    Next.js
    Next.js
    React
    React
    Node.js
    Node.js

    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
    Martin Johannesson
    Martin Johannesson
    Senior Software Developer at IT Minds | 10 upvotes 12K views
    atIT MindsIT Minds
    AMP
    AMP
    PWA
    PWA
    React
    React
    MongoDB
    MongoDB
    Next.js
    Next.js
    GraphQL
    GraphQL
    Apollo
    Apollo
    PostgreSQL
    PostgreSQL
    TypeORM
    TypeORM
    Node.js
    Node.js
    TypeScript
    TypeScript
    #Serverless
    #Backend
    #B2B

    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 540 views
    Next.js
    Next.js
    Graphene
    Graphene
    GraphQL
    GraphQL
    Django
    Django

    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
    Interest over time
    Reviews of Next.js and PhoneGap
    No reviews found
    How developers use Next.js and PhoneGap
    Avatar of Trading Log
    Trading Log uses PhoneGapPhoneGap

    We used phonegap best practices to compile and deploy our hybrid to android and ios markets.

    Avatar of William Baker
    William Baker uses PhoneGapPhoneGap

    To release the JavaScript game Whack-A-Mol http://www.ethertear.com/apps.html

    Avatar of Smileupps
    Smileupps uses PhoneGapPhoneGap

    to let web apps benefit of native device features

    Avatar of Eyal El.
    Eyal El. uses PhoneGapPhoneGap

    Our Apps are wrapped with PhoneGap 7 & 8

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