Intel INDE Multi-OS Engine
Not so long ago, in early August, at the Android Developer Conference (Andevcon) 2015, held in Boston, Intel announced INDE Multi-OS Engine, a framework for developing native cross-platform Java applications.
Development of applications that work simultaneously on iOS and Android, can not be called either fast or cheap. Until recently, if you wanted to launch an application for two of the most popular mobile platforms at once, you had a difficult choice. On the one hand, you could use a cross-platform tool, such as Cordova , and as a result get a relatively inexpensive application with a fairly high-quality, but at the same time very limited UI / UX.
')
On the other hand, you had the opportunity to develop two separate native applications:
Both approaches have their pros and cons. However, even for large companies with serious resources, this choice was not easy. But the situation is changing. Now, developers can try Intel's Multi-OS Engine (MOE), which is specifically designed to significantly reduce the development time needed to create separate native Android and iOS applications:
As you may know, Intel INDE is a cross-platform toolkit for creating native mobile applications. INDE consists of a number of SDKs, libraries, compilers, debuggers, and performance analysis utilities — all that is required for a full software development cycle. A Multi-OS Engine can be called a real “cherry” on the “cake” INDE!
The modern user of mobile applications is very sophisticated, and shops for any platform are filled with a huge number of analogues. How to stand out among them? I myself, from two similar applications, rather choose the one that looks and feels truly consistent with the entire system. Even though the development of native applications takes more time, the native “Look & Feel” is exactly what the end users are paying attention to, which means you simply cannot save money on it. For a number of reasons, native applications have a significant advantage in this area:
To answer this question, it is enough to refer to the following schedule:
The GitHub language rating, based on the amount of code stored in its repositories, clearly explains why Javascript was chosen as the cross-platform development language for React Native on Facebook and Intel chose Java for the Multi-OS Engine .
Multi-OS Engine comes as a plug-in for Android Studio. With it, you can create a new MOE project, or add a MOE module to an existing project. Thus, you do not need to know Objective-C to write native iOS applications. At the same time, the development for Android does not undergo any changes. But you have a great opportunity to reuse all platform-independent code. MOE does not offer a 100% reuse code, but with the right architecture, this value can reach 60%.
Here's how the Multi-OS Engine provides Java support on iOS:
All this allows you to immediately start writing iOS applications in Java.
To try the Multi-OS Engine, you can tell us a little about yourself through a special form . This will allow us to make MOE even better. But if you can not wait, you can immediately go to the download page: I want MOE right now! On this page you will find a detailed user manual.
PS
The team developing the Multi-OS Engine is almost entirely located in Russia (Nizhny Novgorod and Moscow). And if you have questions that you want to ask in person, you have a great opportunity to attend the Droidcon conference in Moscow on September 26th.
Development of applications that work simultaneously on iOS and Android, can not be called either fast or cheap. Until recently, if you wanted to launch an application for two of the most popular mobile platforms at once, you had a difficult choice. On the one hand, you could use a cross-platform tool, such as Cordova , and as a result get a relatively inexpensive application with a fairly high-quality, but at the same time very limited UI / UX.
')
On the other hand, you had the opportunity to develop two separate native applications:
Both approaches have their pros and cons. However, even for large companies with serious resources, this choice was not easy. But the situation is changing. Now, developers can try Intel's Multi-OS Engine (MOE), which is specifically designed to significantly reduce the development time needed to create separate native Android and iOS applications:
As you may know, Intel INDE is a cross-platform toolkit for creating native mobile applications. INDE consists of a number of SDKs, libraries, compilers, debuggers, and performance analysis utilities — all that is required for a full software development cycle. A Multi-OS Engine can be called a real “cherry” on the “cake” INDE!
Why is being native so important?
The modern user of mobile applications is very sophisticated, and shops for any platform are filled with a huge number of analogues. How to stand out among them? I myself, from two similar applications, rather choose the one that looks and feels truly consistent with the entire system. Even though the development of native applications takes more time, the native “Look & Feel” is exactly what the end users are paying attention to, which means you simply cannot save money on it. For a number of reasons, native applications have a significant advantage in this area:
- Direct access to the specific platform UI components: application navigation stack, date and time selection dialogs, maps, etc. Without a doubt, you can recreate all these components yourself, but our re-implementation will never feel as native as the native one. Such home-made components also will not receive any automatic updates along with changes in the platform.
- No overhead associated with UI rendering.
- Native multithreading. Web-based frameworks do not allow the application to be parallelized as it is possible in native code.
Why Java?
To answer this question, it is enough to refer to the following schedule:
The GitHub language rating, based on the amount of code stored in its repositories, clearly explains why Javascript was chosen as the cross-platform development language for React Native on Facebook and Intel chose Java for the Multi-OS Engine .
Technical details
Multi-OS Engine comes as a plug-in for Android Studio. With it, you can create a new MOE project, or add a MOE module to an existing project. Thus, you do not need to know Objective-C to write native iOS applications. At the same time, the development for Android does not undergo any changes. But you have a great opportunity to reuse all platform-independent code. MOE does not offer a 100% reuse code, but with the right architecture, this value can reach 60%.
Here's how the Multi-OS Engine provides Java support on iOS:
- Automatically generates banding on ObjectiveC and C header files
- Uses special Java annotations
- Associates Java with Native Code with the NatJ Library
- Eliminates the need for JNI calls
- Fully covers iOS API
All this allows you to immediately start writing iOS applications in Java.
Java application development process
- Create a Multi-OS Engine project in Android Studio
- If you are using a Mac, add a new Run / Debug configuration “Intel MOE iOS Application” for building on a local machine. On a Windows host, an “Intel MOE Remote Build” configuration is available for building “in the cloud”.
- You can create UI directly in XCode or use the special MOE UI designer, built-in Android Studio.
- Associate your UI with Java using the annotation and the NatJ library.
- Use code completion for easy work with iOS SDK.
- iOS applications can be run on the simulator and device directly from Android Studio.
- Debug your apps right in Android Studio.
To try the Multi-OS Engine, you can tell us a little about yourself through a special form . This will allow us to make MOE even better. But if you can not wait, you can immediately go to the download page: I want MOE right now! On this page you will find a detailed user manual.
PS
The team developing the Multi-OS Engine is almost entirely located in Russia (Nizhny Novgorod and Moscow). And if you have questions that you want to ask in person, you have a great opportunity to attend the Droidcon conference in Moscow on September 26th.
Source: https://habr.com/ru/post/266653/
All Articles