SMF·BUBBLE
Can a prompt replace Bubble?
No-code apps — visual web app builder
Exhibit tracking slip
Verdict
The honest move is never to clone Bubble itself — it's to rebuild the one specific app you actually run on it, in plain code. That's a real multi-day build: CRUD screens, a couple of workflows, and hosting. What you give up is the visual editor, which means every future change is now a code change, not a drag-and-drop one.
Exhibit A — The prompt
Received on30.07.2026Before writing anything, get the actual shape of the app: the 3–5 core screens, the data types and their fields, and the one or two workflows that matter most. Then build exactly that app in code — not a general-purpose app builder, not a Bubble clone. A typical shape: server-rendered pages backed by a real database, CRUD screens (list with search/filter, detail view, create/edit forms with validation) for each data type, and each 'workflow' from the original app rewritten as a plain function — a form submit that updates a row, sends an email, and redirects; anything scheduled becomes a cron job in the same process. Add authentication only if people other than the owner will log in; for a single-user tool, skip auth entirely and keep it private. Store data in a real database with a scheduled export so nothing is ever trapped.
Do not build a visual editor, a plugin system, or anything else platform-shaped — the deliverable is one working app that deploys to a small server, not a tool for building other apps. Make clear in the README that every future change is now a code change: that trade is the actual point of doing this.Opening prefills the prompt — press enter to run it.
Exhibit B — What you lose
- B.1 the visual editor for making changes without touching code
- B.2 Bubble's plugin marketplace
- B.3 built-in hosting and scaling
- B.4 the ability for a non-developer to maintain the app afterward
Prior art
Exhibit C — Why people still pay: no-code platform/ecosystem
People keep paying because future changes stay visual — no developer required. The moment you own the code instead, every change is a pull request, not a drag-and-drop edit.
Questions
Can I bring over my existing Bubble app and data?
The data, yes — Bubble can export your database to CSV, and that maps onto the new schema. The app itself doesn't transfer: Bubble's visual workflows have to be re-read and rewritten as code by hand, one at a time.
Will it work on my phone?
As a responsive web page, yes, the same way the Bubble version did. There's no native app either way, so nothing changes there.
What does it cost to run?
A small VPS and a database, typically five to ten dollars a month — often less than a workflow-heavy Bubble plan, since you're only paying for your own server.
What's the one thing that doesn't survive the rebuild?
Visual, no-code changes. Every future tweak — a new field, a new screen, a changed workflow — now goes through code and a deploy, not a drag-and-drop edit in a browser tab.
Related tools
Receipt