What would an opinionated framework look like if it focused on building multi-page PWAs?
-
-
Replying to @asolove
It's a different problem from building an SPA with server rendering. Needs a sharper distinction between server and browser contexts.
1 reply 0 retweets 1 like -
Replying to @asolove
Should output chunks of static html suitable for a CDN, where all user-specific info is rendered client-side by JS.
1 reply 0 retweets 0 likes -
Replying to @asolove
And a pre-packaged solution for building the service worker, stream ops, distinguishing which requests get http2 server push added, etc.
1 reply 0 retweets 1 like -
Replying to @asolove
: I actually think that starting with a WordPress plugin might be the right way to go.
2 replies 0 retweets 2 likes -
Replying to @slightlylate
That's one market. But there's also a market for the edge-cached, API-backed, mostly-static site. At least where I work.
1 reply 0 retweets 0 likes
: yeah; I think the needs are roughly similar (from the SW perspective). If you're doing static site generation, can be simpler.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.