People can sense carelessness, even when they cannot see the code
People can sense carelessness. They cannot see the code, but they notice when something feels rushed or stitched together without thought.
Based on my February 2026 Next.js Melbourne talk about care, craft, and product quality.
Care is visible in the finished product
Care for the user shows up in small decisions: how quickly a page settles, whether the copy is clear, whether a form feels obvious, whether the product creates friction at the wrong moment.
Users sense when something is off before they can describe it. They are not inspecting code. They are reacting to the experience.
AI raises the floor, but it can flatten the result
AI makes it easy to produce competent output fast. It also makes it easy to stop too early and ship something that works but feels generic.
The risk is teams confuse speed with quality and ship the first plausible version instead of the considered one.
- A fast draft is not a finished product.
- Generated interfaces need stronger editing than teams expect.
- The closer a product is to the user, the more obvious careless details become.
What care looks like in practice
Care means being willing to edit. Cut awkward steps. Rewrite vague copy. Tighten motion. Simplify the hierarchy. Remove details that distract.
It also means being honest about where AI helps. AI is great at momentum. It is less reliable at deciding what should matter most to the user.
Fingertip after the MVP: a series of 1,000 small iterations
At Fingertip, care showed up as deliberate improvements after the MVP shipped. Each change was small. Together they transformed the experience.
Static list to drag-and-drop grid
The page editor started as a static list. We replaced it with a drag-and-drop grid that gave users real control over layout.
Sharing that matches reality
The default share preview was just the Fingertip logo. We replaced it with a live screenshot of the user's page via a headless render API.
Default shadcn to intentional system
Central icons, custom typography, taller inputs, and custom colours turned default shadcn into a considered design system.
Why this matters to me
My work sits between product, engineering, and design. Whether it was VenueSafe under time pressure, Fingertip growing into a broader SMB platform, or LinkApps at Linktree, the question stays the same: does this feel right to the user?
That is the standard. Not perfection. Not polish for its own sake. Enough care that the product feels deliberate.