Alternatives to Vue Native logo

Alternatives to Vue Native

React Native, Vue.js, React, Flutter, and NativeScript are the most popular alternatives and competitors to Vue Native.
101
746
+ 1
57

What is Vue Native and what are its top alternatives?

Vue Native is a framework that allows developers to build cross-platform mobile apps using Vue.js. Key features include a familiar Vue.js syntax, easy integration with existing Vue.js projects, and access to native components of iOS and Android. However, Vue Native is relatively new in the market and may have fewer community resources and third-party integrations compared to more established frameworks.

  1. React Native: React Native is a popular framework for building cross-platform mobile apps using React.js. Key features include a large community, extensive documentation, and powerful native components. However, React Native has a steeper learning curve compared to Vue Native.
  2. Flutter: Flutter is Google's UI toolkit for building natively compiled applications for mobile, web, and desktop from a single codebase. Key features include fast development times, hot reload functionality, and customizable widgets. However, Flutter uses Dart programming language instead of JavaScript like Vue Native.
  3. Ionic: Ionic is a framework for building cross-platform mobile and web apps using web technologies like HTML, CSS, and JavaScript. Key features include a large collection of UI components, easy integration with Angular, and support for progressive web apps. However, Ionic may not offer the same level of performance as Vue Native.
  4. NativeScript: NativeScript is an open-source framework for building truly native mobile applications using JavaScript. Key features include direct access to native APIs, support for Angular and Vue.js, and a rich plugin ecosystem. However, NativeScript may have a steeper learning curve compared to Vue Native.
  5. Xamarin: Xamarin is a framework for building cross-platform mobile apps using C# and .NET. Key features include native performance, shared codebase, and access to platform-specific APIs. However, Xamarin may have a larger overhead compared to Vue Native in terms of setup and configuration.
  6. PhoneGap: PhoneGap is an open-source framework for building cross-platform mobile apps using web technologies. Key features include easy integration with existing web code, support for multiple platforms, and access to native device features. However, PhoneGap may not offer the same level of performance and native-like user experience as Vue Native.
  7. Quasar Framework: Quasar Framework is a Vue.js framework for building responsive websites, PWAs, SSR, mobile apps, and Electron apps. Key features include a large collection of Vue components, SSR and PWA support, and a rich ecosystem of plugins. However, Quasar may not provide the same level of customization for mobile apps as Vue Native.
  8. Onsen UI: Onsen UI is an open-source framework for building mobile apps using Web Components with Vue.js integration. Key features include a large collection of customizable components, support for touch gestures, and theming capabilities. However, Onsen UI may have a smaller community compared to Vue Native.
  9. Weex: Weex is a framework for building cross-platform mobile apps using Vue.js and the Weex native rendering engine. Key features include high performance, a familiar Vue.js syntax, and support for multiple platforms. However, Weex may have fewer community resources and third-party integrations compared to Vue Native.
  10. Svelte Native: Svelte Native is a framework for building truly native mobile applications using Svelte and NativeScript. Key features include high-performance reactive components, a simple and easy-to-learn syntax, and seamless integration with NativeScript. However, Svelte Native may have a smaller community compared to Vue Native.

Top Alternatives to Vue Native

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

  • Vue.js
    Vue.js

    It is a library for building interactive web interfaces. It provides data-reactive components with a simple and flexible API. ...

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

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

  • NativeScript-Vue
    NativeScript-Vue

    It is a NativeScript plugin which allows you to use Vue.js to craft your mobile application. It aims to have a syntax that you are used to from Vue.js. ...

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

Vue Native alternatives & related posts

React Native logo

React Native

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

related React Native posts

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

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

See more

I'm working as one of the engineering leads in RunaHR. As our platform is a Saas, we thought It'd be good to have an API (We chose Ruby and Rails for this) and a SPA (built with React and Redux ) connected. We started the SPA with Create React App since It's pretty easy to start.

We use Jest as the testing framework and react-testing-library to test React components. In Rails we make tests using RSpec.

Our main database is PostgreSQL, but we also use MongoDB to store some type of data. We started to use Redis  for cache and other time sensitive operations.

We have a couple of extra projects: One is an Employee app built with React Native and the other is an internal back office dashboard built with Next.js for the client and Python in the backend side.

Since we have different frontend apps we have found useful to have Bit to document visual components and utils in JavaScript.

See more
Vue.js logo

Vue.js

