Would love to see results! I’m thinking about doing a small cafe user study and asking for people to rate the experience with a slightly more build out version of reactive.surge.sh, but of course real user behavior data wins every time so would love that one day!
On the stylesheet is totally fine!
And unfortunately I’ve not really dug into stable loads + responsive images. I remember thinking before that this could be tricky, but now it seems to me that since we know the ratio of the image (the important bit) everything should just work…… would want to try it and prove it though…
I tried this and at least for me, the children content appears in the DOM but doesn’t actually visually show up in the page itself, and I’ve not yet found a way to have it show up. (DOM ended up like this FWIW: http://imgur.com/a/AjSIJ)
That delay doesn’t apply any more (in modern browsers at least) so long as the page sets a mobile viewport, see https://developers.google.com/web/updates/2013/12/300ms-tap-delay-gone-away
Well there are definitely issues here (ordered least significant to most)
On low end devices this is especially bad, I haven’t looked into fetch specifically, but in general the amount of time you block the main thread for is how delayed the animation of CSS toggle is.
Thanks a lot for the thoughts, definitely a lot to think about.
I did follow the Origin Chip work as closely as one could at the time (as someone that didn’t directly work on it), but I’d be interested to get your thoughts and takeaways from it.
Thanks for writing!
Some thoughts — I can’t find convincing evidence that “installability” is particularly useful to users on desktop. Icons are so important on mobile as typing is hard and everything is driven from the home screen. The fact that 87% of time is spent in native apps underline this.