hybrid_apps:alternative_architecture_for_hybrid_applications
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
hybrid_apps:alternative_architecture_for_hybrid_applications [2017/11/06 16:54] – [A REST-based hybrid architecture] mithat | hybrid_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 |
- | In this model, which to the best of my knowledge is used by [[http:// | + | {{:misc:conventional-hybrid.png|}} |
- | The UI is tightly bound in a one-to-one relationship with the app engine.((I' | + | Here, the UI is tightly bound in a one-to-one relationship with the app engine.((I' |
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