Alternatives to Create React Native App logo

Alternatives to Create React Native App

Expo, React Native, Create React App, Flutter, and Ionic are the most popular alternatives and competitors to Create React Native App.
97
205
+ 1
0

What is Create React Native App and what are its top alternatives?

Create React Native App allows you to work with all of the Components and APIs in React Native, as well as most of the JavaScript APIs that the Expo App provides.
Create React Native App is a tool in the Cross-Platform Mobile Development category of a tech stack.
Create React Native App is an open source tool with GitHub stars and GitHub forks. Here’s a link to Create React Native App's open source repository on GitHub

Top Alternatives to Create React Native App

  • Expo
    Expo

    It is a framework and a platform for universal React applications. It is a set of tools and services built around React Native and native platforms that help you develop, build, deploy, and quickly iterate on iOS, Android, and web apps. ...

  • React Native
    React Native

    React Native enables you to build world-class application experiences on native platforms using a consistent developer experience based on JavaScript and React. The focus of React Native is on developer efficiency across all the platforms you care about - learn once, write anywhere. Facebook uses React Native in multiple production apps and will continue investing in React Native. ...

  • Create React App
    Create React App

    Create React apps with no build configuration.

  • Flutter
    Flutter

    Flutter is a mobile app SDK to help developers and designers build modern mobile apps for iOS and Android. ...

  • Ionic
    Ionic

    Free and open source, Ionic offers a library of mobile and desktop-optimized HTML, CSS and JS components for building highly interactive apps. Use with Angular, React, Vue, or plain JavaScript. ...

  • Xamarin
    Xamarin

    Xamarin’s Mono-based products enable .NET developers to use their existing code, libraries and tools (including Visual Studio*), as well as skills in .NET and the C# programming language, to create mobile applications for the industry’s most widely-used mobile devices, including Android-based smartphones and tablets, iPhone, iPad and iPod Touch. ...

  • Apache Cordova
    Apache Cordova

    Apache Cordova is a set of device APIs that allow a mobile app developer to access native device function such as the camera or accelerometer from JavaScript. Combined with a UI framework such as jQuery Mobile or Dojo Mobile or Sencha Touch, this allows a smartphone app to be developed with just HTML, CSS, and JavaScript. ...

  • PhoneGap
    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. ...

Create React Native App alternatives & related posts

Expo logo

Expo

602
657
66
Build one project that runs natively on all your users' devices
602
657
+ 1
66
PROS OF EXPO
  • 15
    Free
  • 13
    Hot Reload
  • 9
    Easy to learn
  • 9
    Common ios and android app setup
  • 6
    Open Source
  • 6
    Streamlined
  • 5
    Builds into a React Native app
  • 2
    PWA supported
  • 1
    Plugins for web use with Next.js
