The Challenge We Didn’t Expect

Building features is hard.

Scaling infrastructure is hard.

But the real challenge turned out to be something else entirely:

> Understanding how users actually think.

As developers, it’s easy to build interfaces based on our own assumptions. We know how the system works internally, so everything feels logical to us.

But users don’t see the product the way we do.

And that changes everything.

The UI Problem Is More Psychological Than Technical

A user interface isn’t just buttons and layouts.

It’s:

Expectations
Habits
Intuition
Emotions
Decision-making behavior

The difficult part is understanding:

How users expect something to work
What feels natural to them
What confuses them immediately
What they ignore completely

And often, users won’t tell you directly.

They simply leave.

Why Developer Perspective Can Be Dangerous

One of the biggest mistakes product teams make is this:

> Designing for themselves instead of for real users.

As creators of the platform, we already know:

Where everything is
What every button does
How the flows are intended to work

But first-time users don’t have that context.

That means even “obvious” interfaces can become confusing in practice.

Tracking Helps—But It Has Limits

To better understand user behavior, we track a lot of interactions inside the platform:

Searches
Session creation
Queue actions
Click behavior
Flow progression

This data helps us identify:

Where users hesitate
Where they leave
Which actions succeed
Which parts create friction

But there’s another challenge:

> Tracking is no longer as reliable as it used to be.

The Adblocker Problem

Modern privacy tools and adblockers increasingly interfere with analytics and tracking systems.

That means:

Some user actions never get recorded
Session behavior becomes incomplete
Funnels become harder to interpret
Important insights can disappear entirely

This creates a difficult situation:

We want to improve the product experience—but we can only optimize what we can actually observe.

Building Better UX Requires Empathy

The biggest lesson we’re learning is this:

> Good UI design starts with empathy, not code.

We constantly have to ask ourselves:

What would a new user expect here?
Is this truly intuitive—or only intuitive to us?
What creates uncertainty?
What slows people down?

Because ultimately:

Users don’t care how technically advanced something is if it feels confusing to use.

The Continuous Process of Improvement

Understanding users is not a one-time task.

It’s an ongoing process of:

Observing behavior
Testing assumptions
Improving flows
Simplifying interactions
Removing friction wherever possible

The UI is never “finished.”

It evolves alongside the users.

Why This Matters So Much

A fast backend and powerful features are important.

But if users don’t understand how to use the product comfortably and naturally, none of that matters.

That’s why UI and UX are now among our highest priorities moving forward.

Not because they look good—but because they directly determine whether users stay or leave.

Final Thoughts

The deeper we go into product development, the clearer one thing becomes:

> Building technology is easier than understanding people.

And yet, understanding people is exactly what creates truly great products.

We’ll continue refining the interface, learning from behavior, and improving the experience step by step.

Because every smoother interaction makes the platform better for everyone.

Experience the Platform Yourself

We’re continuously improving the experience based on real user behavior and real-world usage.

Try the tool today, create a session, search for songs, and experience how collaborative music voting is evolving with every improvement we make.

The Hardest Part of Building an App? Understanding How Users Actually Think