Alternatives to Xamarin Forms logo

Alternatives to Xamarin Forms

React Native, Flutter, Android Studio, Android SDK, and Ionic are the most popular alternatives and competitors to Xamarin Forms.
290
259
+ 1
5

What is Xamarin Forms and what are its top alternatives?

A mobile application framework for building user interfaces.It easily create native user interface layouts that can be shared across Android, iOS, and Windows Phone.
Xamarin Forms is a tool in the Cross-Platform Mobile Development category of a tech stack.

Top Alternatives to Xamarin Forms

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

  • Flutter
    Flutter

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

  • Android Studio
    Android Studio

    Android Studio is a new Android development environment based on IntelliJ IDEA. It provides new features and improvements over Eclipse ADT and will be the official Android IDE once it's ready. ...

  • Android SDK
    Android SDK

    Android provides a rich application framework that allows you to build innovative apps and games for mobile devices in a Java language environment. ...

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

Xamarin Forms alternatives & related posts

React Native logo

React Native

27.7K
24.2K
1.1K
A framework for building native apps with React
27.7K
24.2K
+ 1
1.1K
PROS OF REACT NATIVE
  • 207
    Learn once write everywhere
  • 168
    Cross platform
  • 165
    Javascript
  • 120
    Native ios components
  • 67
    Built by facebook
  • 63
    Easy to learn
  • 44
    Bridges me into ios development
  • 40
    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
  • 18
    Built by facebook
  • 12
    Cant use CSS
  • 4
    30 FPS Limit
  • 2
    Generate large apk even for a simple app
  • 2
    Some compenents not truly native
  • 2
    Slow

related React Native posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 2.1M 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
Flutter logo

Flutter

11.9K
12.1K
1.1K
Cross-platform mobile framework from Google
11.9K
12.1K
+ 1
1.1K
PROS OF FLUTTER
  • 127
    Hot Reload
  • 106
    Cross platform
  • 98
    Performance
  • 82
    Backed by Google
  • 69
    Compiled into Native Code
  • 54
    Fast Development
  • 54
    Open Source
  • 49
    Fast Prototyping
  • 44
    Expressive and Flexible UI
  • 43
    Single Codebase
  • 35
    Reactive Programming
  • 31
    Material Design
  • 26
    Widget-based
  • 25
    Dart
  • 24
    Target to Fuchsia
  • 17
    IOS + Android
  • 14
    Easy to learn
  • 14
    Great CLI Support
  • 13
    Tooling
  • 13
    You can use it as mobile, web, Server development
  • 12
    Have built-in Material theme
  • 11
    Target to Android
  • 11
    Good docs & sample code
  • 11
    Community
  • 11
    Debugging quickly
  • 10
    Support by multiple IDE: Android Studio, VS Code, XCode
  • 9
    Easy Testing Support
  • 9
    Written by Dart, which is easy to read code
  • 8
    Target to iOS
  • 8
    Real platform free framework of the future
  • 8
    Have built-in Cupertino theme
  • 7
    Easy to Unit Test
  • 7
    Easy to Widget Test
CONS OF FLUTTER
  • 28
    Need to learn Dart
  • 10
    No 3D Graphics Engine Support
  • 9
    Lack of community support
  • 7
    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 · 2.1M 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
Shared insights
on
DartDartFlutterFlutter

Hi, I'm considering building a social marketplace app on android, ios and web, Flutter seems to be a good UI framework for cross-platform apps, it's safe type, hot reload, and native compiling on native machine code (thanks to Dart). My question is, for an MVP product is it a good choice? if yes, will it be on the mid-term, long term? Or will I have to change as the users grow?

thank you

See more
Android Studio logo

Android Studio

21.6K
16.9K
355
Android development environment based on IntelliJ IDEA
21.6K
16.9K
+ 1
355
PROS OF ANDROID STUDIO
  • 173
    Android studio is a great tool, getting better and bet
  • 101
    Google's official android ide
  • 36
    Intelligent code editor with lots of auto-completion
  • 25
    Its powerful and robust
  • 5
    Easy creating android app
  • 3
    Amazing Layout Designer
  • 3
    Great Code Tips
  • 3
    Great tool & very helpful
  • 2
    Easy to use
  • 2
    Built in Emulator
  • 2
    Keyboard Shortcuts are Amazing Out of the box
CONS OF ANDROID STUDIO
  • 4
    Slow emulator
  • 4
    Huge memory usage
  • 2
    Complex for begginers
  • 2
    No checking incompatibilities
  • 1
    Using Intellij IDEA, while Intellij IDEA have too
  • 1
    Lags behind IntelliJ IDEA
  • 1
    Slow release process

related Android Studio posts

Gustavo Muñoz
Senior Software Engineer at JOOR · | 8 upvotes · 413.8K views

