Live data from Hacker News

Test your product on a crappy laptop

css-tricks.com

251–260 of 321 posts

Re: Test your product on a crappy laptop

#251

> British soldiers in World War I were equipped with a Brodie helmet, a steel hat designed to protect its wearer from overhead blasts and shrapnel while conducting trench warfare. After its deployment, field hospitals saw an uptick in soldiers with severe head injuries. > Because of the rise in injuries, British command considered going back to the drawing board with the helmet’s design. Fortunately, a statistician p…

We apply this kind of thinking at work: early on we focused all our energy fixing user problems or adding features that were requested. We realised it is actually a small number of users who volunteer to report to us what's wrong or missing (outside of regular crash/feature tracking) - they are the ones that care enough to make an effort, and it's a small percentage. So we started campaigning to engage users we never…

Way back in the day I was a lone IT guy in a distributor/wholesaler, and part of that was creating line of business apps to do some real heavy lifting, extending existing ones, and creating utilities to tie other apps together. In a tiny company of maybe 40 people, where even an underpaid IT guy was still an extravagance (but was adding huge value).

Periodically I'd ask to shadow someone for a day or two. At some points, even asking if I could do their task and have them watch me to confirm I was doing it correctly.

What you would learn from this was amazing. All sorts of inefficiencies that people would quietly accept, because it was still way better than the previous state.

Then a week or two later I'd roll out the update, and get huge thank yous from accounting, or sales, or the warehouse because I completely trivialized some previous common task. What used to take 45 seconds now takes 2 because all the work is done for them 99.9% of the time and they just need to confirm it's correct (or correct the odd edge case). The computer became this increasingly magical tool they loved more and more.

Re: Test your product on a crappy laptop

#252

The same survivor bias analogy goes for usage of Firefox and Javascript in general. "Our users dont block JS and are 99% on Chrome." Because the tech savvy users just block your surveillance stuff.

But we anyway don't care about people who block our ads

Re: Test your product on a crappy laptop

#253

> British soldiers in World War I were equipped with a Brodie helmet, a steel hat designed to protect its wearer from overhead blasts and shrapnel while conducting trench warfare. After its deployment, field hospitals saw an uptick in soldiers with severe head injuries. > Because of the rise in injuries, British command considered going back to the drawing board with the helmet’s design. Fortunately, a statistician p…

https://en.wikipedia.org/wiki/Survivorship_bias#In_the_milit...

Re: Test your product on a crappy laptop

#254

It's not just developers, and it's not just about speed, it's also designers / UX bods who need to heed this. My decently powered work laptop from job 1 has a fairly rubbish screen, which means that a lot of the subtle hover effects, 1 pixel light grey on lighter grey divisions and skinny fonts either aren't visible or are incredibly difficult to see. A good trick if you're working on a large, hi res screen is to hav…

I work in web development at a major, well-known company. My top of mind is exactly what the article is reflecting: how will this product/feature perform on a craptop/low power ChromeOS device/cheap smartphone that isn't even sold in the U.S.? I can say first hand that our designers do not care about this. I have never heard any concerns around this even so much as uttered. I think part of this is due to a rigid 'design system' that, if adjusted to better accommodate for our craptop, etc. users, would require updating many other products to keep consistent. Thus, the problem is handwaved away with "that problem is only reflected on x% of DAU."

There is so much design/development guidance around screen width, breakpoints, contrast ratio, accessibility and so forth, but so little around "real world" testing on low-tier devices. Every designer is using a 5K display with perfect color and definition, or an iMac with a super fast processor and tons of memory; our users are not.

Re: Test your product on a crappy laptop

#255
post #215

Earlier quoted context omitted.

Indeed. Buy a crappy 15 year old LCD TV with HDMI and hook it up. Most of the really cheap Chinese models have terrible gamma that means half the colors look the same.

I highly recommend setting (non-HDR) screens to sRGB color mode or at least gamma, to have at least decent color reproduction.

