Collaboration in Loveable feels too much like coding, especially with version control and CI/CD processes like protecting main branches and requiring pull requests. The user needs a more intuitive, less technical way for teams to manage these aspects, making collaboration smoother for non-technical users.
Collaboration shouldn’t feel like coding. But in Loveable, it does. For the last 3 months, I’ve been building Fractional First's talent platform with Daniel Sit. We've been able to map out ideas and turn them into working interfaces faster than ever. Daniel isn’t technical, but he can jump right in and help shape things. That’s a huge win. We create beautiful prototypes quickly. The massive speed unlock is real. But when it comes to collaborating, things start to break down. Loveable’s version control sounds good on paper: It easily plugs into GitHub, making changes on separate branches. By default, there's a two-way sync between what happens on Lovable and what happens on GitHub. But even simple CI/CD stuff, like protecting the main branch and requiring pull requests slows everything down. We spend a lot of time explaining, resetting, and figuring things out. And fixing other people's code (when they can't jump in and re-write it themselves) - pushes me deeper and deeper into the nitty-gritty of execution. It gets trickier with more people. If anyone switches branches, everyone’s view changes. A single click can interrupt the whole team’s progress. That’s frustrating when you’re in the middle of work. These collaboration tools are still very much in beta. As a real team, we can't just wing it pushing straight to production. We need stable, reliable tools for real teamwork. I still find Lovable lacking in that department. Has anyone found a better way to collaborate on Lovable? Curious to hear how other are solving problems like this.