53.2K
43.2K
1.6K
A progressive framework for building user interfaces
53.2K
43.2K
+ 1
1.6K
PROS OF VUE.JS
  • 293
    Simple and easy to start with
  • 229
    Good documentation
  • 196
    Components
  • 131
    Simple the best
  • 100
    Simplified AngularJS
  • 94
    Reactive
  • 77
    Intuitive APIs
  • 56
    Javascript
  • 52
    Changed my front end coding life
  • 48
    Configuration is smooth
  • 37
    Easy to learn
  • 35
    So much fun to use
  • 25
    Progressive
  • 22
    Virtual dom
  • 16
    Faster than bulldogs on hot tarmac
  • 12
    Component is template, javascript and style in one
  • 12
    It's magic
  • 10
    Perfomance
  • 10
    Light Weight
  • 9
    Best of Both Worlds
  • 8
    Intuitive and easy to use
  • 8
    Elegant design
  • 8
    Application structure
  • 8
    Without misleading licenses
  • 6
    Small learning curve
  • 6
    Good command line interface
  • 5
    Logicless templates
  • 5
    Like Angular only quicker to get started with
  • 5
    Single file components
  • 5
    Easy to integrate to HTML by inline-templates
  • 4
    High performance
  • 3
    Vuex
  • 3
    Component based
  • 3
    Customer Render ending eg to HTML
  • 3
    Bridge from Web Development to JS Development
  • 2
    Concise error messages
  • 2
    Supports several template languages
  • 2
    One-way data flow
  • 2
    Lots of documentation
  • 2
    Intuitive
  • 1
    GUI
CONS OF VUE.JS
  • 9
    Less Common Place
  • 5
    YXMLvsHTML Markup
  • 3
    Don't support fragments
  • 3
    Only support programatically multiple root nodes

related Vue.js posts

Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 27 upvotes · 4.7M views

Our whole Node.js backend stack consists of the following tools:

  • Lerna as a tool for multi package and multi repository management
  • npm as package manager
  • NestJS as Node.js framework
  • TypeScript as programming language
  • ExpressJS as web server
  • Swagger UI for visualizing and interacting with the API’s resources
  • Postman as a tool for API development
  • TypeORM as object relational mapping layer
  • JSON Web Token for access token management

The main reason we have chosen Node.js over PHP is related to the following artifacts:

  • Made for the web and widely in use: Node.js is a software platform for developing server-side network services. Well-known projects that rely on Node.js include the blogging software Ghost, the project management tool Trello and the operating system WebOS. Node.js requires the JavaScript runtime environment V8, which was specially developed by Google for the popular Chrome browser. This guarantees a very resource-saving architecture, which qualifies Node.js especially for the operation of a web server. Ryan Dahl, the developer of Node.js, released the first stable version on May 27, 2009. He developed Node.js out of dissatisfaction with the possibilities that JavaScript offered at the time. The basic functionality of Node.js has been mapped with JavaScript since the first version, which can be expanded with a large number of different modules. The current package managers (npm or Yarn) for Node.js know more than 1,000,000 of these modules.
  • Fast server-side solutions: Node.js adopts the JavaScript "event-loop" to create non-blocking I/O applications that conveniently serve simultaneous events. With the standard available asynchronous processing within JavaScript/TypeScript, highly scalable, server-side solutions can be realized. The efficient use of the CPU and the RAM is maximized and more simultaneous requests can be processed than with conventional multi-thread servers.
  • A language along the entire stack: Widely used frameworks such as React or AngularJS or Vue.js, which we prefer, are written in JavaScript/TypeScript. If Node.js is now used on the server side, you can use all the advantages of a uniform script language throughout the entire application development. The same language in the back- and frontend simplifies the maintenance of the application and also the coordination within the development team.
  • Flexibility: Node.js sets very few strict dependencies, rules and guidelines and thus grants a high degree of flexibility in application development. There are no strict conventions so that the appropriate architecture, design structures, modules and features can be freely selected for the development.
See more
Johnny Bell
Shared insights
on
Vue.jsVue.jsReactReact

I've used both Vue.js and React and I would stick with React. I know that Vue.js seems easier to write and its much faster to pick up however as you mentioned above React has way more ready made components you can just plugin, and the community for React is very big.

It might be a bit more of a steep learning curve for your friend to learn React over Vue.js but I think in the long run its the better option.

See more
React logo

