Alternatives to NativeScript-Vue logo

Alternatives to NativeScript-Vue

Vue Native, React Native, NativeScript, Flutter, and Weex are the most popular alternatives and competitors to NativeScript-Vue.
56
128
+ 1
0

What is NativeScript-Vue and what are its top alternatives?

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

Top Alternatives to NativeScript-Vue

  • Vue Native
    Vue Native

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

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

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

  • Flutter
    Flutter

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

  • Weex
    Weex

    Weex renders code in native widgets in Android & iOS and helps preserve the quality of user experience on critical platforms. ...

  • Ionic
    Ionic

    Free and open source, Ionic offers a library of mobile and desktop-optimized HTML, CSS and JS components for building highly interactive apps. Use with Angular, React, Vue, or plain JavaScript. ...

  • Xamarin
    Xamarin

    Xamarin’s Mono-based products enable .NET developers to use their existing code, libraries and tools (including Visual Studio*), as well as skills in .NET and the C# programming language, to create mobile applications for the industry’s most widely-used mobile devices, including Android-based smartphones and tablets, iPhone, iPad and iPod Touch. ...

  • Apache Cordova
    Apache Cordova

    Apache Cordova is a set of device APIs that allow a mobile app developer to access native device function such as the camera or accelerometer from JavaScript. Combined with a UI framework such as jQuery Mobile or Dojo Mobile or Sencha Touch, this allows a smartphone app to be developed with just HTML, CSS, and JavaScript. ...

NativeScript-Vue alternatives & related posts

Vue Native logo

Vue Native

98
725
57
Build cross platform native mobile apps using Vue.js
98
725
+ 1
57
PROS OF VUE NATIVE
  • 13
    Can use v-if, v-model and so on
  • 11
    Can be use with vuex and vue-router
  • 8
    Use .vue file instead of .js
  • 6
    Syntactic sugar
  • 5
    Single File Components
  • 5
    Easier to learn
  • 3
    Reactive programming
  • 3
    Great CLI
  • 3
    IOS + Android
CONS OF VUE NATIVE
  • 6
    Read more docs
  • 2
    Transpiles to React Native

related Vue Native posts

Shared insights
on
ReactReactVue NativeVue NativeVue.jsVue.js

I'm a huge fan of Vue.js and I'm pretty comfortable with it. I need to build a mobile app for my company and I was now wondering whether I could make use of VueJS with Vue Native instead of switching to React. I know Vue Native builds on top of RN. My question is whether I'd have as much freedom with Vue Native over RN and whether you feel like Vue Native is "production ready" or not. Not sure of which shortcomings I may find using Vue Native... Thanks a lot!!!

See more

Hi! I want to make a mobile app, but I am not sure if it is better to use Vue.js + Apache Cordova or Vue Native. I am a starter. I do not know anything about Vue nor React. Can someone recommend which one is better, please? Thank you :)

See more
React Native logo

React Native

26.4K
23K
1.1K
A framework for building native apps with React
26.4K
23K
+ 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
    Virtual Dom
  • 12
    Livereload
  • 11
    Insanely fast develop / test cycle
  • 10
    Great community
  • 9
    Easy setup
  • 9
    Backed by Facebook
  • 9
    It is free and open source
  • 8
    Native android components
  • 7
    Highly customizable
  • 6
    Scalable
  • 6
    Everything component
  • 6
    Awesome
  • 6
    Win win solution of hybrid app
  • 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
    Web development meets Mobile development
  • 2
    Hot reload
  • 2
    Over the air update (Flutter lacks)
  • 2
    'It's just react'
  • 2
    Many salary
  • 2
    Can be incrementally added to existing native apps
  • 1
    Nigger
  • 1
    Cons
  • 1
    Ngon
  • 0
    Ful
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
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 · 209.9K 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
Flutter logo

Flutter

