Ask HN: How to fight back against Lovable, Replit, etc. in enterprise products
We're a very small startup with a web-based application written in React. Every non-engineer in the company spends a lot of time making screens in Lovable and thinks we can and should just "take that" and drop it on the site. We fight back, but even when we just use it as a design inspiration we're left with terrible UX, vastly different pages and a genuinely bad product that's just good enough not to be seen as a problem by the rest of the team. Help me make the case that we need a product designer, graphic designer, and to use these tools for what they're worth.
Sometimes you need regular meetings for workflows, like a retrospective meeting. You bring up problems, like bad UX. You analyze the cause of these problems. You don't jump to a solution (e.g. "Hey let's hire designers!!!").
Telling people to stop making incompetent designs just makes them defensive.
Do you have a product manager - someone who can take all these suggestions and turn them into something coherent?
Failing that. I would take a customer centric approach. What do you users think of these random UIs and features? What do they think your roadmap is? What do they think your product strategy is?
Telling people to stop making incompetent designs just makes them defensive.
Failing that. I would take a customer centric approach. What do you users think of these random UIs and features? What do they think your roadmap is? What do they think your product strategy is?