User Tools

Site Tools


hybrid_apps:alternative_architecture_for_hybrid_applications

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
hybrid_apps:alternative_architecture_for_hybrid_applications [2017/11/06 16:54] – [A REST-based hybrid architecture] mithathybrid_apps:alternative_architecture_for_hybrid_applications [2022/06/16 19:57] (current) – [The conventional hybrid architecture] mithat
Line 5: Line 5:
 ===== The conventional hybrid architecture ===== ===== The conventional hybrid architecture =====
  
-{{:misc:conventional-hybrid.png|}}+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.
  
-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.+{{:misc:conventional-hybrid.png|}}
  
-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.+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.
  
 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. 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.
hybrid_apps/alternative_architecture_for_hybrid_applications.txt · Last modified: 2022/06/16 19:57 by mithat

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki