A lot of valid points on the downsides to the design.
But from a progressive enhancement perspective it's an interesting approach. The users who benefit from this are the ones with a slow connection and old phone, with the desktop + broadband users paying the penalty.
As a desktop user, I don't like progressive enhancement especially as the content I'm trying to read bounces around the page as it gets built.
If the goal is to optimise the user experience, I would have thought a nicer way (for the user, not so for the developer) would be to create content bundles for the different responsive modes and get it served up server side based on interrogating the user agent and looking up which support html5 etc.
But from a progressive enhancement perspective it's an interesting approach. The users who benefit from this are the ones with a slow connection and old phone, with the desktop + broadband users paying the penalty.
As a desktop user, I don't like progressive enhancement especially as the content I'm trying to read bounces around the page as it gets built.
If the goal is to optimise the user experience, I would have thought a nicer way (for the user, not so for the developer) would be to create content bundles for the different responsive modes and get it served up server side based on interrogating the user agent and looking up which support html5 etc.