Alternatives to Xamarin logo

Alternatives to Xamarin

React Native, Ionic, Flutter, NativeScript, and PhoneGap are the most popular alternatives and competitors to Xamarin.
1.1K
1.2K
+ 1
758

What is Xamarin and what are its top alternatives?

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.
Xamarin is a tool in the Cross-Platform Mobile Development category of a tech stack.
Xamarin is an open source tool with GitHub stars and GitHub forks. Here’s a link to Xamarin's open source repository on GitHub

Top Alternatives to Xamarin

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

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

  • Flutter

    Flutter

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

  • NativeScript

    NativeScript

    NativeScript enables developers to build native apps for iOS, Android and Windows Universal while sharing the application code across the platforms. When building the application UI, developers use our libraries, which abstract the differences between the native platforms. ...

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

  • Swift

    Swift

    Writing code is interactive and fun, the syntax is concise yet expressive, and apps run lightning-fast. Swift is ready for your next iOS and OS X project — or for addition into your current app — because Swift code works side-by-side with Objective-C. ...

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

  • Appcelerator

    Appcelerator

    Appcelerator is the first mobile platform to combine the flexibility of open source development technologies with the power of cloud services. ...

Xamarin alternatives & related posts

React Native logo

React Native

18.7K
15.7K
1.1K
A framework for building native apps with React
18.7K
15.7K
+ 1
1.1K
PROS OF REACT NATIVE
  • 196
    Learn once write everywhere
  • 158
    Cross platform
  • 157
    Javascript
  • 114
    Native ios components
  • 65
    Built by facebook
  • 59
    Easy to learn
  • 43
    Bridges me into ios development
  • 39
    No compile
  • 38
    It's just react
  • 36
    Declarative
  • 19
    Fast
  • 12
    Livereload
  • 11
    Virtual Dom
  • 10
    Insanely fast develop / test cycle
  • 9
    Backed by Facebook
  • 8
    Native android components
  • 8
    It is free and open source
  • 8
    Easy setup
  • 8
    Great community
  • 7
    Highly customizable
  • 6
    Awesome
  • 6
    Scalable
  • 6
    Great errors
  • 6
    Win win solution of hybrid app
  • 6
    Everything component
  • 5
    Not dependent on anything such as Angular
  • 5
    Simple
  • 4
    OTA update
  • 4
    Awesome, easy starting from scratch
  • 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
  • 0
    Ful
  • 0
    Nigger
CONS OF REACT NATIVE
  • 22
    Javascript
  • 17
    Built by facebook
  • 11
    Cant use CSS
  • 2
    Some compenents not truly native

related React Native posts

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

Ionic

6.4K
5.7K
1.7K
A beautiful front-end framework for developing cross-platform apps with web technologies like Angular and React.
6.4K
5.7K
+ 1
1.7K
PROS OF IONIC
  • 245
    Allows for rapid prototyping
  • 225
    Hybrid mobile
  • 208
    It's angularjs
  • 183
    Free
  • 178
    It's javascript, html, and css
  • 108
    Ui and theming
  • 76
    Great designs
  • 74
    Mv* pattern
  • 70
    Reuse frontend devs on mobile
  • 64
    Extensibility
  • 31
    Great community
  • 28
    Open source
  • 22
    Responsive design
  • 20
    Good cli
  • 13
    Angularjs-based
  • 13
    Beautifully designed
  • 13
    So easy to use
  • 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
    So much thought behind what developers actually need
  • 7
    Base on angular
  • 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
    1
  • 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
  • 1
    Not a native app

related Ionic posts

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
Gaurav Patil
Software Developer at PLMTECH LOGIX Pvt. Ltd. · | 3 upvotes · 382.2K views

Which hybrid framework I should for my upcoming mobile application project?

Options: 1. Flutter 2. Ionic 3. React Native

See more
Flutter logo

Flutter

4.7K
5.1K
730
Cross-platform mobile framework from Google
4.7K
5.1K
+ 1
730
PROS OF FLUTTER
  • 92
    Hot Reload
  • 77
    Cross platform
  • 72
    Performance
  • 63
    Backed by Google
  • 53
    Compiled into Native Code
  • 40
    Open Source
  • 36
    Fast Prototyping
  • 34
    Expressive and Flexible UI
  • 34
    Fast Development
  • 28
    Single Codebase
  • 26
    Reactive Programming
  • 18
    Material Design
  • 15
    Widget-based
  • 15
    Dart
  • 15
    Target to Fuchsia
  • 11
    Great CLI Support
  • 10
    IOS + Android
  • 9
    Tooling
  • 7
    Debugging quickly
  • 7
    Easy to learn
  • 7
    Have built-in Material theme
  • 7
    Target to Android
  • 7
    You can use it as mobile, web, Server development
  • 6
    Support by multiple IDE: Android Studio, VS Code, XCode
  • 6
    Target to iOS
  • 6
    Easy Testing Support
  • 5
    Have built-in Cupertino theme
  • 5
    Good docs & sample code
  • 4
    Easy to Widget Test
  • 4
    Written by Dart, which is easy to read code
  • 4
    Easy to Unit Test
  • 4
    Community
  • 3
    Real platform free framework of the future
