News for hackers. Stuff that matters.
Re:Our best practices are killing mobile web performance by webartisan on Saturday May 21, 2016 @09:09AM (#11744548)
`navigation.connection` only tells if the user is on cellular/wifi. While this is certainly helpful, cellular connections themselves can vary enormously.
Re:Our best practices are killing mobile web performance by manigandham on Saturday May 21, 2016 @11:16AM (#11744929)
There is connection.type (bluetooth, cellular, ethernet, wifi, wimax, other, mixed, unknown, none) and connection.downlinkMax (megabits/sec of the first hop) both available.

You can read the W3C draft for more details: https://w3c.github.io/netinfo/

It's not perfect but far better than nothing. It's relatively easy to figure out a "slow" profile based on both device and connection and optimize some of the heavier resources.

Re:Our best practices are killing mobile web performance by Klathmon on Saturday May 21, 2016 @01:30PM (#11745418)
But even then there is only so much the application can (and should) do.

I don't want my application making decisions like trading download speed/size for battery life (better compression, etc...), or deciding to sacrifice quality because it thinks I don't want to wait.

We need APIs that let the useragents choose what they want, and let the users configure their useragent (or choose one that aligns with their ideas at the moment).

Like how srcset works, build APIs that let developers offer up several different assets, and let the useragent choose which is best for that moment (combining preferences for battery-life, connection speed, connection-capping and how close to the cap you are, preferred load time, and if it should "upgrade" to a better resource at a later time if possible)

Re:Our best practices are killing mobile web performance by manigandham on Saturday May 21, 2016 @02:07PM (#11745541)
Sure, better capabilities reporting + user control is the ideal. This will take a long time though considering how slow this all moves so incremental progress is still good until we get there.
Re:Our best practices are killing mobile web performance by hackney on Sunday May 22, 2016 @03:44AM (#11747699)
Very interesting, but how does requesting an optimized version of seemingly a gazillion different pages by a billion different authors magically make any of that happen? From what I've seen, web devs throw the kitchen sink even on mobile.
Re:Our best practices are killing mobile web performance by Dylan16807 on Saturday May 21, 2016 @04:14PM (#11746003)
I suppose that could be useful, but max downlink is the least useful metric they could have gone with. The times when I need traffic minimization the most also tend to be times when max downlink and average downlink are very far apart.
Re:Our best practices are killing mobile web performance by webartisan on Sunday May 22, 2016 @11:51AM (#11749025)
True, but the poor browser support for connection type and even poorer support for downlink means it cannot be relied on all the time.