Small UX details that real products teach you

I used to think UX was the main flow.
Onboarding, checkout, player, profile, all the important screens.
The main flow matters.
But real products are tested in the small moments around it.
The button label. The empty state. The loading screen. The error message. The long title that breaks the card.
That sounds like polish.
Important, but still polish.
It becomes product quality very fast.
A button that says "Start your journey" may look nice, but the user still has to guess what happens next.
A button that says "Listen to your first episode for free" does more work.
Same layout. Better decision for the user.
So words are design?
Yes. Users do not use rectangles. They read what the rectangle says.
Before making the screen pretty, ask what the user needs to know first, what action they should take, and what words may create doubt.
What else should I check early?
Use real content as soon as possible.
Fake content makes weak layouts look safe.
A show title looks clean when it is one line. Then the real title becomes three lines and the whole card starts fighting for space.
And the weird states?
Loading, empty, failed, no internet, that kind of thing?
Design them like product screens, not leftovers.
If there is no data, explain why. If payment fails, show the next step. If upload stops, keep the file name and let the user retry.
The happy path is only one version of the product.
Where does accessibility fit in this?
It is basic hygiene.
Can people read the text? Can they tap the control? Does the state work without color alone? Does the screen survive sunlight, a small phone, and one hand?
A low-contrast screen may look premium in Figma and fail in real life.
When should engineering come in?
Before the design starts pretending everything is easy.
Ask if the data loads fast enough, if the component already exists, what happens when the API fails, and what is expensive.
Users do not use the Figma file. They use what gets built.
So the small stuff is not small.
Exactly.
Write real content early. Test long text. Design loading, empty, error, and success states. Bring engineering in early. QA the built product.
The main flow is the center. The full product is everything around it.