mozilla / coss

Mozilla's Community Support Software
https://discourse.mozilla-community.org/t/iam-coss-work-week-jan-2017/13497
Mozilla Public License 2.0
19 stars 20 forks source link

How to design and build for low bandwidth #95

Open kristinashu opened 7 years ago

kristinashu commented 7 years ago

I will make design notes on what we need to show vs what is bonus content (e.g. images).

Can we do a query to see what bandwidth a user has and then give them the appropriate version of our site?

cc @Pomax @alanmoo

alanmoo commented 7 years ago

Nope, bandwidth queries are notoriously not-a-thing. There are many ways to prepare for low-bandwidth user experiences, but directly checking for it is not one of them.

Pomax commented 7 years ago

progressive enhancements are pretty much the only "known" solution at the moment

a-kilroy commented 7 years ago

This basically means we can determine the order in which things load so that critical content is prioritized. Did I express this well?

kristinashu commented 7 years ago

Sounds good to me.

alanmoo commented 7 years ago

Along those lines, yes. Things like offering multiple image sources (low res, high res, etc), reducing HTTP requests, and only loading content that's most likely to be seen (don't load all the images at once, etc.)

mbransn commented 7 years ago

Re: content loading - lazy loading?

And does mezzanine have something like image transforms available? This being something we set on the technical side, not expecting our admin users to handle transform specs.

Including a focal point on images when they're uploaded will help the transforms be most affective as well (see #90). This is something our admin users would set when they upload an image.

alanmoo commented 7 years ago

Yup, lazy loading, but used judiciously. I'm not sure about image transforms, I've used a service to handle that before (I think it was Cloudinary). Depending on what we're trying to do, that might be worth separately investigating.