Yes, do this if you want to actually use the screen properly. But do not do this if you want to test how awful your content looks on other people's setups.

Re: Test your product on a crappy laptop

#256
post #41

There are three kinds of web developers: - Those who don't care about performance, as long as it loads within a few seconds on their own beefed up system on the LAN. This article is for them, and we can only hope they will listen. - Those who care about performance, and work for people who care. They are already doing great work (or are about to), producing those rare low-friction, high-speed, content-is-king sites w…

"This article is for them, and we can only hope they will listen."

By my reckoning: everybody assumes that this article is for somebody else, and that's the problem. Assuming the problem is either developers who don't care or developers who don't have enough agency to act on it is easy because we can say "I care, and I have agency, so I'm not part of the problem."

Hanlon's razor applies here, but the related incompetence stems from competent people doing things outside their areas of expertise rather than being fundamentally incompetent. The developer discussion focusing almost exclusively on performance reinforces that. We favor our strongest mental models when reasoning about problems— when you're a hammer, everything looks like a nail.

But we often contribute to or create things outside our direct areas of expertise, (often reluctantly because we're the last people to touch the code before it hits production.) We might not even 'realize' how far outside they are, though. In my experience, this testing reveals far fewer performance problems than interface design and front-end implementation problems— i.e. touch targets are nearly impossible to use on burner smart phones, sidebars that clobber content or top menu bars that wrap between break points, weird behavior on non-widescreen landscape orientation devices, poor keyboard (and therefore screen reader) navigation, etc.

I believe this discussion illustrates the importance of thoughtful and skillfully-applied UX principles, where the data would ideally come from real users operating as they normally would... but maybe that's just the nail this particular hammer is hunting for! XD

Re: Test your product on a crappy laptop

#257
post #73
post #41

There are three kinds of web developers: - Those who don't care about performance, as long as it loads within a few seconds on their own beefed up system on the LAN. This article is for them, and we can only hope they will listen. - Those who care about performance, and work for people who care. They are already doing great work (or are about to), producing those rare low-friction, high-speed, content-is-king sites w…

Explain Gmail.

Gmail is an AdTech-funded, no-charge email service operated by Google, a popular internet services subsidiary of Alphabet Inc.

Re: Test your product on a crappy laptop

#258
post #175
post #164

Earlier quoted context omitted.

In my personal experience, even getting an average web dev to touch a slower Windows machine is mission impossible. The best you can hope is "ewww, this sucks so much and it's ugly, why would anyone do this" and then arrogant walk back to their 3000$+ MacBook to shovel more JS libraries into the website. I've literally not seen a single rockstart javascripter actually willingly try to test things on Windows, much les…

Come to Europe, most of those designers will be using Windows machines issued by IT to everyone on the building anyway. And the only Apple gear will be iPhones and iPads used by upper management. Yes, I am also aware there are plenty of cases that aren't like that specially for the fortunate ones living on tier 1 EU countries.

(Waiting for company issue M1 Pro MBP)

Re: Test your product on a crappy laptop

#259
The article omitted an important aspect: craptops have crappy screens with terrible contrast. It makes some elements really hard to discern, even though they look fantastic on your development machine.

The screen size can also have an impact. Developers rarely use 1366x768 monitors, or even low DPI displays.

There's also internet speed. Wired internet is fast, but people use your website on crappy hotel wifi, or in the underground.

Re: Test your product on a crappy laptop

#260
post #259

The article omitted an important aspect: craptops have crappy screens with terrible contrast. It makes some elements really hard to discern, even though they look fantastic on your development machine. The screen size can also have an impact. Developers rarely use 1366x768 monitors, or even low DPI displays. There's also internet speed. Wired internet is fast, but people use your website on crappy hotel wifi, or in t…

This also applies to desktops. Where contrast and brightness can be anywhere and they might even be placed in direct sunlight...
Post reply on HN