Are my users developers, or ordinary people whose experience is shaped by developers?

Let me clarify this for you with an analogy: Is your business a hardware store or a restaurant?

If your users are developers, then you're running a "hardware store."

The people who come to your store are "craftsmen" (developers). They buy drills, screwdrivers, pipes, and wires not to display them beautifully at home, but to use them to build houses and do renovations (develop software).

• What do they care about? Whether the tools are easy to use, efficient, professional enough, and compatible with other tools they already have. Telling them how great the "user experience" of a drill is won't help; they care more about RPM, power, and compatible drill bit sizes.
• What does your product look like? It might be a code library (a box of high-quality screws), an API interface (a pre-fabricated standard faucet), or a cloud service (a high-performance crane available for rent anytime). These things are incomprehensible and useless to ordinary people, but they are treasures in the hands of professionals.

If your users are ordinary people, then you're running a "restaurant."

The people who come here are "diners" (ordinary users). They come to eat, enjoy good food, and chat with friends.

• What do they care about? Whether the food tastes good, the environment is comfortable, the service is attentive, and the food is served quickly. They don't care what brand of pot you use in the kitchen, nor do they want to know how your chef (developer) managed to tenderize the beef. They just want the result: that delicious plate of braised beef.
• What does your product look like? An app, a website, a mini-program. Users tap a few times and can hail a car, order takeout, or watch interesting videos. The whole process should be smooth, simple, and enjoyable.

As for what you call "being dominated by developers," this is a very common "trap."

It's like a top chef opening his own restaurant. He's obsessed with the finest ingredients and the most complex cooking techniques, but the dishes he creates are either unpalatable to ordinary diners or they find them "too pretentious." The menu is written like a chemical formula, making it incomprehensible.

This is a typical example of "engineer's mindset" in product development: the functionality is powerful, but it's difficult to use, full of options and jargon that ordinary people don't understand. The product exudes a strong "code smell" rather than "human touch."

So, you can ask yourself a very simple question:

When your users are excited about your product, what exactly are they excited about?

• Is it because your product enables them to "build" other things faster and better? (Then your users are developers)
• Or is it because your product directly solves a problem in their lives, making them happier and more convenient? (Then your users are ordinary people)

Once you figure out this question, you'll know who your users are.