CONS OF FLUTTER
  • 22
    Need to learn Dart
  • 9
    Lack of community support
  • 8
    No 3D Graphics Engine Support
  • 5
    Lack of friendly documentation
  • 4
    Graphics programming
  • 2
    Lack of promotion
  • 1
    Https://iphtechnologies.com/difference-between-flutter

related Flutter posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.3M 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've been juggling with an app idea and am clueless about how to build it.

A little about the app:

  • Social network type app ,
  • Users can create different directories, in those directories post images and/or text that'll be shared on a public dashboard .

Directory creation is the main point of this app. Besides there'll be rooms(groups),chatting system, search operations similar to instagram,push notifications

I have two options:

  1. React Native, Python, AWS stack or
  2. Flutter, Go ( I don't know what stack or tools to use)
See more
NativeScript logo

NativeScript

480
917
496
Build truly native apps with JavaScript
480
917
+ 1
496
PROS OF NATIVESCRIPT
  • 73
    Access to the entire native api
  • 46
    Support for native ios and android libraries
  • 45
    Support for javascript libraries
  • 45
    Angular 2.0 support
  • 43
    Native ux and performance
  • 36
    Typescript support
  • 34
    Backed up by google and telerik
  • 29
    Css support
  • 26
    Cross-platform declarative ui and code
  • 24
    Fully open source under apache 2.0 license
  • 11
    Vuejs support
  • 8
    60fps performance
  • 5
    Powerful data visualization with native UI
  • 5
    VS Code integration
  • 4
    Cloud builds as part of Telerik PLatform
  • 4
    Angular, typescript and javascript support
  • 4
    No need for Mac to build iOS apps in Telerik Platform
  • 4
    Extended CLI support
  • 3
    On-device debugging
  • 3
    Extensibility
  • 3
    Truly Object-Oriented with Typescript
  • 3
    Easiest of all other frameworks
  • 3
    Backed by google
  • 3
    0 day support for new OS updates
  • 3
    Publishing modules to NPM
  • 2
    Access to entire native api
  • 2
    VueJS support
  • 2
    Svelte support
  • 2
    Powerfull mobile services as part of Telerik Platform
  • 2
    Live reload
  • 2
    Native ui with angular
  • 2
    Easy to learn
  • 2
    Vue.js support out of the box
  • 2
    Vue support
  • 1
    It works with Angular
  • 1
    Easy to use, support for almost all npm packages
  • 1
    Very small app size
  • 1
    Write once, use anywhere
  • 1
    Compile to Apple/Google Stores via CloudCompiler
  • 1
    HMR via webpack
  • 1
    Code reuse with your website
  • 1
    Rich ecosystem
  • 1
    Has CSS ;-)
  • 1
    Playground
  • 1
    Hot Reload
CONS OF NATIVESCRIPT
  • 5
    Lack of promotion
  • 1
    Slower Performance compared to competitors

related NativeScript posts

leonardo silveira
Software Engineer at Casa Magalhães · | 5 upvotes · 155.8K views

So, i am preparing to adopt NativeScript.

For years my hybrid projects used Apache Cordova.

"Let's avoid to maintain two teams and double the deliver velocity".

It was good for a few years, we had those september issues, (i.e. apple broke some backward compatibility) , but for the last years, things seems to be losing the grip faster.

Last breaking changes, for instance, seems to have a workaround, however that growing feeling that simple things can not rely on so fragile webviews keeps growing faster and faster.

I've tested nativescript not only on it's "helloworld", but also on how do they respond on issues.

I got tweed support. I opened an github issue and got answers on less than 10 hours (yes i did it on another timezone and very close to a weekend). I saw the faulty docs get corrected in two days.

The bad news is i only can adopt nativescript on newer projects, since there is no budget to revamp the current solutions.

The good news is i can keep coding on Vue.js , without vou router, but that's ok. I've already exchanged vanilla html for real native app with background magic enabled, the router can be easily reproduced.

See more
PhoneGap logo

PhoneGap

553
630
94
Easilily create mobile apps using HTML, CSS, and JavaScript
553
630
+ 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.3M 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 · 360K 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
Swift logo

Swift

