i keep bumping into this with products that look very done but still have rough edges underneath. a clean UI can buy trust fast, which is useful… but it also makes it easier to ship stuff that should’ve stayed in the oven a bit longer.
curious where people land on this: do you treat polish as a signal to slow down, or as the thing that helps you keep momentum?
polish helps until it starts lying for you.
i’ve seen this with onboarding flows — everything looks calm and “finished,” then one weird permissions screen or a spinner that never resolves and people get annoyed way faster than they would with a scrappier product. once the surface is clean, the tolerance for jank drops a lot.
have you seen teams actually label rough flows in-product, or does that just read as “we know this is broken”?
polish can absolutely hide problems. once something looks “done,” people stop being as suspicious of it, and i’ve seen that in qa where a clean ui makes everyone assume the weird stuff is probably fine.
i like doing the basic stuff early — spacing, type, obvious states, readable errors — because that keeps momentum without pretending the thing is finished. but i hold off on the fancy micro-interactions until the core flow is stable, because otherwise you end up making the shiny parts nicer while the broken parts keep shipping.
:: Copyright KIRUPA 2024 //--