26
you are viewing a single comment's thread
view the rest of the comments
[-] bleistift2@sopuli.xyz 14 points 1 week ago* (last edited 1 week ago)

First do it, then do it right, then do it better. Get the ugly prototype in front of users.

I tend to agree with that one. I’ve heard it phrased “Don’t ask users what they want. They don’t know. Just give them something to work off of, because they most definitely know what they don’t want”.

But there’s a catch that I’ve seen twice now: If a feature doesn’t work correctly when you present it, users lose trust and avoid it. That could mean they use the ‘long way around’ when creating entities instead of just copy/pasting them, or that they unnecessarily refresh web pages instead of trusting the state that’s displayed to them.

Even when you tell them that their behaviour is … not optimal, they stick to it.

[-] Maestro@fedia.io 5 points 1 week ago

Don't give users an ugly prototype for exactly that reason. Also, users conflate looks and functionality so make it don't look ugly. You should give them an MVP. Emphasis on the V for "viable". The things it does it should do well. It should just do the minimum amount of things.

this post was submitted on 04 Jan 2026
26 points (96.4% liked)

Programming

24343 readers
287 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 2 years ago
MODERATORS