11.4K
7.9K
1.2K
An innovative new programming language for Cocoa and Cocoa Touch.
11.4K
7.9K
+ 1
1.2K
PROS OF SWIFT
  • 248
    Ios
  • 175
    Elegant
  • 123
    Not Objective-C
  • 105
    Backed by apple
  • 89
    Type inference
  • 58
    Generics
  • 51
    Playgrounds
  • 47
    Semicolon free
  • 37
    OSX
  • 34
    Tuples offer compound variables
  • 21
    Clean Syntax
  • 21
    Easy to learn
  • 20
    Open Source
  • 19
    Functional
  • 17
    Beautiful Code
  • 10
    Linux
  • 10
    Dynamic
  • 9
    Promotes safe, readable code
  • 8
    Protocol-oriented programming
  • 7
    Explicit optionals
  • 7
    No S-l-o-w JVM
  • 5
    Storyboard designer
  • 4
    Super addicting language, great people, open, elegant
  • 4
    Type safety
  • 4
    Optionals
  • 4
    Best UI concept
  • 3
    Feels like a better C++
  • 3
    Swift is faster than Objective-C
  • 3
    Faster and looks better
  • 2
    Easy to Maintain
  • 2
    Strong Type safety
  • 2
    Fail-safe
  • 2
    Its fun and damn fast
  • 2
    Highly Readable codes
  • 2
    Native
  • 2
    Protocol extensions
  • 2
    Powerful
  • 2
    Much more fun
  • 2
    Its friendly
  • 2
    Easy to learn and work
  • 1
    Protocol as type
  • 1
    Protocol oriented programming
  • 1
    Great for Multi-Threaded Programming
  • 1
    Objec
  • 1
    Type Safe
  • 1
    All Cons C# and Java Swift Already has
  • 1
    Free from Memory Leak
  • 1
    Swift is easier to understand for non-iOS developers.
  • 1
    Actually don't have to own a mac
  • 1
    Can interface with C easily
  • 1
    Esay
  • 1
    Numbers with underbar
  • 1
    MacOS
  • 1
    Optional chain
CONS OF SWIFT
  • 2
    Must own a mac
  • 2
    Memory leaks are not uncommon
  • 1
    Its classes compile to roughly 300 lines of assembly
  • 1
    Complicated process for exporting modules
  • 1
    Very irritatingly picky about things that’s
  • 1
    Is a lot more effort than lua to make simple functions
  • 0
    Overly complex options makes it easy to create bad code

related Swift posts

Shivam Bhargava
AVP - Business at VAYUZ Technologies Pvt. Ltd. · | 22 upvotes · 165.4K views

Hi Community! Trust everyone is keeping safe. I am exploring the idea of building a #Neobank (App) with end-to-end banking capabilities. In the process of exploring this space, I have come across multiple Apps (N26, Revolut, Monese, etc) and explored their stacks in detail. The confusion remains to be the Backend Tech to be used?

What would you go with considering all of the languages such as Node.js Java Rails Python are suggested by some person or the other. As a general trend, I have noticed the usage of Node with React on the front or Node with a combination of Kotlin and Swift. Please suggest what would be the right approach!

See more
Siddhant Sharma
Tech Connoisseur at Channelize.io · | 12 upvotes · 691.6K views

WordPress Magento PHP Java Swift JavaScript

Back in the days, we started looking for a date on different matrimonial websites as there were no Dating Applications. We used to create different profiles. It all changed in 2012 when Tinder, an Online Dating application came into India Market.

Tinder allowed us to communicate with our potential soul mates. That too without paying any extra money. I too got 4-6 matches in 6 years. It changed the life of many Millennials. Tinder created a revolution of its own. P.S. - I still don't have a date :(

Posting my first article. Please have a look and do give feedback.

Communication InAppChat Dating Matrimonial #messaging

See more
Android Studio logo

Android Studio

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

related Android Studio posts

Gustavo Muñoz
Web UI Developer at Globant · | 8 upvotes · 351K 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 · 283.8K 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
Appcelerator logo

Appcelerator

47
56
26
Build network-connected mobile applications across native platforms and the web
47
56
+ 1
26
PROS OF APPCELERATOR
  • 4
    Open Source
  • 4
    Android
  • 4
    Easy to learn
  • 2
    Javascript
  • 2
    IOS
  • 2
    Great community
  • 1
    Vue.js beta
  • 1
    Lots of native modules, components, libraries
  • 1
    Native UI
  • 1
    MVC-based
  • 1
    Paid plans available
  • 1
    Free
  • 1
    Write directly to iOS and Android SDK with JavaScript
  • 1
    Angular.js beta
CONS OF APPCELERATOR
  • 1
    No online IDE

related Appcelerator posts