10.8K
11K
1K
Cross-platform mobile framework from Google
10.8K
11K
+ 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
    Target to Fuchsia
  • 24
    Dart
  • 17
    IOS + Android
  • 14
    Easy to learn
  • 13
    Tooling
  • 13
    You can use it as mobile, web, Server development
  • 13
    Great CLI Support
  • 11
    Have built-in Material theme
  • 11
    Good docs & sample code
  • 11
    Debugging quickly
  • 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
    Real platform free framework of the future
  • 8
    Target to iOS
  • 8
    Have built-in Cupertino theme
  • 7
    Easy to Unit Test
  • 7
    Flutter is awesome
  • 7
    Easy to Widget Test
  • 1
    F
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
Weex logo

Weex

24
55
8
A framework for building Mobile cross-platform UI
24
55
+ 1
8
PROS OF WEEX
  • 2
    Backed by Apache and Alibaba
  • 2
    Hot reload
  • 1
    Cross platform
  • 1
    Web platform capable
  • 1
    VueJS based
  • 1
    Almost "batteries included"
CONS OF WEEX
  • 1
    Small support community
  • 1
    Los od docs written only in Chinesse
  • 1
    Lot of docs written only in Chinesse

related Weex posts

Ionic logo

Ionic

8K
7.4K
1.7K
A beautiful front-end framework for developing cross-platform apps with web technologies like Angular and React.
8K
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
    So much thought behind what developers actually need
  • 7
    Because of the productivity and easy for development
  • 7
    Fast, easy, free
  • 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 · 126.3K 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
Apache Cordova logo

Apache Cordova

692
853
211
Platform for building native mobile applications using HTML, CSS and JavaScript
692
853
+ 1
211
PROS OF APACHE CORDOVA
  • 44
    Lots of plugins
  • 34
    JavaScript
  • 26
    Great community
  • 23
    Easy Development
  • 18
    Easy to learn
  • 15
    Cross platform
  • 7
    Open Source
  • 6
    Easy, fast, not buggy in my experience with my code
  • 6
    Lots of descendants; PhoneGap, Ionic, Intel XDA etc
  • 4
    Can use CSS3
  • 4
    Easy debugging
  • 4
    Rich HTML 5
  • 3
    Use what you code in your browser
  • 3
    Fast and hot reload
  • 3
    Rich css ui
  • 3
    HTML, CSS and JS
  • 2
    Need a light system
  • 2
    Native Web Technologies
  • 2
    Without extra tooling needed
  • 2
    One code base everywhere
CONS OF APACHE CORDOVA
  • 2
    No native performance
  • 1
    Hard to install
  • 0
    Hard to install

related Apache Cordova posts

Jonathan Pugh
Software Engineer / Project Manager / Technical Architect · | 25 upvotes · 1.8M views

I needed to choose a full stack of tools for cross platform mobile application design & development. After much research and trying different tools, these are what I came up with that work for me today:

For the client coding I chose Framework7 because of its performance, easy learning curve, and very well designed, beautiful UI widgets. I think it's perfect for solo development or small teams. I didn't like React Native. It felt heavy to me and rigid. Framework7 allows the use of #CSS3, which I think is the best technology to come out of the #WWW movement. No other tech has been able to allow designers and developers to develop such flexible, high performance, customisable user interface elements that are highly responsive and hardware accelerated before. Now #CSS3 includes variables and flexboxes it is truly a powerful language and there is no longer a need for preprocessors such as #SCSS / #Sass / #less. React Native contains a very limited interpretation of #CSS3 which I found very frustrating after using #CSS3 for some years already and knowing its powerful features. The other very nice feature of Framework7 is that you can even build for the browser if you want your app to be available for desktop web browsers. The latest release also includes the ability to build for #Electron so you can have MacOS, Windows and Linux desktop apps. This is not possible with React Native yet.

Framework7 runs on top of Apache Cordova. Cordova and webviews have been slated as being slow in the past. Having a game developer background I found the tweeks to make it run as smooth as silk. One of those tweeks is to use WKWebView. Another important one was using srcset on images.

