4 ms·
It's not about being backwardly compatible (by and large most mobile browsers do a sterling job of that), it's about "friendly", which is to say, something whic
by mnem 11y ago
It's not about being backwardly compatible (by and large most mobile browsers do a sterling job of that), it's about "friendly", which is to say, something which works fairly well with common mobile devices. HN has pretty tiny fonts and very small hit areas for fat human fingers.
Mobile friendly isn't a meme, it's just a description of how well your chosen presentation of content translates into a different context of use. Context changes often require different choices about how you break up your content to throw at someone - this has been the case since the web began.
- jacquesm 11y agoFont sizes are hints that can (and should, when appropriate) be overruled locally. Shifting the layout burden to content supplied (and or javascript) was/is a huge mistake, the browser on the device should do the layout using whatever style hints it feels are appropriate.
- nfm 11y agoDo you think that's a problem that can be solved generically by the browser? It seems infeasible to me.
- jacquesm 11y agoYes, I think it could be, but it would require less focus on eye candy and more focus on functionality and utility. Works well, looks identical on all devices, is future proof: pick any two.
- thomasahle 11y agoWhat about something like the size of the up/down buttons? Should mobile browsers also automatically upscale those?