Differences

This shows you the differences between two versions of the page.

--- hybrid_apps:alternative_architecture_for_hybrid_applications [2017/11/06 16:32] – [The conventional hybrid architecture] mithat
+++ hybrid_apps:alternative_architecture_for_hybrid_applications [2022/06/16 19:57] (current) – [The conventional hybrid architecture] mithat
@@ Line 4: / Line 4: @@
 ===== The conventional hybrid architecture =====
+In the conventional hybrid architecture used by [[http://electron.atom.io/|Electron]], [[http://nwjs.io/|NW.js]] and others, the user interface is rendered as HTML using whatever HTML, CSS, and front-end JS frameworks you desire. The primary aim of this architecture is to facilitate the use Web technologies for the UI.
 {{:misc:conventional-hybrid.png|}}
-In this model, which to the best of my knowledge is used by [[http://electron.atom.io/|Electron]], [[http://nwjs.io/|NW.js]] and others, the user interface is rendered as HTML using whatever HTML, CSS, and front-end JS frameworks you desire. The overriding goal of this architecture is to use Web technologies for the UI.
+Here, the UI is tightly bound in a one-to-one relationship with the app engine.((I'm using "app engine" generically here, not as a reference to Google's AppEngine.)) The app engine is implemented with Web back-end technology, typically Node.js. The app engine makes system calls through the engine's baked-in features or through generic ''child_process.exec()''-like calls. This means custom and platform-specific behaviors that the app may require will need to be implemented as external ''child_process.exec()'' callable units.
-The UI is tightly bound in a one-to-one relationship with the app engine.((I'm using "app engine" generically here, not as a reference to Google's AppEngine.)) The app engine is implemented with Web back-end technology, typically Node.js. The app engine makes system calls through the engine's baked-in features or through generic ''child_process.exec()''-like calls. This means custom and platform-specific behaviors that the app may require will need to be implemented as external ''child_process.exec()'' callable units.
 This architecture does a good job of leveraging Web technologies to create secure, conventional desktop apps. In addition, frameworks like Electron have matured to the point that developing hybrid apps that use many desktop app conventions is relatively easy.
@@ Line 19: / Line 19: @@
 {{:misc:alternative-hybrid.png|}}
-In this model, the tightly bound user<->app engine connection is replaced by a REST API. Thus the app engine becomes a REST server, possibly embellished with whatever superpowers are needed for accessing host resources. When the app interface is API driven, //any// REST client technology can be used for the interface, including HTML/CSS/JS clients, native mobile clients, terminal clients, etc. In addition, the client need not be local, making remote-controlled apps almost trivial to implement. Adequate measures must be taken to assure secure and authorized communication with the REST server.
+In this model, the tightly bound user<->app engine connection is replaced by a REST API. The app engine becomes a REST server, possibly embellished with whatever superpowers are needed for accessing host resources, and the UI is supported through a client. Because the app interface is API driven, any REST client technology can be used for the interface, including HTML/CSS/JS clients, native mobile clients, terminal clients, etc. In addition, the client need not be local, which makes remote-controlled apps almost trivial to implement. As with any network-based communication, adequate measures must be taken to assure secure communication with the REST server.
-The other change in the above model is that the REST server is implemented in any high-level language on which a REST server can be built. The ideal server language will be one that also supports the necessary system manipulations the application requires (file access, etc.)
-The two changes outlined above are decoupled---meaning that either can be adopted in the absence of the other.
+The REST server can be implemented in any language on which a REST server can be built. Thus the "app" language can be one that also supports the necessary system manipulations the application requires (file access, etc.) or is otherwise best-suited to the app's requirements.
-One obvious requirement is that the chosen language must be able to run on the target host platform. This isn't a significant issue with desktop deployment: typically, at most reconfiguring and/or rebuilding the REST server for each target platform is all that will be required. But it does currently present a problem for mobile deployment as few mobile platforms provide native support for more than one blessed development language.
+One obvious requirement is that the language chosen for the REST server language must be able to run on the target host platform. This isn't a significant issue for desktop deploymen. However, it does currently present a problem for mobile deployment as few mobile platforms provide native support for more than one blessed development language.
 --------------------------------------------------