In my modest opinion, Flutter is the future of mobile development. The framework is as important to mobile as React is to the web. And seeing that React Native does not finish taking off, I am focusing all my efforts on learning Flutter and Dart. The ecosystem is amazing. The community is crazy about Flutter. There are enough resources to learn and enjoy the framework, and the tools developed to work with it are amazing. Android Studio or Visual Studio Code has incredible plugins and Dart is a pretty straight forward and easy-to-learn language, even more, if you came from JavaScript. I admit it. I'm in love with Flutter. When you are not a designer, having a framework focused on design an pretty things is a must. And counting with tools like #flare for animations makes everything easier. It is so amazing that I wish I had a big mobile project right now at work just to use Flutter.

See more
Julien DeFrance
Principal Software Engineer at Tophatter · | 8 upvotes · 383.6K views

As a Engineering Manager & Director at SmartZip, I had a mix of front-end, back-end, #mobile engineers reporting to me.

Sprints after sprints, I noticed some inefficiencies on the MobileDev side. People working multiple sprints in a row on their Xcode / Objective-C codebase while some others were working on Android Studio. After which, QA & Product ensured both applications were in sync, on a UI/UX standpoint, creating addional work, which also happened to be extremely costly.

Our resources being so limited, my role was to stop this bleeding and keep my team productive and their time, valuable.

After some analysis, discussions, proof of concepts... etc. We decided to move to a single codebase using React Native so our velocity would increase.

After some initial investment, our initial assumptions were confirmed and we indeed started to ship features a lot faster than ever before. Also, our engineers found a way to perform this upgrade incrementally, so the initial platform-specific codebase wouldn't have to entirely be rewritten at once but only gradually and at will.

Feedback around React Native was very positive. And I doubt - for the kind of application we had - no one would want to go back to two or more code bases. Our application was still as Native as it gets. And no feature or device capability was compromised.

See more
Android SDK logo

Android SDK

22.8K
17.7K
787
An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps...
22.8K
17.7K
+ 1
787
PROS OF ANDROID SDK
  • 285
    Android development
  • 154
    Necessary for android
  • 127
    Android studio
  • 85
    Mobile framework
  • 81
    Backed by google
  • 26
    Platform-tools
  • 21
    Eclipse + adt plugin
  • 4
    Powerful, simple, one stop environment
  • 2
    Больно
  • 2
    Free
