Alternatives to Flutter logo

Alternatives to Flutter

React Native, Xamarin, Android SDK, Java, and Kotlin are the most popular alternatives and competitors to Flutter.
7.3K
7.8K
+ 1
908

What is Flutter and what are its top alternatives?

Flutter is a mobile app SDK to help developers and designers build modern mobile apps for iOS and Android.
Flutter is a tool in the Cross-Platform Mobile Development category of a tech stack.
Flutter is an open source tool with 131.1K GitHub stars and 19K GitHub forks. Here’s a link to Flutter's open source repository on GitHub

Top Alternatives to Flutter

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

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

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

  • Java

    Java

    Java is a programming language and computing platform first released by Sun Microsystems in 1995. There are lots of applications and websites that will not work unless you have Java installed, and more are created every day. Java is fast, secure, and reliable. From laptops to datacenters, game consoles to scientific supercomputers, cell phones to the Internet, Java is everywhere! ...

  • Kotlin

    Kotlin

    Kotlin is a statically typed programming language for the JVM, Android and the browser, 100% interoperable with Java ...

  • React

    React

    Lots of people use React as the V in MVC. Since React makes no assumptions about the rest of your technology stack, it's easy to try it out on a small feature in an existing project. ...

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

  • 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 alternatives & related posts

React Native logo

React Native

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

related React Native posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.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
Ganesa Vijayakumar
Full Stack Coder | Module Lead · | 19 upvotes · 2.4M views

I'm planning to create a web application and also a mobile application to provide a very good shopping experience to the end customers. Shortly, my application will be aggregate the product details from difference sources and giving a clear picture to the user that when and where to buy that product with best in Quality and cost.

I have planned to develop this in many milestones for adding N number of features and I have picked my first part to complete the core part (aggregate the product details from different sources).

As per my work experience and knowledge, I have chosen the followings stacks to this mission.

UI: I would like to develop this application using React, React Router and React Native since I'm a little bit familiar on this and also most importantly these will help on developing both web and mobile apps. In addition, I'm gonna use the stacks JavaScript, jQuery, jQuery UI, jQuery Mobile, Bootstrap wherever required.

Service: I have planned to use Java as the main business layer language as I have 7+ years of experience on this I believe I can do better work using Java than other languages. In addition, I'm thinking to use the stacks Node.js.

Database and ORM: I'm gonna pick MySQL as DB and Hibernate as ORM since I have a piece of good knowledge and also work experience on this combination.

Search Engine: I need to deal with a large amount of product data and it's in-detailed info to provide enough details to end user at the same time I need to focus on the performance area too. so I have decided to use Solr as a search engine for product search and suggestions. In addition, I'm thinking to replace Solr by Elasticsearch once explored/reviewed enough about Elasticsearch.

Host: As of now, my plan to complete the application with decent features first and deploy it in a free hosting environment like Docker and Heroku and then once it is stable then I have planned to use the AWS products Amazon S3, EC2, Amazon RDS and Amazon Route 53. I'm not sure about Microsoft Azure that what is the specialty in it than Heroku and Amazon EC2 Container Service. Anyhow, I will do explore these once again and pick the best suite one for my requirement once I reached this level.

Build and Repositories: I have decided to choose Apache Maven and Git as these are my favorites and also so popular on respectively build and repositories.

Additional Utilities :) - I would like to choose Codacy for code review as their Startup plan will be very helpful to this application. I'm already experienced with Google CheckStyle and SonarQube even I'm looking something on Codacy.

Happy Coding! Suggestions are welcome! :)

Thanks, Ganesa

See more
Xamarin logo

Xamarin

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

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
Android SDK logo

Android SDK

19.3K
14.5K
785
An SDK that provides you the API libraries and developer tools necessary to build, test, and debug apps...
19.3K
14.5K
+ 1
785
PROS OF ANDROID SDK
  • 284
    Android development
  • 153
    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
    Free
  • 2
    Больно
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 · 852K 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 · 654.9K 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
    Java logo

    Java

    88.9K
    65.9K
    3.5K
    A concurrent, class-based, object-oriented, language specifically designed to have as few implementation dependencies as possible
    88.9K
    65.9K
    + 1
    3.5K
    PROS OF JAVA
    • 579
      Great libraries
    • 438
      Widely used
    • 396
      Excellent tooling
    • 381
      Huge amount of documentation available
    • 329
      Large pool of developers available
    • 199
      Open source
    • 195
      Excellent performance
    • 151
      Great development
    • 145
      Used for android
    • 144
      Vast array of 3rd party libraries
    • 56
      Compiled Language
    • 47
      Used for Web
    • 43
      Managed memory
    • 42
      Native threads
    • 41
      High Performance
    • 37
      Statically typed
    • 32
      Easy to read
    • 30
      Great Community
    • 26
      Reliable platform
    • 23
      JVM compatibility
    • 23
      Sturdy garbage collection
    • 19
      Cross Platform Enterprise Integration
    • 18
      Universal platform
    • 17
      Good amount of APIs
    • 16
      Great Support
    • 11
      Lots of boilerplate
    • 10
      Great ecosystem
    • 10
      Backward compatible
    • 9
      Everywhere
    • 7
      Excellent SDK - JDK
    • 6
      Mature language thus stable systems
    • 5
      Clojure
    • 5
      Static typing
    • 5
      It's Java
    • 5
      Portability
    • 5
      Better than Ruby
    • 5
      Cross-platform
    • 5
      Vast Collections Library
    • 4
      Long term language
    • 4
      Old tech
    • 3
      Most developers favorite
    • 3
      Best martial for design
    • 3
      Great Structure
    • 3
      Used for Android development
    • 3
      Stable platform, which many new languages depend on
    • 2
      Testable
    • 2
      History
    • 1
      Javadoc
    CONS OF JAVA
    • 30
      Verbosity
    • 25
      NullpointerException
    • 15
      Overcomplexity is praised in community culture
    • 14
      Nightmare to Write
    • 10
      Boiler plate code
    • 8
      Classpath hell prior to Java 9
    • 6
      No REPL
    • 4
      No property
    • 2
      Code are too long
    • 2
      There is not optional parameter
    • 2
      Floating-point errors
    • 1
      Terrbible compared to Python/Batch Perormence
    • 1
      Java's too statically, stronglly, and strictly typed
    • 1
      Non-intuitive generic implementation
    • 1
      Returning Wildcard Types

    related Java posts

    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 38 upvotes · 4.1M views

    How Uber developed the open source, end-to-end distributed tracing Jaeger , now a CNCF project:

    Distributed tracing is quickly becoming a must-have component in the tools that organizations use to monitor their complex, microservice-based architectures. At Uber, our open source distributed tracing system Jaeger saw large-scale internal adoption throughout 2016, integrated into hundreds of microservices and now recording thousands of traces every second.

    Here is the story of how we got here, from investigating off-the-shelf solutions like Zipkin, to why we switched from pull to push architecture, and how distributed tracing will continue to evolve:

    https://eng.uber.com/distributed-tracing/

    (GitHub Pages : https://www.jaegertracing.io/, GitHub: https://github.com/jaegertracing/jaeger)

    Bindings/Operator: Python Java Node.js Go C++ Kubernetes JavaScript OpenShift C# Apache Spark

    See more
    Kamil Kowalski
    Lead Architect at Fresha · | 27 upvotes · 1.1M views

    When you think about test automation, it’s crucial to make it everyone’s responsibility (not just QA Engineers'). We started with Selenium and Java, but with our platform revolving around Ruby, Elixir and JavaScript, QA Engineers were left alone to automate tests. Cypress was the answer, as we could switch to JS and simply involve more people from day one. There's a downside too, as it meant testing on Chrome only, but that was "good enough" for us + if really needed we can always cover some specific cases in a different way.

    See more
    Kotlin logo

    Kotlin

    8.5K
    6.5K
    508
    Statically typed Programming Language targeting JVM and JavaScript
    8.5K
    6.5K
    + 1
    508
    PROS OF KOTLIN
    • 63
      Interoperable with Java
    • 48
      Functional Programming support
    • 43
      Null Safety
    • 39
      Backed by JetBrains
    • 38
      Official Android support
    • 30
      Concise
    • 29
      Modern Multiplatform Applications
    • 24
      Expressive Syntax
    • 22
      Coroutines
    • 21
      Target to JVM
    • 20
      Open Source
    • 15
      Practical elegance
    • 14
      Type Inference
    • 14
      Statically Typed
    • 13
      Android support
    • 9
      Pragmatic
    • 9
      Better Java
    • 9
      Readable code
    • 8
      Powerful as Scala, simple as Python, plus coroutines <3
    • 6
      Better language for android
    • 6
      Lambda
    • 6
      Expressive DSLs
    • 5
      Target to JavaScript
    • 4
      Less boilerplate code
    • 3
      Used for Android
    • 3
      Fast Programming language
    • 2
      Functional Programming Language
    • 2
      Less code
    • 1
      Latest version of Java
    • 1
      Friendly community
    • 1
      Less boiler plate code
    CONS OF KOTLIN
    • 5
      Java interop makes users write Java in Kotlin
    • 4
      Frequent use of {} keys
    • 2
      Hard to make teams adopt the Kotlin style
    • 2
      Nonullpointer Exception
    • 1
      Friendly community
    • 1
      No boiler plate code

    related Kotlin posts

    Shivam Bhargava
    AVP - Business at VAYUZ Technologies Pvt. Ltd. · | 22 upvotes · 249.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
    Jakub Olan
    Node.js Software Engineer · | 17 upvotes · 241.5K views

    In our company we have think a lot about languages that we're willing to use, there we have considering Java, Python and C++ . All of there languages are old and well developed at fact but that's not ideology of araclx. We've choose a edge technologies such as Node.js , Rust , Kotlin and Go as our programming languages which is some kind of fun. Node.js is one of biggest trends of 2019, same for Go. We want to grow in our company with growth of languages we have choose, and probably when we would choose Java that would be almost impossible because larger languages move on today's market slower, and cannot have big changes.

    See more
    React logo

    React

    109.5K
    87.5K
    3.8K
    A JavaScript library for building user interfaces
    109.5K
    87.5K
    + 1
    3.8K
    PROS OF REACT
    • 757
      Components
    • 651
      Virtual dom
    • 562
      Performance
    • 486
      Simplicity
    • 436
      Composable
    • 175
      Data flow
    • 159
      Declarative
    • 124
      Isn't an mvc framework
    • 113
      Reactive updates
    • 111
      Explicit app state
    • 32
      JSX
    • 23
      Learn once, write everywhere
    • 19
      Uni-directional data flow
    • 16
      Easy to Use
    • 14
      Works great with Flux Architecture
    • 10
      Great perfomance
    • 8
      Built by Facebook
    • 7
      Javascript
    • 5
      TypeScript support
    • 5
      Speed
    • 4
      Feels like the 90s
    • 4
      Scalable
    • 4
      Easy to start
    • 4
      Awesome
    • 3
      Fancy third party tools
    • 3
      Hooks
    • 3
      Functional
    • 3
      Server side views
    • 3
      Props
    • 2
      Rich ecosystem
    • 2
      Obama
    • 2
      Very gentle learning curve
    • 2
      Has functional components
    • 2
      Simple
    • 2
      Closer to standard JavaScript and HTML than others
    • 2
      Super easy
    • 2
      Has arrow functions
    • 2
      Strong Community
    • 2
      Great migration pathway for older systems
    • 2
      SSR
    • 2
      Fast evolving
    • 2
      Simple, easy to reason about and makes you productive
    • 2
      Excellent Documentation
    • 2
      Scales super well
    • 2
      Just the View of MVC
    • 2
      Server Side Rendering
    • 2
      Cross-platform
    • 1
      Fragments
    • 1
      Start simple
    • 1
      Every decision architecture wise makes sense
    • 1
      Permissively-licensed
    • 1
      Beautiful and Neat Component Management
    • 1
      Sdfsdfsdf
    • 1
      Allows creating single page applications
    • 1
      Split your UI into components with one true state
    • 1
      Sharable
    CONS OF REACT
    • 35
      Requires discipline to keep architecture organized
    • 23
      No predefined way to structure your app
    • 21
      Need to be familiar with lots of third party packages
    • 8
      JSX
    • 7
      Not enterprise friendly
    • 3
      One-way binding only
    • 2
      State consistency with backend neglected
    • 1
      Bad Documentation

    related React posts

    Vaibhav Taunk
    Team Lead at Technovert · | 31 upvotes · 1.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
    Adebayo Akinlaja
    Engineering Manager at Andela · | 26 upvotes · 719.6K 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
    Swift logo

    Swift

    13.1K
    9.3K
    1.2K
    An innovative new programming language for Cocoa and Cocoa Touch.
    13.1K
    9.3K
    + 1
    1.2K
    PROS OF SWIFT
    • 250
      Ios
    • 176
      Elegant
    • 124
      Not Objective-C
    • 105
      Backed by apple
    • 91
      Type inference
    • 60
      Generics
    • 54
      Playgrounds
    • 49
      Semicolon free
    • 39
      OSX
    • 35
      Tuples offer compound variables
    • 24
      Easy to learn
    • 23
      Clean Syntax
    • 21
      Open Source
    • 20
      Functional
    • 19
      Beautiful Code
    • 11
      Linux
    • 11
      Dynamic
    • 10
      Promotes safe, readable code
    • 9
      Protocol-oriented programming
    • 8
      Explicit optionals
    • 8
      No S-l-o-w JVM
    • 6
      Storyboard designer
    • 5
      Best UI concept
    • 5
      Optionals
    • 5
      Type safety
    • 5
      Super addicting language, great people, open, elegant
    • 4
      Its friendly
    • 4
      Powerful
    • 4
      Fail-safe
    • 4
      Highly Readable codes
    • 4
      Faster and looks better
    • 4
      Swift is faster than Objective-C
    • 4
      Feels like a better C++
    • 3
      Its fun and damn fast
    • 3
      Easy to learn and work
    • 3
      Much more fun
    • 3
      Protocol extensions
    • 3
      Native
    • 3
      Strong Type safety
    • 3
      Easy to Maintain
    • 2
      Protocol oriented programming
    • 2
      Esay
    • 2
      MacOS
    • 2
      Type Safe
    • 2
      All Cons C# and Java Swift Already has
    • 2
      Protocol as type
    • 1
      Actually don't have to own a mac
    • 1
      Can interface with C easily
    • 1
      Numbers with underbar
    • 1
      Optional chain
    • 1
      Runs Python 8 times faster
    • 1
      Free from Memory Leak
    • 1
      Swift is easier to understand for non-iOS developers.
    • 1
      Great for Multi-Threaded Programming
    • 1
      Objec
    CONS OF SWIFT
    • 5
      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 · 249.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
    Conor Myhrvold
    Tech Brand Mgr, Office of CTO at Uber · | 12 upvotes · 1.1M views

    Excerpts from how we developed (and subsequently open sourced) Uber's cross-platform mobile architecture framework, RIBs , going from Objective-C to Swift in the process for iOS: https://github.com/uber/RIBs

    Uber’s new application architecture (RIBs) extensively uses protocols to keep its various components decoupled and testable. We used this architecture for the first time in our new rider application and moved our primary language from Objective-C to Swift. Since Swift is a very static language, unit testing became problematic. Dynamic languages have good frameworks to build test mocks, stubs, or stand-ins by dynamically creating or modifying existing concrete classes.

    Needless to say, we were not very excited about the additional complexity of manually writing and maintaining mock implementations for each of our thousands of protocols.

    The information required to generate mock classes already exists in the Swift protocol. For Uber’s use case, we set out to create tooling that would let engineers automatically generate test mocks for any protocol they wanted by simply annotating them.

    The iOS codebase for our rider application alone incorporates around 1,500 of these generated mocks. Without our code generation tool, all of these would have to be written and maintained by hand, which would have made testing much more time-intensive. Auto-generated mocks have contributed a lot to the unit test coverage that we have today.

    We built these code generation tools ourselves for a number of reasons, including that there weren’t many open source tools available at the time we started our effort. Today, there are some great open source tools to generate resource accessors, like SwiftGen. And Sourcery can help you with generic code generation needs:

    https://eng.uber.com/code-generation/ https://eng.uber.com/driver-app-ribs-architecture/

    (GitHub : https://github.com/uber/RIBs )

    See more
    Ionic logo

    Ionic

    7.1K
    6.4K
    1.7K
    A beautiful front-end framework for developing cross-platform apps with web technologies like Angular and React.
    7.1K
    6.4K
    + 1
    1.7K
    PROS OF IONIC
    • 246
      Allows for rapid prototyping
    • 226
      Hybrid mobile
    • 208
      It's angularjs
    • 184
      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
    • 2
      Not a native app

    related Ionic posts

    Saber Hosney
    Senior software engineer at Shortcut · | 7 upvotes · 40.1K 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
    Ionic
    Flutter

    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