I Let an AI Build My App. Two Years Later, I Asked Another AI to Fix It.
| Source: Mastodon | Original article
A New Zealand developer who used the AI‑coding platform Lovable (formerly GPT Engineer) to spin up a hobby weather app in a single afternoon in 2024 has now published a two‑year follow‑up that pulls back the curtain on what the tool actually produced. The blog post, released on 19 April 2026, walks readers through the 3,200‑line codebase, pointing out sections that work flawlessly, parts that are riddled with duplicated logic, and a handful of security‑relevant oversights that would have been missed without a manual audit.
The experiment matters because it provides one of the first longitudinal looks at AI‑generated software outside a sandbox. While the app functioned for its intended purpose—displaying local forecasts and sending push notifications—the author discovered that the code lacked modularity, relied on hard‑coded API keys, and contained several dead‑end branches that made future extensions painful. The findings echo concerns raised in recent industry analyses about the “black‑box” nature of AI code generators and their propensity to produce brittle, hard‑to‑maintain artifacts.
The post also highlights how the developer leveraged a second‑generation AI assistant to refactor the project, illustrating a nascent workflow where one model builds and another audits. This “AI‑in‑the‑loop” approach could become a standard practice if tooling improves its ability to explain and verify generated code.
What to watch next: vendors of AI app‑builders such as Builder.ai and the newly ranked lindy.ai platforms are racing to add explainability layers and automated testing suites. Regulators in the EU and the US are beginning to draft guidance on software liability for AI‑produced code, a move that could force tighter validation standards. The developer’s candid audit may spur more long‑term case studies, giving the industry concrete data to gauge whether AI can move from rapid prototyping to reliable production.
Sources
Back to AIPULSEN