Thanks for the link. The article explains some basic stuff, useful indeed but unrelated to the macro architecture used by the service.
Also, I noticed that the content is displayed contextually. If you access Dev.to using incognito mode in browser the information is different compared to authenticated sessions.
I might be wrong, but the information is personalized based on (at least) two factors:
followed channels (this is a common technique)
cover item is updated if you already read that topic and refresh the page (I might be wrong on this)
This kind of "decision" should inject some decisional delay in the service speed. Well, Dev.to still scores 100 on Lighthouse, witch is amazing IMO.
Thanks for the link. The article explains some basic stuff, useful indeed but unrelated to the macro architecture used by the service.
Also, I noticed that the content is displayed contextually. If you access Dev.to using incognito mode in browser the information is different compared to authenticated sessions.
I might be wrong, but the information is personalized based on (at least) two factors:
This kind of "decision" should inject some decisional delay in the service speed. Well, Dev.to still scores 100 on Lighthouse, witch is amazing IMO.
Another neat thing we do if you're curious... π
Instant Webpages and Terabytes of Data Savings Through the Magic of Service Workers β¨
Ben Halpern γ» Dec 18 '19 γ» 5 min read
Thank you Ben. I'll get back with more questions :)