There's a difference between a primary use case and a secondary use case.

A primary use case is one whose expected value for a user is greater than its expected cost.

This difference gives a gradient of activation energy to lead to more adoption.

The gradient need not be large; it's better to be dependably a little above the bar than sometimes way above the bar but often below it.

A secondary use case is one that doesn't qualify as a primary use case, perhaps because:

The quality can be great but is often below the bar

The use case isn't good enough to activate usage on its own but can ride the coattails of another feature

You can't lead a value proposition with a secondary use case; it's not dependable enough.

But often the primary long-term value arises from the secondary use case (especially when there's some kind of self-improving quality of it, e.g. a network effect).

You have to lead with your primary use case and sprinkle in the secondary use case as a bonus, at least to start.