CONS OF ANDROID SDK
    Be the first to leave a con

    related Android SDK posts

    Jesus Dario Rivera Rubio
    Telecomm Engineering at Netbeast · | 10 upvotes · 917K views

    We are using React Native in #SmartHome to share the business logic between Android and iOS team and approach users with a unique brand experience. The drawback is that we require lots of native Android SDK and Objective-C modules, so a good part of the invested time is there. The gain for a app that relies less on native communication, sensors and OS tools should be even higher.

    Also it helps us set different testing stages: we use Travis CI for the javascript (business logic), Bitrise to run build tests and @Detox for #end2end automated user tests.

    We use a microservices structure on top of Zeit's @now that read from firebase. We use JWT auth to authenticate requests among services and from users, following GitHub philosophy of using the same infrastructure than its API consumers. Firebase is used mainly as a key-value store between services and as a backup database for users. We also use its authentication mechanisms.

    You can be super locked-in if you also rely on it's analytics, but we use Amplitude for that, which offers us great insights. Intercom for communications with end-user and Mailjet for marketing.

    See more
    Sezgi Ulucam
    Developer Advocate at Hasura · | 7 upvotes · 775.5K 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
    Ionic logo

    Ionic

    8.3K
    7.6K
    1.7K
    A beautiful front-end framework for developing cross-platform apps with web technologies like Angular and React.
    8.3K
    7.6K
    + 1
    1.7K
    PROS OF IONIC
    • 246
      Allows for rapid prototyping
    • 227
      Hybrid mobile
    • 208
      It's angularjs
    • 185
      Free
    • 179
      It's javascript, html, and css
    • 108
      Ui and theming
    • 76
      Great designs
    • 74
      Mv* pattern
    • 70
      Reuse frontend devs on mobile
    • 65
      Extensibility
    • 31
      Great community
    • 29
      Open source
    • 22
      Responsive design
    • 20
      Good cli
    • 13
      So easy to use
    • 13
      Beautifully designed
    • 13
      Angularjs-based
    • 12
      Widgets
    • 11
      Typescript
    • 11
      Allows for rapid prototyping, hybrid mobile
    • 10
      Quick prototyping, amazing community
    • 10
      Easy setup
    • 8
      Angular2 support
    • 7
      Base on angular
    • 7
      So much thought behind what developers actually need
    • 7
      Because of the productivity and easy for development
    • 7
      Fast, easy, free
    • 6
      Super fast, their dev team is amazingly passionate
    • 6
      Easy to use
    • 6
      It's Angular
    • 4
      Hot deploy
    • 4
      UI is awesome
    • 3
      Amazing support
    • 3
      Easy setup, development and testing
    • 3
      Material design support using theme
    • 3
      It's the future
    • 3
      Angular
    • 3
      Allow for rapid prototyping
    • 3
      Ionic creator
    • 2
      User Friendly
    • 2
      It's angular js
    • 2
      Complete package
    • 2
      Simple & Fast
    • 2
      Removes 300ms delay in mobile browsers
    • 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
    • 1
      Ionic conect codeigniter
    • 1
      Fast Prototyping
    • 1
      All Trending Stack
    • 1
      Native access
    • 1
      Typescript support
    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

    Saber Hosney
    Senior software engineer at Shortcut · | 7 upvotes · 152.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
    Melanie Verstraete
    Shared insights
    on
    IonicIonicFlutterFlutter

    Hi community, I am looking into how I should build my tech stack for a business/analytics platform. I am not very familiar with frontend development; when looking into cross-platform frameworks, I found a lot of options. What is the best cross-platform frontend framework to go with? I found Flutter interesting, but Ionic also looks promising? Thank you for the advice!

    See more
    Xamarin logo

    Xamarin

    1.2K
    1.5K
    783
    Create iOS, Android and Mac apps in C#
    1.2K
    1.5K
    + 1
    783
    PROS OF XAMARIN
    • 121
      Power of c# on mobile devices
    • 81
      Native performance
    • 78
      Native apps with native ui controls
    • 72
      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
      Enables code reuse on server
    • 9
      Backed by Microsoft
    • 8
      Faster Development
    • 7
      Best performance than other cross-platform
    • 7
      Use of third-party .NET libraries
    • 7
      Easy Debug and Trace
    • 7
      Open Source
    • 7
      It's free since Apr 2016
    • 6
      Xamarin.forms is the best, it's amazing
    • 6
      Mac IDE (Xamarin Studio)
    • 5
      That just work for every scenario
    • 5
      Power of C#, no javascript, visual studio
    • 5
      C# mult paradigm language
    • 4
      Microsoft stack
    • 4
      Great docs
    • 4
      Compatible to develop Hybrid apps
    • 4
      Microsoft backed
    • 3
      Small learning curve for Mobile developers
    • 3
      Well Designed
    • 2
      Ability to leverage legacy C and C++
    • 2
      Ionic
    CONS OF XAMARIN
    • 9
      Build times
    • 5
      Visual Studio
    • 3
      Complexity
    • 3
      Scalability
    • 3
      Price
    • 2
      Nuget
    • 2
      Maturity
    • 2
      Build Tools
    • 2
      Support
    • 0
      Maturidade
    • 0
      Performance

    related Xamarin posts

    Greg Neumann

    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
    William Miller

    We are developing an AWS IoT app for large boats. The IoT devices have sensors all over the boat for engine oil pressure, position, water depth, fuel level, crew location, etc. When the boat has internet, we interact with AWS cloud using lambda and Amazon DynamoDB. When the boat is offshore, the captain and crew still need normal and emergency alerts and real-time sensor information. The crew might have an Android or IoS phone or a Windows or macOS PC to receive alerts and interact with sensors. We may use the AWS GreenGrasss edge computing solution and either MQTT or HTML for that function.

    Question: We want to develop a cross-platform client to run on Windows, Mac, Android, IOS, and possibly Linux. We are primarily Python programmers, so PyQt or Kivy are options for us, but we have heard good things about React Native, Flutter, Xamarin, and others. We think an AWS Greengrass core on an RPI4 could communicate to the client with MQTT or a local webserver with a client web interface.

    Any thoughts would be much appreciated.

    See more
    Apache Cordova logo

    Apache Cordova

    693
    866
    212
    Platform for building native mobile applications using HTML, CSS and JavaScript
    693
    866
    + 1
    212
    PROS OF APACHE CORDOVA
    • 45
      Lots of plugins
    • 34
      JavaScript
    • 26
      Great community
    • 23
      Easy Development
    • 18
      Easy to learn
    • 15
      Cross platform
    • 7
      Open Source
    • 6
      Lots of descendants; PhoneGap, Ionic, Intel XDA etc
    • 6
      Easy, fast, not buggy in my experience with my code
    • 4
      Can use CSS3
    • 4
      Rich HTML 5
    • 4
      Easy debugging
    • 3
      Rich css ui
    • 3
      Fast and hot reload
    • 3
      HTML, CSS and JS
    • 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
    • 0
      44
    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 · 1.9M 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

    572
    668
    94
    Easilily create mobile apps using HTML, CSS, and JavaScript
    572
    668
    + 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 · 1.9M 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 · 396.8K 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