"A completely native app-one that runs without the need for a web UI-is likely your best choice when you have the following criteria: A web UI isn't vital. For example, a lightweight command-line tool could have an optional web interface for convenience but doesn't need it to function. The size of the deliverable matters. (The command-line tool example also fits here.) You want as few layers as possible between the app and the operating system or the underlying system."
"A web UI makes most sense when: The size of the deliverable is negotiable. The ease of using web components for the front end is essential to the app's ongoing development. It is acceptable to work with the underlying system through the abstractions provided by the browser. The front end doesn't need to have the lowest possible latency with the back end. (Or when any performance-sensitive behavior can be moved into the browser.)"
A completely native app is preferable when a web UI is not vital, deliverable size matters, minimal layers between the app and operating system are desired, or the UI requires minimal latency that browsers cannot accommodate. Examples include lightweight command-line tools that may optionally include a convenience web interface without functional dependence. A web UI is preferable when deliverable size is negotiable, using web components eases ongoing frontend development, working through browser-provided abstractions is acceptable, or frontend-backend latency constraints can be addressed by moving performance-sensitive behavior into the browser. Local and web apps continue to blur, while desktops and command-line tools retain advantages.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]