Add to Chrome
Add to Edge
Add to Firefox
Add to Opera
Add to Brave
Add to Safari
Join our communityTop Pro
•••
Top Pro
•••Top Pro
•••Top Pro
•••
Top Pro
•••Top Pro
•••
Top Pro
•••
Top Pro
•••Top Pro
•••
Top Con
•••
Top Pro
•••
Meteor can generate mobile (iOS and Android) apps from the same codebase as the web app, using the Cordova (PhoneGap) library (which brings native device functionality to JavaScript applications). Meteor-generated mobile apps are JavaScript, HTML and CSS bundles that run in a UIWebView (on iOS) or WebView (on Android). Apps can be run locally in the iOS/Android emulator, or on physical devices. You can also publish them to Google Play Store or Apple's App Store. Moreover, these hybrid mobile apps benefit from hot code push, which dramatically accelerates the development cycle. See More
A Meteor package can supply code for both the client and the server, and for mobile (Cordova) apps. For example, an autocomplete package supplies both server code to search a collection, and client code to display the results. The mdg:camera package supports the native camera if the app is built for mobile, or the HTML getUserMedia API to take pictures from the browser. See More
The same code can be run on both the server and the client, because Meteor is a full-stack JavaScript-everywhere platform. A common example of code that should run on both the client and the server is input validation - on the client for speed/UX, and on the server for security (the client can't be trusted). See More
Every time a change in the source file is saved, all connected clients will refresh automatically - browser tabs, mobile apps running in the simulator or on the physical device. Or, deploy a Meteor app (meteor deploy myapp) and all clients, plus all mobile apps with the server set to myapp.meteor.com will automatically reload to use the code changes. This drastically reduces the development cycle for apps in the App Store, where a regular update can wait for one to two weeks before being approved. See More
Meteor was developed with simplicity in mind, even for beginners who have just started using JavaScript frameworks. One of the reasons that beginners should start with Meteor is that Meteor is a full-stack framework, this way they can get the complete learning experience when it comes to web development (back-end and front-end development), all by using a single platform and a single language. Furthermore, Meteor does not have complex and esoteric concepts that may be hard to grasp by a beginner, it has a clear documentation and well-established coding conventions. There's also a very useful resource for learning Meteor in the form of a book: Discover Meteor, by the authors of many Meteor packages. See More
Meteor also has an official testing framework called Velocity. Velocity enables real-time unit testing and integration with Jasmine or Mocha syntax. Tests are automatically run when code is saved and the testing result is indicated by a green or red dot in the upper right corner of the app. See More
The community behind Meteor has created a useful application for debugging Meteor apps that will automatically delete collections and display client-side documents, allow you to control subscriptions and lets you modify the documents. Meteor also has great support for server-side debugging, and WebStorm has also released full support for Meteor, including debugging capabilities. See More
Feather can sync events happening in two different Node processes or even servers in real-time. For example: an event happens in server A, the user connected to server B is instantly notified of that event. This is done through a central Redis or Mongo collection or through a websocket libraries' clustering library. See More
Feathers makes extensive use of modules (which are called Feathers services). These services work like ExpressJS middleware and can be used with app.use('/path', serviceObject). Services help developers keep their applications modular and as minimal as possible, without any unnecessary libraries or bloat. See More
The built-in Waterline is not well designed and is not suitable for production environments. Populating more than 1 level deep is a nightmare, there is no transaction support, new features/bug fixes are not implemented anywhere near a timely manner (the most requested feature 'deep populate' has been lingering in their github issues list for over a year and a half now). See More
Sails helps a lot when starting a project, you simply run new appname to create a project skeleton. Then, for example if you want to create a Controller and Model you can run sails generate modelname. So you can create an application and a controller with just a couple of lines of code. See More