Seriously impressed - had an email inviting us this morning, and connected a repo and boom, I have a visual workflow of my coded app
. Well done bubble
and this is just beta ![]()
Bubble made this? Why do you say well done Bubble?
A few months back we had a company-wide hackathon. This was one of the ideas coming from a couple of devs from the meta team (the team that uses bubble to build bubble).
Some hackathon projects are easy to implement alongside the end product you all use. For others like this one, it’s easier and faster to stand them up on their own. Ultimately the goal of hackathon projects is to ship fast, collect feedback and iterate.
This is actually a really good idea. First idea I’ve seen from Bubble that makes sense in this new world we are living with. Hats off to the team that built this. ![]()
I feel like Bubble can literally disappear and just have that Reverse app and be better. Reverse is exactly what Bubble should be now. Crazy how simple an app can be and it could be just what we are looking for.
Yeah, why is this the first time I am seeing this… ![]()
So is Bubble the owner of it or did the devs get to create their own platform separate from Bubble? Just trying to figure out who owns it.
Just checked the terms, I guess Bubble owns it.
It literally just launched yesterday.
But if you mean why we didn’t announce it like we do with typical bubble releases, the team wanted to try and separate audiences a bit
Ahh, seemed like from your message it was done awhile ago
Looks like you get enough tokens to demo one repo and I picked my test one and not my actual app ![]()
Hi all! LD here from the Meta team ![]()
We’ve been working on Reverse for a little while now, thanks for trying the pilot! DMs are open for questions ![]()
So this takes a traditionally coded app and turns it into a bubble app?
Oh boy I got it! Now theres a plenty vibe coding apps and the founders cant understand their creation, so this will explain the thing and then maybeee suggest to migrate code-to-bubble to have understanding of its app…
Great, it makes sense for a lot of fast-chunky-prototype apps out there, i think.
Right now we create an understanding layer for your code!
Short overview:
Connect any github repo &…
- View logic as workflows + peek at the files
- Read documentation - automatically generated + view stack
- Everything can stay in sync with github
- Preview your app in the browser (+ some custom devtools)
- Ask about or Edit your Code with the Chat, you can highlight anything and ask the agent
- Changes are done securely on branches, merge when ready
DMs open + we have an in-app feedback tool. Click the (?) on the top right toolbar. ![]()
Very good ![]()
Tried it with a GitHub repo and it worked great.
I like how it shows how many credits you have left.
Also like the preview feature.
Great job!
Probably because you can’t really use it on Bubble apps. I would guess.
Worth stepping back and thinking about where this sits strategically, rather than just “nice tool.”
Bubble’s core strength has always been the finely controlled ecosystem: database, workflows, auth and hosting in one place, with guardrails. For a lot of production apps that’s exactly what you want, and it isn’t going anywhere.
Where they’ve struggled, honestly, is the native AI story. It has been slow and a bit painful to use. Roadmap pieces like MCP may help close that gap. But Reverse is a different kind of bet, because it looks outward instead of inward.
Here’s the part I think is easy to miss:
Bubble’s original market was people without a traditional dev background. The exact same people now building with AI on Lovable, v0, Cursor, Replit and the rest. Reverse doesn’t compete with any of those. Because it works through GitHub, it wraps around all of them.
So if Bubble markets this right:
- Platform-agnostic — one tool that sits on top of every type of coding output, whatever built it.
- Targets the pain, not the platform: “I can’t see how my app works” is universal across all of them.
- Meets Bubble’s original audience where they’ve gone, instead of asking them to come back.
- Addresses the whole vibe-coding wave at once, far bigger than any single builder’s user base.
That last point is the one.
No individual platform can own that space. A neutral layer that explains any of them can.
Hope the team sees it that way too.
O
I think this whole release stinks of Bubble not knowing what its strategy or place in the market is… but I seem to be in the minority and was telling Bubble to stop wasting time on AI two years ago, so maybe I’m just a party pooper
Maybe it’s an experiment to try and find a strategy, but w/ stuff like this I think you’ve got to pick a target and hit it rather than hand waving and trying to entertain every opportunity
I could be way off the mark and get quoted in 6 months and you can laugh at how silly I am though ![]()
Edit: and this could’ve been built on Bubble! But wasn’t!
I’m not really thinking this took any of the developers away from any time they’re spending on making Bubble better. Quite the opposite, I’m thinking.
I’m quite sure they use GitHub a whole lot when working with Bubble and built this tool to help manage their own internal repos so they can make Bubble better.
Maybe they put it out to see if others could use it and maybe give feedback on ideas or suggestions?
Yes, the frontend maybe could have been built with Bubble, but Bubble isn’t a low-level compiler tool designed to parse abstract syntax trees and manage Git branches for raw codebases. So I don’t see how the whole thing could have been built on Bubble?
So, my own opinion is that this will help the Bubble team build faster and better.
Just my thoughts
I’m loving where the space is going. What a time to be alive! We may get to a point where audiences who were taken away by vibe coding may come back full circle into Bubble. It sounds like this could be a potential play from this tool
I would argue the exact opposite, that this is the first indication I’ve seen that Bubble understands its place in the market.
I said this a few months ago but they need to focus their marketing on “unbreaking your AI app” and “the AI/vibe-coded app that doesn’t break.” In the same way that you’ve built a service on unbreaking hastily put together Bubble apps, Bubble can build a product on unbreaking hastily put together vibe-coded apps.
consider me thoroughly corrected then
