I was browsing Flipkart the other day, doing something pretty routine—comparing products.
Nothing fancy. Just scanning titles, checking specs, trying to find the right model.
At one point, I needed the model number from a product title. The title was long, so it was truncated with an ellipsis. Fair enough—that's common.
So I clicked on it.
The full title appeared.
Good.
Then I tried to select the model number.
And it disappeared.
here's the link
The small moment that turned into friction
I clicked again. It expanded.
I tried to select again.
Collapsed.
Now I'm clicking more carefully. Slower. Adjusting my mouse like I'm defusing a bomb.
Expand. Collapse. Expand. Collapse.
All I wanted was a few characters from a product title.
Instead, I found myself fighting the interface.
What's actually going on here?
At first glance, this feels like a minor annoyance. But if you zoom in, it's a collision of multiple design decisions:
- The title is truncated to keep the layout clean
- Clicking it expands the full text
- Clicking it again collapses it
- The same text is also selectable
Each of these decisions is reasonable on its own.
Together, they create friction.
The real problem: one element, multiple intentions
The title is trying to do too much.
It's acting as:
- A display element (to read)
- A control (to expand/collapse)
- A selectable field (to interact with text)
And that's where things break.
Because user intent isn't that complicated:
- Sometimes I want to read more
- Sometimes I want to copy something
- Sometimes I just want to scan quickly
But the interface treats all of these as the same action: click the text
That overlap creates ambiguity—and friction.
The issue isn't "temporary"—it's fragile
The expanded state doesn't disappear on its own.
It disappears because of how easy it is to accidentally trigger collapse.
And that's the real problem.
Clicking is required for both:
- Expanding/collapsing
- Beginning text selection
So even though the system is technically consistent (click toggles state), it conflicts with natural user behavior.
The UI isn't unstable—it's too sensitive to the same interaction users need for something else.
The bigger insight: micro-interactions can block real goals
I wasn't trying to "interact with a title."
I was trying to:
- Compare products
- Verify specifications
- Maybe search that model elsewhere
The expanding/collapsing behavior wasn't helping me do that.
It was getting in the way.
That's the subtle danger of micro-interactions:
A tiny detail—like how text expands—can quietly block a meaningful user task.
A principle worth remembering
If there's one takeaway from this, it's this:
Don't overload a single element with multiple competing interactions.
Or even simpler:
Separate reading from acting.
Text is usually for reading (and sometimes selecting). Controls are for actions.
When one element tries to do both, users pay the price.
What could work better?
This isn't a hard problem to fix. Just a matter of being intentional.
A few better approaches:
- Let the title expand on click, but don't collapse it on the same element
- Add a small, clear "expand/collapse" control separate from the text
- May be allow multi-line wrapping based on length instead of aggressive truncation
None of these are complex.
But they respect user intent.
Why this matters more than it seems
Moments like this don't usually make users quit instantly.
But they do something more subtle:
- They introduce hesitation
- They create small frustrations
- They make the product feel just a little less intuitive
And over time, those small moments add up.
Final thought
Good UX isn't just about clean layouts or clever interactions.
It's about making sure nothing gets in the way of what the user came to do.
Because if a user has to fight the interface to complete a simple task—
the design, no matter how polished, is already working against them.
Top comments (0)