Join the DZone community and get the full member experience.Join For Free
1. JQuery Mobile
JQuery is a popular framework building mobile apps that can easily be accessed through a variety of devices, including touch-enabled devices. It is easy to integrate with third-party technologies and this expands its application area.
With HTML5 and CSS3, a developer can easily achieve custom-made user interface for his/her mobile application. The latest version of JQuery features a lightweight code base, which helps optimize the speed.
- Easy to develop, if you understand HTML(HTML5) you will have pretty good understanding of jQuery Mobile
- Excellent 3rd party support, what through knowledge what through plugins
- Easy to debug
- Better for mobile web applications
- Official documentation
- Sometimes slow and sluggish on mobile devices, application needs to be designed properly
- Dull look unless you are capable UI designer. All applications look the same, and it looks pretty bad on large screens
Stay Informed- Popular Hybrid App Development Frameworks of 2015
2. AngularJS 2.0 & 1.x
After the most awaited official release of AngularJS 2.0, the popularity of the framework has reached a new level in today’s time. However, this is still a risky decision to jump to the new version if you are not so sure. Let us help your decision with this flowchart:
Whatever the conclusion you come to, you must admit that AngularJS (maintained by Google) has the capacity to build web applications like no other. With a rapid development pace, easy code integration, readiness for unit testing AngulatJS can certainly be you choice for next project.
- Good documentation.
- Two-way data binding simplifies some parts of the process.
- Two-way data binding checks for changes in the data model, which may lead to possible issues with performance and faster draining the battery of the device.
- Difficulties with understanding the code and debugging.
- Substantial framework size.
Stay Informed- Angular 2.0: Why Should You Upgrade?
However, while comparing with AngularJS, ReactJS falls short in testing simplicity and component structure. Also, needless to say, this does not make ReactJS fall far from AngularJS.
- It is quite easy to be mastered.
- It is easy to maintain isolated components in React.
- Constant re-rendering of components provides efficient arranging at increasing complexity.
- Convenient architecture – Flux – is highly competitive to MVC. One-way data flow provides maintainability and efficient arrangement of data and DOM elements.
- It is the most light-weighted framework among the ones that are widely used today.
- Some issues with DOM manipulation libraries are possible (e.g., jQuery).
- Frequent re-rendering may slow down the work of application at handling a large set of data.
4. Appcelerator Titanium
This open-source platform is more popular for developing cross-platform native apps. One can easily learn the framework to quickly build apps to be run on different platforms.
With a basic web development skill, one can build scalable apps, based on the MVC pattern. The framework allows developers to take better advantage of the native functionality of a device and include custom features.
- By using native UI components, we achieve a distinct performance win;
- The Alloy framework works to normalize the UI across platforms;
- Added value is realized being that Appcelerator provides items such as App Analytics and Backend-as-a-Service (BaaS);
- Titanium is free, as well as open-source.
- Developers must manage platform SDKs locally; it’s recommended that you maintain a controlled build environment – a continuous integration (CI) process – particularly when targeting multiple platforms.
- SDK- related issues, due to versions and build, can rob time that is always better-suited to the delivery of product and features.
- The normalization of the UI across platforms, generally viewed as a Pro, can be a Con that requires the team to train on proprietary technology, and these skills are not applicable outside Titanium.
- Highly flexible. You can choose not to implement some features (e.g Controller) based on your requirement.
- It is tightly integrated with underscore.js which is great.
- Designed more towards consuming REST data.
- More complex initially if compared to knockout.js.
- All the PhoneGap apps can be installed much like a native app, and are able to leverage app store discoverability.
- It follows a plug-in architecture, which indirectly means that access to the native device APIs can be extended in a modular way.
- Using PhoneGap would enable you to distribute and integrate payment through the app store.
- Leverage from tons of libraries.
- If your mobile app includes too many graphic elements, performance could be a big issue.
Which one are you planning to use in 2017? Let us know in the comments.
Published at DZone with permission of Ryan Roy. See the original article here.
Opinions expressed by DZone contributors are their own.