4 ms·
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.
- iamflimflam1 10mo agoDo 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?
- muzani 10mo agoSometimes 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.
- brazukadev 10mo agostart by not using React. Using React is not a competitive advantage as it is a bad framework with security issues. To fight back, you need to use different tools that the big players can't use. What tool is that is up to you to figure out, otherwise this would be easy.
- odla 10mo agoSolving a people problem by rewriting your entire app seems less than ideal
- odla 10mo agoimo we don’t want to discourage non technical people from sharing ideas. But it’s the role of a product manager to push back, extract the “why” from these mockups, and set expectations that the UI will be reinterpreted by the product team using existing design systems.