Talking about cross-platform toolkits, there is no “best of the best” technology. Business requirements are first, technology will follow. In this article, I’ll explain how React Native works to give you an understandinMore
RAD.js – A Breakthrough In Cross-Platform
MobiDev is happy to announce the release of our brand new software framework!
We support the projects and initiatives of our employees. The most recent and significant project among these is a software framework for cross-platform development. It is a result of collective work and it’s named RAD.js. How and why is it useful for software developers and business owners?
For businesses, it’s crucial to look for new clients and reach the existing ones across several platforms (at least two: iOS and Android). But the most fully-featured applications used to be created by native development only, which always means a separate project for each chosen mobile platform. With the help of such tools as RAD.js, cross-platform comes closer to equal with native development in capabilities and performance. It also takes less time: there is only one project with adjustments to the chosen platforms (which anyway requires much less time and budget than two or more projects).
RAD.js is a system-level software framework which helps build a single-page cross-platform application that looks and feels as a conventional multi-page one. Now cross-platform software of high quality can be created faster and easier than before. This framework was created by JS/HTML team of MobiDev, under the guidance of the leading PhoneGap specialist Yuriy Luchaninov.
Its features and advantages include:
- optimization for iOS, Android, Windows Phone 8;
- optimization for PhoneGap and mobile browsers (Chrome, Firefox, Opera, Safari, IE 10);
- ability to dynamically control (create and delete) module instances of the application through the functionality of the core, at both view level and application level;
- ability to build an application consisting of loosely bound modules: models, views, services (application part without visual representation), and the object of the application;
- tree-structured messaging;
- debug mode of the core and messages;
- flexible and loosely bound architecture – almost any extraneous code can be enveloped by the module with several lines of code. Failure of a module doesn’t cause failure of the whole application;
- ability to monitor the lifecycle of view and services. Callback methods for all lifecycle events;
- templating. A template is an HTML file that can be created separately;
- partial templating of view. Ability to determine parts of the view template, that will or will not be rerendered by changes of data within a model;
- ability to extend functionality of the core via plugins;
- complex embedded views and declarative transition animations between them;
- ability to inherit views, services and models;
- modal and non-modal self-positioning windows;
- dynamic routing;
- reuse of modules in other projects;
- module testing can be performed through external frameworks.