CONS OF EXPO
    Be the first to leave a con

    related Expo posts

    Vishal Narkhede
    Javascript Developer at getStream.io · | 19 upvotes · 435.8K views

    Recently, the team at Stream published a React Native SDK for our new Chat by Stream product. React Native brings the power of JavaScript to the world of mobile development, making it easy to develop apps for multiple platforms. We decided to publish two different endpoints for the SDK – Expo and React Native (non-expo), to avoid the hurdle and setup of using the Expo library in React Native only projects on the consumer side.

    The capability of style customization is one a large deal breaker for frontend SDKs. To solve this, we decided to use styled-components in our SDK, which makes it easy to add support for themes on top of our existing components. This practice reduces the maintenance effort for stylings of custom components and keeps the overall codebase clean.

    For module bundling, we decided to go with Rollup.js instead of Webpack due to its simplicity and performance in the area of library/module providers. We are using Babel for transpiling code, enabling our team to use JavaScript's next-generation features. Additionally, we are using the React Styleguidist component documentation, which makes documenting the React Native code a breeze.

    See more
    Sezgi Ulucam
    Developer Advocate at Hasura · | 7 upvotes · 906.6K views

    I've recently switched to using Expo for initializing and developing my React Native apps. Compared to React Native CLI, it's so much easier to get set up and going. Setting up and maintaining Android Studio, Android SDK, and virtual devices used to be such a headache. Thanks to Expo, I can now test my apps directly on my Android phone, just by installing the Expo app. I still use Xcode Simulator for iOS testing, since I don't have an iPhone, but that's easy anyway. The big win for me with Expo is ease of Android testing.

    The Expo SDK also provides convenient features like Facebook login, MapView, push notifications, and many others. https://docs.expo.io/versions/v31.0.0/sdk/

    See more
    React Native logo

    React Native

    32.5K
    28.2K
    1.1K
    A framework for building native apps with React
    32.5K
    28.2K
    + 1
    1.1K
    PROS OF REACT NATIVE
    • 210
      Learn once write everywhere
    • 170
      Cross platform
    • 166
      Javascript
    • 121
      Native ios components
    • 68
      Built by facebook
    • 65
      Easy to learn
    • 44
      Bridges me into ios development
    • 39
      It's just react
    • 39
      No compile
    • 36
      Declarative
    • 22
      Fast
    • 13
      Virtual Dom
    • 12
      Insanely fast develop / test cycle
    • 12
      Livereload
    • 11
      Great community
    • 9
      It is free and open source
    • 9
      Native android components
    • 9
      Easy setup
    • 9
      Backed by Facebook
    • 7
      Highly customizable
    • 7
      Scalable
    • 6
      Awesome
    • 6
      Everything component
    • 6
      Great errors
    • 6
      Win win solution of hybrid app
    • 5
      Not dependent on anything such as Angular
    • 5
      Simple
    • 4
      Awesome, easy starting from scratch
    • 4
      OTA update
    • 3
      As good as Native without any performance concerns
    • 3
      Easy to use
    • 2
      Many salary
    • 2
      Can be incrementally added to existing native apps
    • 2
      Hot reload
    • 2
      Over the air update (Flutter lacks)
    • 2
      'It's just react'
    • 2
      Web development meets Mobile development
    • 1
      Ngon
    CONS OF REACT NATIVE
    • 23
      Javascript
    • 19
      Built by facebook
    • 12
      Cant use CSS
    • 4
      30 FPS Limit
    • 2
      Slow
    • 2
      Generate large apk even for a simple app
    • 2
      Some compenents not truly native

    related React Native posts

    Vaibhav Taunk
    Team Lead at Technovert · | 31 upvotes · 3.6M views

    I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

    See more

    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
    Create React App logo

    Create React App

    1K
    992
    4
    Create React apps with no build configuration
    1K
    992
    + 1
    4
    PROS OF CREATE REACT APP
    • 2
      No config, easy to use
    • 2
      Maintained by React core team
    CONS OF CREATE REACT APP
    • 1
      No SSR

    related Create React App posts

    Adebayo Akinlaja
    Engineering Manager at Andela · | 30 upvotes · 3.2M views

    I picked up an idea to develop and it was no brainer I had to go with React for the frontend. I was faced with challenges when it came to what component framework to use. I had worked extensively with Material-UI but I needed something different that would offer me wider range of well customized components (I became pretty slow at styling). I brought in Evergreen after several sampling and reads online but again, after several prototype development against Evergreen—since I was using TypeScript and I had to import custom Type, it felt exhaustive. After I validated Evergreen with the designs of the idea I was developing, I also noticed I might have to do a lot of styling. I later stumbled on Material Kit, the one specifically made for React . It was promising with beautifully crafted components, most of which fits into the designs pages I had on ground.

    A major problem of Material Kit for me is it isn't written in TypeScript and there isn't any plans to support its TypeScript version. I rolled up my sleeve and started converting their components to TypeScript and if you'll ask me, I am still on it.

    In summary, I used the Create React App with TypeScript support and I am spending some time converting Material Kit to TypeScript before I start developing against it. All of these components are going to be hosted on Bit.

    If you feel I am crazy or I have gotten something wrong, I'll be willing to listen to your opinion. Also, if you want to have a share of whatever TypeScript version of Material Kit I end up coming up with, let me know.

    See more

    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
    Flutter logo

    Flutter

    15.8K
    15.6K
    1.2K
    Cross-platform mobile framework from Google
    15.8K
    15.6K
    + 1
    1.2K
    PROS OF FLUTTER
    • 141
      Hot Reload
    • 119
      Cross platform
    • 103
      Performance
    • 89
      Backed by Google
    • 72
      Compiled into Native Code
    • 59
      Fast Development
    • 58
      Open Source
    • 53
      Fast Prototyping
    • 49
      Single Codebase
    • 48
      Expressive and Flexible UI
    • 36
      Reactive Programming
    • 34
      Material Design
    • 30
      Dart
    • 29
      Widget-based
    • 26
      Target to Fuchsia
    • 20
      IOS + Android
    • 17
      Easy to learn
    • 16
      Great CLI Support
    • 14
      You can use it as mobile, web, Server development
    • 14
      Tooling
    • 13
      Debugging quickly
    • 13
      Have built-in Material theme
    • 12
      Target to Android
    • 12
      Community
    • 12
      Good docs & sample code
    • 11
      Support by multiple IDE: Android Studio, VS Code, XCode
    • 10
      Written by Dart, which is easy to read code
    • 10
      Easy Testing Support
    • 9
      Real platform free framework of the future
    • 9
      Have built-in Cupertino theme
    • 9
      Target to iOS
    • 8
      Easy to Unit Test
    • 8
      Easy to Widget Test
    • 1
      Large Community
    CONS OF FLUTTER
    • 29
      Need to learn Dart
    • 10
      Lack of community support
    • 10
      No 3D Graphics Engine Support
    • 8
      Graphics programming
    • 6
      Lack of friendly documentation
    • 2
      Lack of promotion
    • 1
      Https://iphtechnologies.com/difference-between-flutter

    related Flutter posts

    Vaibhav Taunk
    Team Lead at Technovert · | 31 upvotes · 3.6M views

    I am starting to become a full-stack developer, by choosing and learning .NET Core for API Development, Angular CLI / React for UI Development, MongoDB for database, as it a NoSQL DB and Flutter / React Native for Mobile App Development. Using Postman, Markdown and Visual Studio Code for development.

    See more

    The only two programming languages I know are Python and Dart, I fall in love with Dart when I learned about the type safeness, ease of refactoring, and the help of the IDE. I have an idea for an app, a simple app, but I need SEO and server rendering, and I also want it to be available on all platforms. I can't use Flutter or Dart anymore because of that. I have been searching and looks like there is no way to avoid learning HTML and CSS for this. I want to use Supabase as BASS, at the moment I think that I have two options if I want to learn the least amount of things because of my lack of time available:

    1. Quasar Framework: They claim that I can do all the things I need, but I have to use JavaScript, and I am going to have all those bugs with a type-safe programming language avoidable. I guess I can use TypeScript?, but that means learning both, and I am not sure if I will be able to use 100% Typescript. Besides Vue.js, Node.js, etc.

    2. Blazor and .NET: There is MAUI with razor bindings in .Net now, and also a Blazor server. And as far as I can see, the transition from Dart to C# will be easy. I guess that I have to learn some Javascript here and there, but I have to less things I guess, am I wrong? But Blazor is a new technology, Vue is widely used.

    See more
    Ionic logo

    Ionic

    9.3K
    8.4K
    1.8K
    A beautiful front-end framework for developing cross-platform apps with web technologies like Angular and React.
    9.3K
    8.4K
    + 1
    1.8K
    PROS OF IONIC
    • 248
      Allows for rapid prototyping
    • 228
      Hybrid mobile
    • 208
      It's angularjs
    • 186
      Free
    • 179
      It's javascript, html, and css
    • 109
      Ui and theming
    • 78
      Great designs
    • 74
      Mv* pattern
    • 71
      Reuse frontend devs on mobile
    • 65
      Extensibility
    • 31
      Great community
    • 29
      Open source
    • 23
      Responsive design
    • 21
      Good cli
    • 14
      So easy to use
    • 13
      Angularjs-based
    • 13
      Beautifully designed
    • 12
      Widgets
    • 11
      Allows for rapid prototyping, hybrid mobile
    • 11
      Typescript
    • 10
      Quick prototyping, amazing community
    • 10
      Easy setup
    • 8
      Angular2 support
    • 7
      Fast, easy, free
    • 7
      Because of the productivity and easy for development
    • 7
      Base on angular
    • 7
      So much thought behind what developers actually need
    • 6
      Super fast, their dev team is amazingly passionate
    • 6
      Easy to use
    • 6
      It's Angular
    • 4
      UI is awesome
    • 4
      Hot deploy
    • 3
      Material design support using theme
    • 3
      Amazing support
    • 3
      It's the future
    • 3
      Angular
    • 3
      Allow for rapid prototyping
    • 3
      Easy setup, development and testing
    • 3
      Ionic creator
    • 2
      User Friendly
    • 2
      It's angular js
    • 2
      Complete package
    • 2
      Simple & Fast
    • 2
      Fastest growing mobile app framework
    • 2
      Best Support and Community
    • 2
      Material Design By Default
    • 2
      Cross platform
    • 2
      Documentation
    • 2
      Because I can use my existing web devloper skills
    • 2
      Removes 300ms delay in mobile browsers
    • 1
      Responsive
    • 1
      Native access
    • 1
      Typescript support
    • 1
      Ionic conect codeigniter
    • 1
      Fast Prototyping
    • 1
      All Trending Stack
    CONS OF IONIC
    • 20
      Not suitable for high performance or UI intensive apps
    • 15
      Not meant for game development
    • 2
      Not a native app

    related Ionic posts

    Bhupendra Madhu
    Web Developer at Ecombooks · | 8 upvotes · 509.9K views

    I want to learn cross-platform application frameworks like React Native, Flutter, Xamarin, or Ionic, and I'm a web developer. I can learn other programming languages as well. But I'm confused about what to learn, which framework is best, and which framework will last long as the application grows further into complexity.

    See more
    Saber Hosney
    Senior software engineer at Shortcut · | 7 upvotes · 264.2K views

    Greetings!

    I have been searching lately for frameworks to build mobile apps.

    We are trying to make something like a quiz app as a way for customers to contact us. I considered Ionic and React Native because we use JavaScript most of the time in websites, e.g., Vue.js/Nuxt.js. But Flutter seems a decent choice as well, especially since you can use Android/iOS-like components. We are looking for something that works in the long term, something that's time and cost-effective, especially when paired with backend services like Firebase or a GraphQL server. I would like to know your opinions and recommendations. Thank you!

    See more
    Xamarin logo

    Xamarin

    1.3K
    1.5K
    785
    Create iOS, Android and Mac apps in C#
    1.3K
    1.5K
    + 1
    785
    PROS OF XAMARIN
    • 121
      Power of c# on mobile devices
    • 81
      Native performance
    • 79
      Native apps with native ui controls
    • 73
      No javascript - truely compiled code
    • 67
      Sharing more than 90% of code over all platforms
    • 45
      Ability to leverage visual studio
    • 44
      Mvvm pattern
    • 44
      Many great c# libraries
    • 36
      Amazing support
    • 34
      Powerful platform for .net developers
    • 19
      GUI Native look and Feel
    • 16
      Nuget package manager
    • 12
      Free
    • 9
      Backed by Microsoft
    • 9
      Enables code reuse on server
    • 8
      Faster Development
    • 7
      Use of third-party .NET libraries
    • 7
      It's free since Apr 2016
    • 7
      Best performance than other cross-platform
    • 7
      Easy Debug and Trace
    • 7
      Open Source
    • 6
      Mac IDE (Xamarin Studio)
    • 6
      Xamarin.forms is the best, it's amazing
    • 5
      That just work for every scenario
    • 5
      C# mult paradigm language
    • 5
      Power of C#, no javascript, visual studio
    • 4
      Great docs
    • 4
      Compatible to develop Hybrid apps
    • 4
      Microsoft stack
    • 4
      Microsoft backed
    • 3
      Well Designed
    • 3
      Small learning curve for Mobile developers
    • 2
      Ionic
    • 2
      Ability to leverage legacy C and C++
    CONS OF XAMARIN
    • 9
      Build times
    • 5
      Visual Studio
    • 4
      Price
    • 3
      Complexity
    • 3
      Scalability
    • 2
      Nuget
    • 2
      Maturity
    • 2
      Build Tools
    • 2
      Support
    • 0
      Maturidade
    • 0
      Performance

    related Xamarin posts

    Greg Neumann
    Indie, Solo, Developer · | 8 upvotes · 1.4M views

    Finding the most effective dev stack for a solo developer. Over the past year, I've been looking at many tech stacks that would be 'best' for me, as a solo, indie, developer to deliver a desktop app (Windows & Mac) plus mobile - iOS mainly. Initially, Xamarin started to stand-out. Using .NET Core as the run-time, Xamarin as the native API provider and Xamarin Forms for the UI seemed to solve all issues. But, the cracks soon started to appear. Xamarin Forms is mobile only; the Windows incarnation is different. There is no Mac UI solution (you have to code it natively in Mac OS Storyboard. I was also worried how Xamarin Forms , if I was to use it, was going to cope, in future, with Apple's new SwiftUI and Google's new Fuchsia.

    This plethora of techs for the UI-layer made me reach for the safer waters of using Web-techs for the UI. Lovely! Consistency everywhere (well, mostly). But that consistency evaporates when platform issues are addressed. There are so many web frameworks!

    But, I made a simple decision. It's just me...I am clever, but there is no army of coders here. And I have big plans for a business app. How could just 1 developer go-on to deploy a decent app to Windows, iPhone, iPad & Mac OS? I remembered earlier days when I've used Microsoft's ASP.NET to scaffold - generate - loads of Code for a web-app that I needed for several charities that I worked with. What 'generators' exist that do a lot of the platform-specific rubbish, allow the necessary customisation of such platform integration and provide a decent UI?

    I've placed my colours to the Quasar Framework mast. Oh dear, that means Electron desktop apps doesn't it? Well, Ive had enough of loads of Developers saying that "the menus won't look native" or "it uses too much RAM" and so on. I've been using non-native UI-wrapped apps for ages - the date picker in Outlook on iOS is way better than the native date-picker and I'd been using it for years without getting hot under the collar about it. Developers do get so hung-up on things that busy Users hardly notice; don't you think?. As to the RAM usage issue; that's a bit true. But Users only really notice when an app uses so much RAM that the machine starts to page-out. Electron contributes towards that horizon but does not cause it. My Users will be business-users after all. Somewhat decent machines.

    Looking forward to all that lovely Vue.js around my TypeScript and all those really, really, b e a u t I f u l UI controls of Quasar Framework . Still not sure that 1 dev can deliver all that... but I'm up for trying...

    See more
    Bhupendra Madhu
    Web Developer at Ecombooks · | 8 upvotes · 509.9K views

    I want to learn cross-platform application frameworks like React Native, Flutter, Xamarin, or Ionic, and I'm a web developer. I can learn other programming languages as well. But I'm confused about what to learn, which framework is best, and which framework will last long as the application grows further into complexity.

    See more
    Apache Cordova logo

    Apache Cordova

    701
    891
    216
    Platform for building native mobile applications using HTML, CSS and JavaScript
    701
    891
    + 1
    216
    PROS OF APACHE CORDOVA
    • 47
      Lots of plugins
    • 35
      JavaScript
    • 26
      Great community
    • 24
      Easy Development
    • 18
      Easy to learn
    • 15
      Cross platform
    • 7
      Open Source
    • 6
      Easy, fast, not buggy in my experience with my code
    • 6
      Lots of descendants; PhoneGap, Ionic, Intel XDA etc
    • 4
      Can use CSS3
    • 4
      Rich HTML 5
    • 4
      Easy debugging
    • 3
      HTML, CSS and JS
    • 3
      Fast and hot reload
    • 3
      Rich css ui
    • 3
      Use what you code in your browser
    • 2
      Need a light system
    • 2
      Native Web Technologies
    • 2
      Without extra tooling needed
    • 2
      One code base everywhere
    CONS OF APACHE CORDOVA
    • 2
      No native performance
    • 1
      Hard to install
    • 0
      Hard to install

    related Apache Cordova posts

    Jonathan Pugh
    Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 2.8M views

    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

    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
    PhoneGap logo

    PhoneGap

    580
    682
    94
    Easilily create mobile apps using HTML, CSS, and JavaScript
    580
    682
    + 1
    94
    PROS OF PHONEGAP
    • 46
      Javascript
    • 13
      Backed by Adobe
    • 11
      Free
    • 9
      Easy and developer friendly
    • 6
      Support more platforms
    • 3
      It's javascript, html, and css
    • 2
      Common code base across all mobile platform
    • 1
      Not bound to specific framework
    • 1
      Powerful Framework
    • 1
      Runs on mobile browser
    • 1
      Similar UI across all platform
    • 0
      Free easy fast and not buggy in my experience
    CONS OF PHONEGAP
    • 2
      Never as good as a native app
    • 1
      Created for web pages, not for complex Apps
    • 1
      Poor user experience
    • 1
      Not build for high performance
    • 1
      Hard to see

    related PhoneGap posts

    Jonathan Pugh
    Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 2.8M views

    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
    Sezgi Ulucam
    Developer Advocate at Hasura · | 6 upvotes · 429.5K views

    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