On 2016-12-18 4:16 PM, Karl Dubost wrote: > When reading a thread about a new API or feature such as… > > Le 16 déc. 2016 à 04:39, Ehsan Akhgari <ehsan.akhg...@gmail.com> a écrit : >> From what I remember, the argument for shipping >> this API was that web developers have been asking for this for years, >> and they are basically happy to know the distinction between cellular >> data and other transports, and infer whether the connection "costs >> money". > > > I have always in the back of my mind: > > * How does it give control (benefits) to > - users? > - web developers? > - UX/Designers? > - marketers/analytics crunchers/BD? > > Maybe there is a bit more user research (or maybe Marcos knows this already) > to do in what users want to do? I guess we all have our own ideas about it. > > Mine would be more give me a possibility to choose in the chrome what type of > assets/performances I desire. I am on high performance bandwidth/latency > network, but I want low-res, because I just want speed (the same way I would > access a mobile domain m. for quick access on desktop). Or give me the > high-res pictures on my slow network because I really need this high quality > images I want to share with someone else and/or print.
The only potential for user control through this API is if a noticeable portion of websites used this API to decide whether to give the users a "low-res" version, and for the browser to provide some kind of a UI to allow the user to override the information the browser receives from the OS about your network connection. As things stand now, neither of the above are true to the best of my knowledge. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