React

167.8K
138.9K
4.1K
A JavaScript library for building user interfaces
167.8K
138.9K
+ 1
4.1K
PROS OF REACT
  • 830
    Components
  • 672
    Virtual dom
  • 578
    Performance
  • 507
    Simplicity
  • 442
    Composable
  • 186
    Data flow
  • 166
    Declarative
  • 128
    Isn't an mvc framework
  • 120
    Reactive updates
  • 115
    Explicit app state
  • 50
    JSX
  • 29
    Learn once, write everywhere
  • 22
    Easy to Use
  • 21
    Uni-directional data flow
  • 17
    Works great with Flux Architecture
  • 11
    Great perfomance
  • 10
    Javascript
  • 9
    Built by Facebook
  • 8
    TypeScript support
  • 6
    Speed
  • 6
    Server Side Rendering
  • 5
    Feels like the 90s
  • 5
    Excellent Documentation
  • 5
    Props
  • 5
    Functional
  • 5
    Easy as Lego
  • 5
    Closer to standard JavaScript and HTML than others
  • 5
    Cross-platform
  • 5
    Easy to start
  • 5
    Hooks
  • 5
    Awesome
  • 5
    Scalable
  • 4
    Super easy
  • 4
    Allows creating single page applications
  • 4
    Server side views
  • 4
    Sdfsdfsdf
  • 4
    Start simple
  • 4
    Strong Community
  • 4
    Fancy third party tools
  • 4
    Scales super well
  • 3
    Has arrow functions
  • 3
    Beautiful and Neat Component Management
  • 3
    Just the View of MVC
  • 3
    Simple, easy to reason about and makes you productive
  • 3
    Fast evolving
  • 3
    SSR
  • 3
    Great migration pathway for older systems
  • 3
    Rich ecosystem
  • 3
    Simple
  • 3
    Has functional components
  • 3
    Every decision architecture wise makes sense
  • 3
    Very gentle learning curve
  • 2
    Split your UI into components with one true state
  • 2
    Recharts
  • 2
    Permissively-licensed
  • 2
    Fragments
  • 2
    Sharable
  • 2
    Image upload
  • 2
    HTML-like
  • 1
    React hooks
  • 1
    Datatables
CONS OF REACT
  • 40
    Requires discipline to keep architecture organized
  • 29
    No predefined way to structure your app
  • 28
    Need to be familiar with lots of third party packages
  • 13
    JSX
  • 10
    Not enterprise friendly
  • 6
    One-way binding only
  • 3
    State consistency with backend neglected
  • 3
    Bad Documentation
  • 2
    Error boundary is needed
  • 2
    Paradigms change too fast

related React posts

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

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

See more
Adebayo Akinlaja
Engineering Manager at Andela · | 30 upvotes · 3.3M 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
Flutter logo

Flutter

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

related Flutter posts

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

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

See more

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

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

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

See more
NativeScript logo

NativeScript

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

related NativeScript posts

Hello,

We're just brainstorming for the moment and we have a few questions.

We have an idea for an app that we want to develop, here are the prerequisites:

1) cross-platform (iOS, Android, and website);

2) as easy to maintain as possible / well documented / widely used;

3) Visual Studio Code and Copilot compatible;

4) Text to speech;

5) Speech recognition;

6) Running in background (screen off with TTS and speech recognition);

7) could be using TypeScript;

8) Monetized through ad and in-App payment for premium version;

9) Display on lock screen (Android only I guess)

So what would you recommend?

I've been trying to review the options available, and I've considered:

  • NativeScript

  • React Native

  • Flutter

  • Any other?

Thanks in advance for your help, and I'm open to any comments.

See more
leonardo silveira
Software Engineer at Jobsity · | 5 upvotes · 560K 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
NativeScript-Vue logo

NativeScript-Vue

57
135
0
Truly native apps using Vue.js and NativeScript
57
135
+ 1
0
PROS OF NATIVESCRIPT-VUE
    Be the first to leave a pro
    CONS OF NATIVESCRIPT-VUE
      Be the first to leave a con

      related NativeScript-Vue posts

      Ionic logo

      Ionic

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

      related Ionic posts

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

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

      See more
      Saber Hosney
      Senior software engineer at Shortcut · | 7 upvotes · 270.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
      Xamarin logo

      Xamarin

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

      related Xamarin posts

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

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

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

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

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

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

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

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

      See more