4 ms·
This point is addressed in the article, the point is not to have web app perform as fast or better than native app. As long as they are fast enough it's ok. I'
by hrktb 11y ago
This point is addressed in the article, the point is not to have web app perform as fast or better than native app. As long as they are fast enough it's ok.
I'll support this point: for so many services I'd be ok to trade off native performance for a smoother install process and independance from arbitrary rules. For instance amazon kindle app is severly limited by the app store rules while it has arguably no features that need to be native and does have almost no performance need (I wouldn't care if it took 250ms instead of 100ms to turn pages)
Same goes with apps like google keep or to do list apps. Whole categories of app would be better off as locally installed web apps, if only the OS had better support for them.
- Narishma 11y ago> This point is addressed in the article, the point is not to have web app perform as fast or better than native app. As long as they are fast enough it's ok. That may be true if you only care about performance, but what about battery usage? That's something important on a phone.
- hrktb 11y agoWould the battery usage be much worse ? I get that taking more CPU time and doing less efficient operations will be worse, but this peaks would generally happen when the user is actively interacting, which in the running time of an app is not a lot. I would think the large majority of what this could be used for has less interactions and moving parts than the usual app. Of course someone would implement Quake in JS, but otherwise your note taking app or other utility (even a chat app) won't be actively sucking battery constantly.