Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[docs] How to avoid fetching different assets during fluctuations #28

Open
astronomersiva opened this issue Nov 20, 2019 · 2 comments
Open
Labels
documentation Improvements or additions to documentation

Comments

@astronomersiva
Copy link

Consider this scenario:

My phone is connected to WiFi(4g), the power goes off, and my mobile data(2g) kicks into action. If there were multiple assets fetched for 4g, all their low quality equivalents will now be fetched.
This will also happen when I am travelling between places as my data speed keeps fluctuating.

I am not sure what the solution to this problem is but I believe we shouldn't be replacing assets that are already fully loaded.

@addyosmani
Copy link
Collaborator

This is a good gotcha to raise awareness around. We have thought about this and documented one pattern for addressing over-fetching using Service Workers in https://github.com/GoogleChromeLabs/adaptive-loading/tree/master/cra-network-aware-only-if-cached-loading.

I'm going to rename this issue and keep it open as a reminder to add a docs or wiki entry about how to address this particular consideration in a little more detail.

@addyosmani addyosmani changed the title Might consume more data than needed [docs] How to avoid fetching different assets during fluctuations Nov 20, 2019
@addyosmani addyosmani added the documentation Improvements or additions to documentation label Nov 20, 2019
@anton-karlovskiy
Copy link
Contributor

anton-karlovskiy commented Nov 20, 2019

@addyosmani

I think we have one more approach which is not landed yet.
GoogleChromeLabs/adaptive-loading#27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants