Very impressive engineering on the whole stack. The question that arises to my mind is, maybe even too much engineering?<p>Hard to understand the architecture when there is so many moving parts which makes me not want to use it for my own stuff. Because if I don't know how it works how can I fix/change it when I have to? Also the loader icons last for worryingly long time when I'm running it on my localhost. Which means the caching isn't working as it's supposed to or should it really take that long to load a single webpage? Not trying to attack on anyone here, just observing.<p>How is your serviceWorker configured? The problem I have had with them is the N+1 (or sometimes more) times it takes to reload changes which is infuriating to me and I've stopped using them altogether since the benefits aren't that great (for me at least).<p>Maybe if you could bootstrap with this step by step it would be easier to get to know the structure a little better. So say you could first bootstrap à la create-react-app with bare minimum to get things rolling and then add on caching features which there seems to be plenty of.
FYI react-create-app also has PWA features: <a href="https://github.com/facebookincubator/create-react-app/blob/master/packages/react-scripts/template/README.md#making-a-progressive-web-app" rel="nofollow">https://github.com/facebookincubator/create-react-app/blob/m...</a>
Initial page load: 279kb
Click on 'Features': 1.58Mb (40 requests)
Click on 'PWA': 2.88Mb (74 requests)
...<p>If you visit this page on mobile and start to scroll down while it's still loading, you'll have to scroll down multiple time because the loaded content resets the scrollbar (Firefox on Android)<p>Top comment: 'Impressive engineering on the whole stack'<p>Really?
The website is getting hugged, ouch.<p>Still, it seems perfectly possible to integrate this boilerplate with create-react-app using custom scripts if anyone is interested
Please visit <a href="https://github.com/Atyantik/react-pwa" rel="nofollow">https://github.com/Atyantik/react-pwa</a> if the site is down
Have we solved the issue of server-side rendering + code splitting? I see both in features, but last time we attempted this, we had to give up one of those features.
hey - pretty cool. I wonder if you can incorporate something like Netflix's optimization<p><a href="https://news.ycombinator.com/item?id=15567657" rel="nofollow">https://news.ycombinator.com/item?id=15567657</a>
Website does not load. Same as <a href="https://github.com/vuejs-templates/pwa" rel="nofollow">https://github.com/vuejs-templates/pwa</a> for react?
This is such a coincidence. I was looking for such thing today and found few projects that are from last year and abandoned. Wondered why this is and thought about doing it myself.<p>...<p>Aww, this is such a mess. I am sorry but this project is making me think twice before using it.<p>Look at the creators website... php tags visible
<a href="https://www.atyantik.com/" rel="nofollow">https://www.atyantik.com/</a><p>A lot of comments on slow loading and site not being available. I appreciate your desire to use and share new technology, but this might be too early for this project.<p>Wish you luck!