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.
98
725
+ 1
57

What is Vue Native and what are its top alternatives?

Vue Native is a mobile framework to build truly native mobile app using Vue.js. Its is designed to connect React Native and Vue.js. Vue Native is a wrapper around React Native APIs, which allows you to use Vue.js and compose rich mobile User Interface.
Vue Native is a tool in the Cross-Platform Mobile Development category of a tech stack.
Vue Native is an open source tool with 8.4K GitHub stars and 319 GitHub forks. Here’s a link to Vue Native's open source repository on GitHub

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

26.5K
23.1K
1.1K
A framework for building native apps with React
26.5K
23.1K
+ 1
1.1K
PROS OF REACT NATIVE
  • 205
    Learn once write everywhere
  • 167
    Cross platform
  • 163
    Javascript
  • 119
    Native ios components
  • 67
    Built by facebook
  • 62
    Easy to learn
  • 43
    Bridges me into ios development
  • 40
    It's just react
  • 39
    No compile
  • 36
    Declarative
  • 21
    Fast
  • 12
    Livereload
  • 12
    Virtual Dom
  • 11
    Insanely fast develop / test cycle
  • 10
    Great community
  • 9
    It is free and open source
  • 9
    Easy setup
  • 9
    Backed by Facebook
  • 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
    Not dependent on anything such as Angular
  • 5
    Simple
  • 4
    OTA update
  • 4
    Awesome, easy starting from scratch
  • 3
    Easy to use
  • 3
    As good as Native without any performance concerns
  • 2
    Many salary
  • 2
    Can be incrementally added to existing native apps
  • 2
    Hot reload
  • 2
    Over the air update (Flutter lacks)
  • 2
    'It's just react'
  • 2
    Web development meets Mobile development
  • 1
    Ngon
CONS OF REACT NATIVE
  • 23
    Javascript
  • 18
    Built by facebook
  • 12
    Cant use CSS
  • 4
    30 FPS Limit
  • 2
    Slow
  • 2
    Some compenents not truly native
  • 2
    Generate large apk even for a simple app

related React Native posts

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

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

related Vue.js posts

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
Simon Reymann
Senior Fullstack Developer at QUANTUSflow Software GmbH · | 26 upvotes · 2.6M 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
React logo

React

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

related React posts

Vaibhav Taunk
Team Lead at Technovert · | 31 upvotes · 1.9M 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 · | 27 upvotes · 1.1M 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

10.9K
11.1K
1K
Cross-platform mobile framework from Google
10.9K
11.1K
+ 1
1K
PROS OF FLUTTER
  • 125
    Hot Reload
  • 105
    Cross platform
  • 97
    Performance
  • 81
    Backed by Google
  • 67
    Compiled into Native Code
  • 53
    Fast Development
  • 52
    Open Source
  • 47
    Fast Prototyping
  • 43
    Expressive and Flexible UI
  • 41
    Single Codebase
  • 35
    Reactive Programming
  • 30
    Material Design
  • 25
    Widget-based
  • 24
    Dart
  • 24
    Target to Fuchsia
  • 17
    IOS + Android
  • 14
    Easy to learn
  • 13
    Great CLI Support
  • 13
    Tooling
  • 13
    You can use it as mobile, web, Server development
  • 11
    Good docs & sample code
  • 11
    Debugging quickly
  • 11
    Have built-in Material theme
  • 10
    Community
  • 10
    Target to Android
  • 10
    Support by multiple IDE: Android Studio, VS Code, XCode
  • 9
    Easy Testing Support
  • 9
    Written by Dart, which is easy to read code
  • 8
    Target to iOS
  • 8
    Real platform free framework of the future
  • 8
    Have built-in Cupertino theme
  • 7
    Easy to Unit Test
  • 7
    Easy to Widget Test
CONS OF FLUTTER
  • 28
    Need to learn Dart
  • 10
    No 3D Graphics Engine Support
  • 9
    Lack of community support
  • 7
    Graphics programming
  • 6
    Lack of friendly documentation
  • 2
    Lack of promotion
  • 1
    Https://iphtechnologies.com/difference-between-flutter

related Flutter posts

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

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

See more
Shared insights
on
DartDartFlutterFlutter

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

thank you

See more
NativeScript logo

NativeScript

521
1K
516
Build truly native apps with JavaScript
521
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
    No need for Mac to build iOS apps in Telerik Platform
  • 5
    Angular, typescript and javascript support
  • 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
    0 day support for new OS updates
  • 3
    Easiest of all other frameworks
  • 3
    Easy to learn
  • 3
    Backed by google
  • 3
    Live reload
  • 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

leonardo silveira
Software Engineer at Jobsity · | 5 upvotes · 210.7K 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

56
128
0
Truly native apps using Vue.js and NativeScript
56
128
+ 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

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

      related Ionic posts

      Saber Hosney
      Senior software engineer at Shortcut · | 7 upvotes · 128.2K views

      Greetings!

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

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

      See more
      Melanie Verstraete
      Shared insights
      on
      IonicIonicFlutterFlutter

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

      See more
      Xamarin logo

      Xamarin

      1.2K
      1.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
        Easy Debug and Trace
      • 7
        Use of third-party .NET libraries
      • 7
        It's free since Apr 2016
      • 7
        Best performance than other cross-platform
      • 7
        Open Source
      • 6
        Mac IDE (Xamarin Studio)
      • 6
        Xamarin.forms is the best, it's amazing
      • 5
        Power of C#, no javascript, visual studio
      • 5
        C# mult paradigm language
      • 4
        Compatible to develop Hybrid apps
      • 4
        Microsoft backed
      • 4
        Microsoft stack
      • 4
        Great docs
      • 4
        That just work for every scenario
      • 3
        Well Designed
      • 3
        Small learning curve for Mobile developers
      • 2
        Ability to leverage legacy C and C++
      • 2
        Ionic
      CONS OF XAMARIN
      • 9
        Build times
      • 5
        Visual Studio
      • 3
        Complexity
      • 3
        Scalability
      • 3
        Price
      • 2
        Nuget
      • 2
        Maturity
      • 2
        Build Tools
      • 2
        Support
      • 0
        Maturidade
      • 0
        Performance

      related Xamarin posts

      Greg Neumann

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

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

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

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

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

      See more
      William Miller

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

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

      Any thoughts would be much appreciated.

      See more