Our engineering workflow before vs after using BuildPrint (Bubble agentic engineering platform)

Tips
1

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.

2

Love this!

3

Could you go into more detail about this?

4

@randomanon I’m referring to the BuildPrint agent in edit mode. We tried an early version while building a new feature in a fairly large Bubble app. It didn’t end up implementing the feature exactly the way we intended, but the experience was still promising. I think it can be really useful for other use cases.

5

Out of interest what kind of stuff do you try it for and what don’t you bother with it for?

6

We gave it a spin a few weeks ago, but we’ve really started leaning into it this week and it’s awesome. We found the best workflow is starting in Plan Mode to get the logic right, then moving to Build, and making sure to create a dedicated branch for each new feature or update. It’s made the whole process much cleaner.

7

what kind of tickets do you have it working on?

8

@mo.salama has this changed at all since early April?

9

It’s wild to see a Bubble Renaissance happening in real-time. I remember one of the initial @georgecollier posts on X re: BP’s editing capabilities and thinking “this is gonna be Bubble 2.0.” George and the BP team haven’t disappointed!
Edit: George’s stated initial goal was to “get people excited about Bubble again”. So cool.

10

@georgecollier It has changed a lot. Most of our new features are built now with BP agent. Thanks for building such an amazing product.

11

Awesome. Glad to hear it!

Let’s see where Buildprint is at in another couple of months :wink:

12

I was playing around with an idea to take a Figma design and have it reproduced in Bubble.

It is 100% possible.

I tested it on a button and a couple of other small things, and it worked fine.

I just don’t have the time or energy to follow up and make it for a whole page, etc. Usually, when I do get free time, I’m either wasting my time on some forum or just vegetating lol.

But it can be done.

Would also think that if BP could examine workflows, etc., and give an idea of the work unit costs, that would be awesome. That also could be done… but again, it takes time.

You’re on a roll with BP, and I’m quite sure it will only get better and better :slightly_smiling_face:

13

I mean, you can add your own /estimate skill

I can’t make one for everyone because everyone works at different speeds

14

Ok. Sorry, my bad.

I’m not all that up on everything BP can do.

Was just thinking if I said I had 1000 daily users, if it could give an idea of the monthly WU costs.

I’ll look into that.

Thanks

15

@mo.salama what model(s) are you using now? do you have any tips for people using buildprint (or not using it)?

16

@georgecollier

We typically switch between Sonnet, Opus, and GPT-5.5 depending on the task.

Here’s the workflow that’s been working well for us:

  1. Start in Plan Mode and create a single branch, whether you’re fixing a bug or building a new feature.
  2. Before writing code, ask the AI to understand the problem or explain how the feature should be implemented.
  3. Ask it to generate an implementation plan.
  4. Review and refine the plan before building anything.
  5. Once the plan looks solid, ask it to create a new branch and start implementing.
  6. For new features, build them as reusable components or on separate pages whenever possible.
  7. If the task involves UI, have the AI design it in HTML first. If you’re using Claude Design for design, export the design and ask BuildPrint to implement it. Always tell it to reuse your existing styles (if you have one) so everything stays consistent.
  8. Before merging, run a Review. It almost always catches something useful or suggests a better approach.
  9. When the implementation is complete, ask it to generate tests and documentation before wrapping up.

A little planning upfront saves a lot of debugging later.

17

Preach