DEV Community: rushyhirosan

Why Nobody Came — A Product Distribution Lesson

rushyhirosan — Sun, 01 Mar 2026 23:25:27 +0000

I launched my trend dashboard.

After three days, it had 6 views.

Probably half of them were mine.

At first, I thought I had a marketing problem.

But after thinking more carefully, I realized something else:

I didn’t have a traffic problem.

I had a distribution design problem.

The Illusion of “If You Build It, They Will Come”

Like many indie developers, I believed:

The idea makes sense
The product works
The interface is clean

Therefore:

People will naturally discover and use it.

This belief is comforting.

It is also wrong.

Discovery is not automatic.

It is engineered.

I Built Supply. I Didn’t Build Demand.

The dashboard aggregated trend data from Japan and the US.

It was fast.

It worked.

It solved a logical problem: fragmentation.

But I skipped a critical step.

I never asked:

Who is urgently looking for this?
Where are they already spending time?
Why would they switch to my tool?

In product terms:

I built supply.

I didn’t build a demand engine.

Launch Is Not Distribution

I posted about the product on:

Medium
Dev.to
Zenn
A few communities

I considered that “launch.”

But that was exposure.

Not distribution.

Distribution is not a moment.

It’s a system.

A repeatable mechanism that consistently puts your product in front of the right people.

I had no such system.

No Clear Target User

“People interested in trends” is not a user segment.

It’s a vague category.

Without a specific user:

There is no focused messaging.
There is no obvious channel.
There is no clear urgency.

And without urgency, there is no growth.

Why Starting with Japan Didn’t Solve It

As a Japanese developer, I started by aggregating Japan’s trends before expanding to the US.

This made sense strategically:

I understood the language.
I understood the media landscape.
I had contextual familiarity.

But informational advantage does not equal distribution advantage.

Even in your “home market,”

attention must be earned.

Being local does not guarantee visibility.

The Core Lesson: Distribution Is Part of the Product

I treated distribution as something that happens after building.

That was the mistake.

Distribution is not marketing.

It is product design.

If your product depends on people accidentally finding it,
you have already embedded fragility into the system.

Visibility is not optional.

It is a feature.

What I’m Rethinking Now

Instead of asking:

“How can I get more views?”

I’m asking:

Who exactly is this for?
What urgent problem does it solve?
Where do those users already gather?
How does the product naturally spread?

Because traffic is not vanity.

It is validation.

Final Reflection

Six views felt disappointing.

But they revealed something important.

The product didn’t fail.

The growth system didn’t exist.

And that is a far more useful lesson.

If you're curious about the product itself,

you can try it here:

👉 Trend Dashboard

Building a Stateless Dashboard: Why I Chose Not to Store History

rushyhirosan — Wed, 04 Feb 2026 23:27:50 +0000

Why I Built Yet Another Trend Dashboard

As a developer, I often check trends for ideas, learning, or simple curiosity.

Search trends, social media, videos, podcasts, news.

At some point, I realized something uncomfortable:

I was spending more time tracking trends than actually thinking or building.

Many tools are optimized for deep analysis:

Long-term graphs
Historical comparisons
Detailed metrics

Those are useful — but not always.

Most days, what I really want is much simpler:

“What’s happening right now?”

A Constraint I Chose on Purpose

When I started this project, I made one very deliberate decision:

The dashboard does not store historical data.

At first glance, that sounds like a missing feature.

In reality, it’s the core design.

No history means:

No overanalysis
No pressure to keep up
No sense that you’re “behind”

You open the page, scan the signals, and move on.

If you didn’t see today’s trends, that’s fine.

Tomorrow will already look different.

Why One Trend Source Isn’t Enough

Google Trends is powerful, but it reflects only search behavior.

It doesn’t fully show:

What creators are publishing today
What people are watching or listening to
Where attention is moving, not just being searched

Trends aren’t a single graph.

They’re signals scattered across platforms.

That’s why this dashboard focuses on aggregating current trends from multiple sources, rather than going deep into one.

What the Dashboard Actually Does

The dashboard shows:

Search trends
Video trends
Podcast trends
Other media signals

Everything is:

Read-only
Stateless
Focused entirely on the present

There are no accounts, no saved preferences, and no personalization.

You don’t “use” it for long.

You just check it.

🔗 Live demo:

https://trends-dashboard.fly.dev/us

Why the Dashboard Focuses on US and Japan

This dashboard currently focuses on two regions: the US and Japan.

The US is an obvious choice.

Many global trends — in technology, media, and culture — tend to emerge there first.

Japan, on the other hand, plays a different role.

Some trends arrive later, some evolve differently, and some exist almost entirely within the local context.

By placing US and Japan side by side, it becomes easier to notice those differences.

This isn’t meant to be a comprehensive global view.

It’s a deliberate contrast — between where trends often start and how they appear in a different environment.

That contrast is part of what makes watching trends interesting to me.

How I Approached Building It

I started with a straightforward implementation and iterated quickly.

Instead of optimizing architecture early, I focused on:

Fast feedback loops
Clear, calm UI
Reducing cognitive load

I did use AI-assisted tools along the way, but this wasn’t about technical novelty.

It was an exercise in deciding what not to build.

Possible Improvements (Carefully)

Even with this constraint, I do think about future improvements.

Some ideas:

Lightweight history Short snapshots, not full analytics
Email digests Daily or weekly trend summaries you don’t have to actively check
More sources Industry-specific or regional signals

There’s one rule, though:

If a feature turns awareness into work, it doesn’t belong here.

A Preference for “Just Enough”

This product reflects a preference I have when it comes to software.

I tend to like tools that are:

Calm
Lightweight
Respectful of attention

Not everything needs to be stored.

Not everything needs to be optimized.

Sometimes, awareness alone is sufficient.

In Japanese, there’s a word I like: 「ほどほど」 — just enough.

This dashboard is my attempt to apply that idea to modern software design.

Ephemeral by Design

Many products treat history as value.

Here, impermanence is the value.

Trends fade.

Attention shifts.

So the tool should, too.

Closing Thoughts

Most dashboards try to answer:

“What happened?”

This one asks:

“What’s happening?”

And then it steps aside.

If you’re interested in building:

Stateless tools
Minimal products
Or software that intentionally does less

I’d love to hear your thoughts.