17 ms·
" we pay really attention to performance and it's a dream" Does this include in low-connectivity environments? The biggest advantage of api-driven PWAs is tha
by judge2020 5y ago
" we pay really attention to performance and it's a dream"
Does this include in low-connectivity environments? The biggest advantage of api-driven PWAs is that it supports no-connectivity and low-connectivity nicely, assuming you put effort into enabling it (having an offline cache of data) and having loading indicators visible to the user. With a regular page-load-driven application, if i'm on 1 bar of 4G I might get the TTFB for a page load and then be waiting as page assets slowly load in, staring at a white or half-blank screen the entire time.
- new_stranger 5y agoIronically though, phones usually struggle more with single-page apps / Javascript heavy sites which have all the client-side application logic, 3rd party libraries, and DOM re-renders based on state changes.
- allan_s 5y agoexactly ! most browser will wait for the next to load before unloading the current one so with a little css trick you can do a nice transition between pages While most SPA will put you on a weird state (of course you can handle it nicely too, but it requires effort for something you had for free in the first)
- allan_s 5y agowe certainly can sure improve on that side but currently most of our pages are at most 2 https call 1. html of that page, they never go over 30kb non gzipped, most svg assets are inline, so once you got it, you got it. 2. the tailwind.css file, that is cached after the first page. so even if you feel fancy and you use graphql, you can't do less 1 http call right ?