The first category includes tools like Lovable or Base44. These are prompt-driven tools that can generate visually polished interfaces very quickly. They're great for demos that need to look impressive. However, they are usually frontend-focused. Once you need to store data, manage users, or connect real logic, things often become fragile. Backend integrations—commonly via services like Supabase—can break in ways... - Source: dev.to / 7 months ago

I love how AI is shaking up coding, and vibe coding seems to be the new obsession of -almost- every developer. It lets anyone, even non-coders, build apps by describing ideas in plain English. Tools like Base44, Lovable, and Cursor turn your words into working code, no syntax required. - Source: dev.to / about 1 year ago

Landing page is excellent, esp the video; gets straight to the point. https://www.youtube.com/watch?v=vFzQF_Ik_-g https://base44.com/. - Source: Hacker News / about 1 year ago

Base44 For non-coders. All-in-one. Creates dashboard-like apps pretty well. - Source: dev.to / about 1 year ago

Tools like Userdoc (https://userdoc.fyi) help in a few ways, you can easily create requirements (stories, personas, journeys, test cases), but also reverse engineer existing source code into detailed docs, then ask natural language questions etc. AI helps us plan our product in Userdoc, and our devs connect via MCP to bring those requirements directly in to Cursor (full disclaimer, I work at Userdoc - but we eat... - Source: Hacker News / about 1 year ago

Userdoc has versioning of stories and acceptance criteria, aimed to at helping this exact issue https://userdoc.fyi (transparency: I’m the founder). - Source: Hacker News / over 1 year ago

I'm interested to hear how other people are using tools to help them, we've been playing with userdoc.fyi and having good success, but there are just so many AI related tools I feel like I can't keep up! Source: about 3 years ago

Great read, I spent years thinking requirements should live somewhere like Jira, and I feel for many teams this is the case. But as the author mentions, Jira contains tasks related to bugs, text changes, colour changes etc.. These are not product requirements per se. Like the author, I came to the conclusion requirements are best kept in a requirements management system, that integrates with your project... - Source: Hacker News / about 3 years ago

I built Userdoc (https://userdoc.fyi) a requirements management system for software projects. After running a development consultancy for 8 years, I wanted a dedicated system for gathering and confirming requirements, and only syncing them with project management tools like Jira when they are ready (but keeping them in Userdoc as the living documentation and source of truth. Things are going well, we have some... - Source: Hacker News / over 3 years ago