Even if your ecosystem has a ton of momentum, if the ceiling is low it doesn't matter.

For example, if your system requires users to take an action on the command line, you've set a ceiling.

The ceiling of the audience of a tool is set by what the worst case outcome is that might show up more than 5% of the time.

If when it breaks you have to tweak JavaScript then only programmers will be able to use it.

Or, if a user needs to use the command line to set it up.

The population of users that will be willing or able to use your thing is now set very low.

Sometimes if it has enough momentum it's possible to build an easier-to-use version to get lower-savviness users in.

But just as often, it's extremely hard to cross that rubicon.

If your system takes for granted that early users will use the command line, and "we'll figure out a different UX for less savvy users later", you might back yourself into a corner and have no good options.

This effect is especially strong when the most friction is felt at initial onboarding.

The savvy users are already boarded onto the ecosystem, they never again feel the friction and it doesn't loom large for them.

The friction of first use to them felt like a few gentle rolling hills they've long forgotten about.

But the friction of first use can be like the Himalayas for new users who are less savvy.

You get boxed in by the Himalayas; they set a horizon for your ecosystem that it can't expand beyond.

If you want to change the whole world, the ceiling has to be in the stratosphere.

Every user of software in the world should ultimately use it, otherwise it doesn't matter.

You can have all of the builders or developers in the world, but if you don't get any of the generic population, it doesn't matter.