/articles/what-a-v1-should-feel-like
shell
all articles
article · grid
wahba.os · 2026
1 Apr 2026·4 min read·productcraftprocess

What a v1 should feel like

Polish isn't a v2 problem. It's the 10% that decides the v1.

Most v1s feel like a v1. Empty states without copy. Buttons that work but flash white. Errors that say “Something went wrong”. The product technically functions and emotionally tells the user “we’re not done yet”.

The fix isn’t scope. The fix is which 10% of polish you choose to ship. A v1 doesn’t need to be feature-complete. It needs to feel complete in the slice it covers.

The two scopes of a v1

Every v1 has a feature scope (what it does) and a finish scope (how well it does it). Most teams spend everything on the first and call the second a Phase 2 problem. Then Phase 2 never happens because users already decided.

Move 20% of the feature scope into the finish scope. The product will feel twice as expensive.

The list of things people notice immediately

  • The empty state.First thing a new user sees. If it’s a placeholder image with “No items yet”, you’ve already lost. Write copy. Suggest the next action. Make the empty state itself an onboarding moment.
  • The first interaction. The first click should feel alive. A small motion, a sound, a colour shift. Tactility is what makes a digital product feel made instead of generated.
  • Loading.A skeleton beats a spinner. A skeleton that animates beats a static one. A loading state that hints at what’s coming beats both.
  • Errors.The error state is where most products stop being products. “Something went wrong” is a surrender. Tell the user what failed, why, and what they can do.
  • The 404.Yes, the 404. It’s not vanity. Users who hit it think the team has stopped caring about the parts that don’t demo.

The thing nobody tells you about v1 polish

It’s cheaper than you think. Most of the items above take an hour each. The reason they don’t happen is nobody’s job to own “does this feel good”. Make it someone’s job. The whole product changes.

What “v1 done” should mean

Not “every feature”. Not “no bugs”. The bar I use is: a stranger can use the product alone for ten minutes and at no point think it’s broken or incomplete. That’s a v1. Anything below that is a beta. Anything above is a luxury you can pay for in v2.