a short reflection on quality, written as a web engineer, after years of shipping things people actually pay for.
the thing nobody says about quality
steve jobs made a point once about japanese manufacturers - the companies with the strongest reputation for quality are the ones that never put the word “quality” in their ads.
the lesson stuck with me: reputation is the residue of experience, not the message. customers don’t decide your product is good because you told them. they decide after they use it.
on the web, there is no gate
there’s no app store review, and no install required to get started. yes, we have pwas - but installing one is a choice a user makes after they’ve tried it. the url loads first, and that’s it - the first paint is your pitch. whatever you shipped is what they experience, immediately, on a device and a network you don’t control.
and for us web engineers, it all goes back to the basics - html, css and js. how we write them, how we ship them, and how they come together to build an experience that makes a user feel something. that’s the craft.
the invisible work is the reputation
here’s what i’ve come to believe carries the most weight, and none of it shows up in a screenshot:
- performance - no layout shift, a skeleton that maps the real layout instead of a spinner.
- resilience - aborting a stale request when the user navigates away, surviving a flaky network.
- correctness - a form that keeps your input when the connection blips, a button that never charges twice.
- accessibility - a reduced-motion fallback, real focus states, contrast that holds.
a lot of this lives in plain css, and web.dev/css has some nice insights worth bookmarking. for example:
- css for web vitals - css patterns that keep layout shift and slow paints out of your pages.
- content-visibility - skip rendering work for content that’s off-screen until the user gets there.
- color and contrast accessibility - making sure your text is actually readable, for everyone.
- accessible tap targets - buttons big enough for a real thumb, on a real phone.
and if you’d rather see it built, gui challenges walks through real ui components - with the accessibility and responsive details done properly, not skipped.
a user never says “nice AbortSignal.” they don’t remember the code, they remember how it made them feel - calm, in control, never second-guessing a tap. that feeling is the sum of a hundred invisible decisions, and that feeling is the reputation.
so
the checkout that works on the first try. the page that doesn’t jump under your thumb. the input that’s still there after you lose signal in a lift. none of that is marketing. all of it is the argument.
so stop shipping the word. ship the thing, and let the browser make your case.
turn this into a review with craft-check
craft-check is an agent skill that checks your changes against this.
npx skills add mayeedwin/craft-check
similar write-up for reference: you can’t market your way to quality