"falsehoods developers believe about screens" ?
For example, "What every programmer should know about memory" covers memory but what about (as you say) screens.
11–20 of 399 posts
"falsehoods developers believe about screens" ?
For example, "What every programmer should know about memory" covers memory but what about (as you say) screens.
Just because my horizontal resolution is around 1200, I am not on a tablet. It's amazing how many websites are incredibly unusable when displayed 2-up on my 27" monitor. There's so much screen estate, but I often literally have to resize the window to fullscreen to find a search or login field.
This is the worst when you're displaying two sites side by side on a 1080p screen.
There should IMO be a preference sent, "I'm on a portable, touch-enabled device". I'm guessing it doesn't exist because it would add a bit to the fingerprint.
"falsehoods developers believe about screens" ?
Building responsive client UI is hard. In my experience here, the falsehoods HNers believe about clients is that it's somehow not hard. Or just a silver bullet away from being easy (like replacing JS with $faveLang). Or that resources are infinite such that every defect is explained by incompetence (except for, presumably, that HNer who is intimately familiar with resource finitude in their own life).
For my personal projects, screen size is the factor used to determine layout. Mobile/tablet/laptop/desktop is irrelevant. My goal with smaller viewports is to make the layout as similar as possible, without the user having to scroll horizontally. Because I don't want to change the layout too much, I do not use hidden navigation menus.
Hamburger menus are terrible - I see them as a design copout.
var dppx = window.devicePixelRatio;
var screenWidth = screen.width * dppx;
var screenHeight = screen.height * dppx;"falsehoods developers believe about screens" ?
The rabbit hole is websites are supposed to cater for every screen size by pixel is ridiculous. At some point the user should respectfully use normal orientated/ sized device.
CSS dpi media queries are unsupported in Safari mobile and desktop, so that increases the complexity significantly.
Beyond that, the fact is most web layout is still done in px or other non-fraction-of-the-width units, so it’s often a matter of the wider layout simply being broken at smaller widths, rather than just refusing the display.