I use #Template7 for the for the templating system which is a no-nonsense mobile-centric #HandleBars style extensible templating system. It's easy to write custom helpers for, is fast and has a small footprint. I'm not forced into a new paradigm or learning some new syntax. It operates with standard JavaScript, HTML5 and CSS 3. It's written by the developer of Framework7 and so dovetails with it as expected.

I configured TypeScript to work with the latest version of Framework7. I consider TypeScript to be one of the best creations to come out of Microsoft in some time. They must have an amazing team working on it. It's very powerful and flexible. It helps you catch a lot of bugs and also provides code completion in supporting IDEs. So for my IDE I use Visual Studio Code which is a blazingly fast and silky smooth editor that integrates seamlessly with TypeScript for the ultimate type checking setup (both products are produced by Microsoft).

I use Webpack and Babel to compile the JavaScript. TypeScript can compile to JavaScript directly but Babel offers a few more options and polyfills so you can use the latest (and even prerelease) JavaScript features today and compile to be backwards compatible with virtually any browser. My favorite recent addition is "optional chaining" which greatly simplifies and increases readability of a number of sections of my code dealing with getting and setting data in nested objects.

I use some Ruby scripts to process images with ImageMagick and pngquant to optimise for size and even auto insert responsive image code into the HTML5. Ruby is the ultimate cross platform scripting language. Even as your scripts become large, Ruby allows you to refactor your code easily and make it Object Oriented if necessary. I find it the quickest and easiest way to maintain certain aspects of my build process.

For the user interface design and prototyping I use Figma. Figma has an almost identical user interface to #Sketch but has the added advantage of being cross platform (MacOS and Windows). Its real-time collaboration features are outstanding and I use them a often as I work mostly on remote projects. Clients can collaborate in real-time and see changes I make as I make them. The clickable prototyping features in Figma are also very well designed and mean I can send clickable prototypes to clients to try user interface updates as they are made and get immediate feedback. I'm currently also evaluating the latest version of #AdobeXD as an alternative to Figma as it has the very cool auto-animate feature. It doesn't have real-time collaboration yet, but I heard it is proposed for 2019.

For the UI icons I use Font Awesome Pro. They have the largest selection and best looking icons you can find on the internet with several variations in styles so you can find most of the icons you want for standard projects.

For the backend I was using the #GraphCool Framework. As I later found out, #GraphQL still has some way to go in order to provide the full power of a mature graph query language so later in my project I ripped out #GraphCool and replaced it with CouchDB and Pouchdb. Primarily so I could provide good offline app support. CouchDB with Pouchdb is very flexible and efficient combination and overcomes some of the restrictions I found in #GraphQL and hence #GraphCool also. The most impressive and important feature of CouchDB is its replication. You can configure it in various ways for backups, fault tolerance, caching or conditional merging of databases. CouchDB and Pouchdb even supports storing, retrieving and serving binary or image data or other mime types. This removes a level of complexity usually present in database implementations where binary or image data is usually referenced through an #HTML5 link. With CouchDB and Pouchdb apps can operate offline and sync later, very efficiently, when the network connection is good.

I use PhoneGap when testing the app. It auto-reloads your app when its code is changed and you can also install it on Android phones to preview your app instantly. iOS is a bit more tricky cause of Apple's policies so it's not available on the App Store, but you can build it and install it yourself to your device.

So that's my latest mobile stack. What tools do you use? Have you tried these ones?

See more

We had contemplated a long time which #JavascriptMvcFrameworks to use, React and React Native vs AngularJS and Apache Cordova in both web and mobile. Eventually we chose react over angular since it was quicker to learn, less code for simple apps and quicker integration of third party javascript modules. for the full MVC we added Redux.js for state management and redux-saga for async calls and logic. since we also have mobile app along with the web, we can shere logic and model between web and mobile.

See more