Alternatives to VoltBuilder logo

Alternatives to VoltBuilder

PhoneGap, Onsen UI, Ionic, Apache Cordova, and React Native are the most popular alternatives and competitors to VoltBuilder.
2
6
+ 1
0

What is VoltBuilder and what are its top alternatives?

It is a SaaS to make Android and iOS native apps from Single Page Apps.is designed to be a modern implementation of PhoneGap Build.
VoltBuilder is a tool in the Cross-Platform Mobile Development category of a tech stack.

Top Alternatives to VoltBuilder

  • PhoneGap

    PhoneGap

    PhoneGap is a web platform that exposes native mobile device apis and data to JavaScript. PhoneGap is a distribution of Apache Cordova. PhoneGap allows you to use standard web technologies such as HTML5, CSS3, and JavaScript for cross-platform development, avoiding each mobile platforms' native development language. Applications execute within wrappers targeted to each platform, and rely on standards-compliant API bindings to access each device's sensors, data, and network status. ...

  • Onsen UI

    Onsen UI

    Onsen UI helps you develop both hybrid and web apps. If developing hybrid apps, you can use it with the Cordova / PhoneGap command line, or with Monaca tools (CLI, Monaca IDE - cloud-based IDE for Cordova, Localkit - desktop GUI). ...

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

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

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

  • Flutter

    Flutter

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

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

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

VoltBuilder alternatives & related posts

PhoneGap logo

PhoneGap

563
648
94
Easilily create mobile apps using HTML, CSS, and JavaScript
563
648
+ 1
94
PROS OF PHONEGAP
  • 46
    Javascript
  • 13
    Backed by Adobe
  • 11
    Free
  • 9
    Easy and developer friendly
  • 6
    Support more platforms
  • 3
    It's javascript, html, and css
  • 2
    Common code base across all mobile platform
  • 1
    Not bound to specific framework
  • 1
    Powerful Framework
  • 1
    Runs on mobile browser
  • 1
    Similar UI across all platform
  • 0
    Free easy fast and not buggy in my experience
CONS OF PHONEGAP
  • 2
    Never as good as a native app
  • 1
    Created for web pages, not for complex Apps
  • 1
    Poor user experience
  • 1
    Not build for high performance
  • 1
    Hard to see

related PhoneGap posts

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

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

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

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

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

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

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

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

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

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

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

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

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

See more
Sezgi Ulucam
Developer Advocate at Hasura · | 6 upvotes · 376K views

For a front end dev like me, using a mobile framework for side projects makes more sense than writing a native app. I had used Apache Cordova (formerly PhoneGap) before (because React Native didn't exist yet), and was happy with it. But once React Native came out, it made more sense to go that way instead. It's more efficient and smooth, since it doesn't have the simulation overhead, and has more access to hardware features. It feels cleaner since you don't need to deal with #WebView, using native UI widgets directly. I also considered Flutter . It looks promising, but is relatively new to the game, and React Native seems more stable for now.

MobileFrameworks #JavaScript NativeApps

See more
Onsen UI logo

Onsen UI

42
126
11
HTML5 Hybrid Mobile App UI Framework - work with Angular, React, Vue, Meteor & pure JavaScript. Material &...
42
126
+ 1
11
PROS OF ONSEN UI
  • 3
    Hybrid mobile
  • 3
    Works with any JavaScript framework
  • 3
    Allows for rapid prototyping
  • 2
    Free
CONS OF ONSEN UI
    Be the first to leave a con

    related Onsen UI posts

    Ionic logo

    Ionic

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

    related Ionic posts

    Saber Hosney
    Senior software engineer at Shortcut · | 7 upvotes · 66.8K 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
    Apache Cordova logo

    Apache Cordova

    675
    823
    208
    Platform for building native mobile applications using HTML, CSS and JavaScript
    675
    823
    + 1
    208
    PROS OF APACHE CORDOVA
    • 41
      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
      Easy debugging
    • 4
      Can use CSS3
    • 4
      Rich HTML 5
    • 3
      Rich css ui
    • 3
      HTML, CSS and JS
    • 3
      Fast and hot reload
    • 3
      Use what you code in your browser
    • 2
      One code base everywhere
    • 2
      Need a light system
    • 2
      Without extra tooling needed
    • 2
      Native Web Technologies
    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.6M 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
    React Native logo

    React Native

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

    related React Native posts

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

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

    See more
    Ganesa Vijayakumar
    Full Stack Coder | Module Lead · | 19 upvotes · 2.5M views

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

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

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

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

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

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

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

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

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

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

    Happy Coding! Suggestions are welcome! :)

    Thanks, Ganesa

    See more
    Flutter logo

    Flutter

    8K
    8.3K
    919
    Cross-platform mobile framework from Google
    8K
    8.3K
    + 1
    919
    PROS OF FLUTTER
    • 112
      Hot Reload
    • 91
      Cross platform
    • 91
      Performance
    • 73
      Backed by Google
    • 62
      Compiled into Native Code
    • 47
      Open Source
    • 46
      Fast Development
    • 43
      Fast Prototyping
    • 42
      Expressive and Flexible UI
    • 35
      Single Codebase
    • 32
      Reactive Programming
    • 26
      Material Design
    • 21
      Widget-based
    • 21
      Target to Fuchsia
    • 20
      Dart
    • 16
      IOS + Android
    • 13
      Easy to learn
    • 12
      You can use it as mobile, web, Server development
    • 12
      Great CLI Support
    • 12
      Tooling
    • 10
      Have built-in Material theme
    • 10
      Debugging quickly
    • 9
      Community
    • 9
      Support by multiple IDE: Android Studio, VS Code, XCode
    • 8
      Good docs & sample code
    • 8
      Written by Dart, which is easy to read code
    • 8
      Target to Android
    • 8
      Easy Testing Support
    • 7
      Target to iOS
    • 7
      Have built-in Cupertino theme
    • 6
      Easy to Unit Test
    • 6
      Easy to Widget Test
    • 6
      Real platform free framework of the future
    • 6
      Flutter is awesome
    CONS OF FLUTTER
    • 28
      Need to learn Dart
    • 10
      No 3D Graphics Engine Support
    • 9
      Lack of community support
    • 6
      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.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've been juggling with an app idea and am clueless about how to build it.

    A little about the app:

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

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

    I have two options:

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

    Xamarin

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

    NativeScript

    505
    994
    516
    Build truly native apps with JavaScript
    505
    994
    + 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
      Angular, typescript and javascript support
    • 5
      VS Code integration
    • 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
      Easy to learn
    • 3
      0 day support for new OS updates
    • 3
      Easiest of all other frameworks
    • 3
      Live reload
    • 3
      Backed by google
    • 3
      Access to entire native api
    • 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 Casa Magalhães · | 5 upvotes · 185.6K 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