zlacker

[parent] [thread] 2 comments
1. archag+(OP)[view] [source] 2017-07-27 13:41:34
Agreed -- squeezing these native app elements into the document-based paradigm of the web is a horrid, Frankenstein's monster of an idea. It's like doing app development in Excel.

If native web apps are to be more of a universal thing, I believe there ought to be a blank-canvas "meta-browser" layer that sits above the browser and that all web apps (including today's browsers) are built on top of. Basically a lightweight, sandboxed pseudo-OS that offers a robust standard library, a URL scheme and easy networking support, some sort of bytecode, maybe a UI toolkit, etc. Web apps would still take up the same amount of space and would still be able to run without installing, but they would now be endowed with native performance, app-specific features, and a consistent, functional UI. (Quiz: how often do your back/forward buttons fail when using, for example, your bank's website? The fact that these two ubiquitous controls simply break the web more often than not should be telling.)

Shoehorning all that stuff into a hyperlinked, navigable document browser is insanity, and you can always feel it unless your web-app has basically reimplemented the DOM from scratch[1]. The web is currently layered upside-down and I think web apps won't lose their reputation until this is fixed.

[1]: http://engineering.flipboard.com/2015/02/mobile-web

replies(1): >>_pdp_+Ng
2. _pdp_+Ng[view] [source] 2017-07-27 15:27:18
>>archag+(OP)
Literally all businesses are run on top of Excel, which, if you like, is sort of a generic app development environment.
replies(1): >>archag+ph
◧◩
3. archag+ph[view] [source] [discussion] 2017-07-27 15:32:41
>>_pdp_+Ng
I know, that's why I brought it up! Imagine if the user-facing app ecosystem of the future had to be built on top of that platform.
[go to top]