As AI-assisted coding started taking over the software development industry, teams maintaining Bubble applications were starting to feel like they were falling behind.
While traditional engineering teams were accelerating with AI tools, many Bubble teams were still dealing with the same manual workflows around planning, building, testing, and debugging.
That’s how things felt for our team, until we tried BuildPrint by @georgecollier.
Here’s what the workflow typically looked like.
Before BuildPrint
Feature planning - hours
- Scope the feature
- Explore the current app structure, data models, layout, and workflows
- Design mockups
- Write an implementation plan
Development - days or weeks depending on the project
- Drag and drop UI elements
- Manually create or modify data structures
- Manually build workflows
Testing and review
- Manual testing
- Implementation review by a senior developer (often skipped due to time pressure)
- Address review comments
- Merge and deploy
Then bugs inevitably show up.
Bug workflow:
Slack → ticket in Asana → manual debugging → fix → test → deploy.
After introducing BuildPrint
-
Feature planning - minutes
-
Development - not fully there yet, but moving fast.
-
Testing - writing and running tests is automated and takes minutes.
-
Reviews - surprisingly one of the biggest improvements. The feedback is structured and often highlights things that improve the next feature we build.
-
Debugging - deep debugging across logs, UI, workflows, and data structures from one place.
The biggest change for our team isn’t just speed.
It’s the compression of the engineering loop.
Planning, testing, debugging, and reviewing are becoming assisted processes instead of manual overhead.
Still early, but agentic engineering for Bubble is starting to feel very real.